<?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[Consider ESR Versions]]></title><description><![CDATA[<p dir="auto">Some applications have special versions that are especially for business users.<br />
These applications skip some major releases so in comparison to consumer versions they have different version numbers.</p>
<p dir="auto">For example: Mozilla Firefox ESR (Extended Support Release)<br />
I am not sure if Google Chrome for enterprise also skips some updates.</p>
<p dir="auto">You have to make sure that these versions are detected correctly and that the <a href="https://vulndetect.com/topic/16/show-available-version" rel="nofollow ugc">available versions</a> are also shown correctly.</p>
<p dir="auto">The best way would be to have two separate products:</p>
<ul>
<li>Mozilla Firefox</li>
<li>Mozilla Firefox ESR</li>
</ul>
<p dir="auto">This should be the easiest solution.</p>
]]></description><link>https://vulndetect.org/topic/30/consider-esr-versions</link><generator>RSS for Node</generator><lastBuildDate>Wed, 14 Oct 2026 15:57:17 GMT</lastBuildDate><atom:link href="https://vulndetect.org/topic/30.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 17 May 2018 07:28:47 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Consider ESR Versions on Thu, 17 May 2018 16:48:37 GMT]]></title><description><![CDATA[<p dir="auto">The short answer is that we have to.<br />
The bit longer is that the agent should be able to handle this in almost all cases, so it is mostly a question of the rules. However, the first iteration of the rules will not be able to handle this correctly.</p>
]]></description><link>https://vulndetect.org/post/111</link><guid isPermaLink="true">https://vulndetect.org/post/111</guid><dc:creator><![CDATA[Tom]]></dc:creator><pubDate>Thu, 17 May 2018 16:48:37 GMT</pubDate></item></channel></rss>