<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Signature Update S161 Missing Signatures in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/signature-update-s161-missing-signatures/m-p/405527#M98151</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;These are 5.x only signatures; they replace 4701 and 4702 which have been retired in 5.x. Thank you for bringing this to our attention, we are posting an updated version of the readme.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 02 May 2005 23:09:02 GMT</pubDate>
    <dc:creator>craiwill</dc:creator>
    <dc:date>2005-05-02T23:09:02Z</dc:date>
    <item>
      <title>Signature Update S161 Missing Signatures</title>
      <link>https://community.cisco.com/t5/network-security/signature-update-s161-missing-signatures/m-p/405526#M98150</link>
      <description>&lt;P&gt;The following signatures are mentioned in the release notes but do not show up in VMS:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;4703.0  MSSQL Resolution Service Stack Overflow STRING.TCP  Info  True  &lt;/P&gt;&lt;P&gt;4704.0  MSSQL Resolution Service Stack Overflow STRING.TCP  Info  True  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 09:26:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/signature-update-s161-missing-signatures/m-p/405526#M98150</guid>
      <dc:creator>lbhoang</dc:creator>
      <dc:date>2019-03-10T09:26:05Z</dc:date>
    </item>
    <item>
      <title>Re: Signature Update S161 Missing Signatures</title>
      <link>https://community.cisco.com/t5/network-security/signature-update-s161-missing-signatures/m-p/405527#M98151</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;These are 5.x only signatures; they replace 4701 and 4702 which have been retired in 5.x. Thank you for bringing this to our attention, we are posting an updated version of the readme.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 May 2005 23:09:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/signature-update-s161-missing-signatures/m-p/405527#M98151</guid>
      <dc:creator>craiwill</dc:creator>
      <dc:date>2005-05-02T23:09:02Z</dc:date>
    </item>
    <item>
      <title>Re: Signature Update S161 Missing Signatures</title>
      <link>https://community.cisco.com/t5/network-security/signature-update-s161-missing-signatures/m-p/405528#M98152</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What I have noticed already in former updates is that there is a difference in grouping of the new signatures in the CiscoWorks VMS/IDS MC and on the ids device itself(via IDM). For example, in S161, there is the new signature 3347 which is added to the attack signatures group under 'command execution' on the ids device, but in CW VMS I don't find this signature in the same category. For us this is however important to find this signature in the proper group in CW VMS, because we do additional modifications on those signatures. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 May 2005 08:15:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/signature-update-s161-missing-signatures/m-p/405528#M98152</guid>
      <dc:creator>jodr</dc:creator>
      <dc:date>2005-05-03T08:15:45Z</dc:date>
    </item>
  </channel>
</rss>

