<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[FreeCommander - Version Number]]></title><description><![CDATA[<p dir="auto">FreeCommander is detected as:<br />
FreeCommander XE	2019.0.0.790</p>
<p dir="auto">GUI:<br />
FreeCommander XE 2019   Build 790 32-bit public</p>
<p dir="auto">Recommended version is older:<br />
Recommended version: 2018 release 770 public</p>
]]></description><link>https://vulndetect.org/topic/552/freecommander-version-number</link><generator>RSS for Node</generator><lastBuildDate>Sat, 13 Jun 2026 18:57:07 GMT</lastBuildDate><atom:link href="https://vulndetect.org/topic/552.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 20 Dec 2018 20:24:11 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to FreeCommander - Version Number on Thu, 20 Dec 2018 20:51:41 GMT]]></title><description><![CDATA[<p dir="auto">Thank you</p>
<p dir="auto">The primary issue is that you are too fast ;)</p>
<p dir="auto">New versions need a Specific Rule, in some cases you can't see this, because the version number in the file is the same as the one on the site, but in other cases like FreeCommander, we need to rewrite it. The unknown versions are added automatically to our to do list and are usually added within a working day.</p>
<p dir="auto">But this 790 releases might cause a headache, because now I added it as "public", but this time the "donor" is also at 790, so I guess <a class="plugin-mentions-user plugin-mentions-a" href="/user/olli_s" aria-label="Profile: OLLI_S">@<bdi>OLLI_S</bdi></a>  will complain soon :D</p>
]]></description><link>https://vulndetect.org/post/2207</link><guid isPermaLink="true">https://vulndetect.org/post/2207</guid><dc:creator><![CDATA[Tom]]></dc:creator><pubDate>Thu, 20 Dec 2018 20:51:41 GMT</pubDate></item></channel></rss>