<?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: Strange snmp issue in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/strange-snmp-issue/m-p/874262#M84996</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No just a snmp-walk from a linux host and then grep on the snmp string.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 10 Jan 2008 14:57:42 GMT</pubDate>
    <dc:creator>hendriksm</dc:creator>
    <dc:date>2008-01-10T14:57:42Z</dc:date>
    <item>
      <title>Strange snmp issue</title>
      <link>https://community.cisco.com/t5/network-security/strange-snmp-issue/m-p/874259#M84986</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If I do a snmpwalk on our IDSM-2 blade, I can read the SNMP write string, this seems a bit insecure to me.&lt;/P&gt;&lt;P&gt;Is this normal behavior?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Michael&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 10:55:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/strange-snmp-issue/m-p/874259#M84986</guid>
      <dc:creator>hendriksm</dc:creator>
      <dc:date>2019-03-10T10:55:39Z</dc:date>
    </item>
    <item>
      <title>Re: Strange snmp issue</title>
      <link>https://community.cisco.com/t5/network-security/strange-snmp-issue/m-p/874260#M84988</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It depends how are you querying the MIB. Some MIB lets you know the write string. Following link may help you&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/tech/tk648/tk362/technologies_tech_note09186a00801576ff.shtml" target="_blank"&gt;http://www.cisco.com/en/US/tech/tk648/tk362/technologies_tech_note09186a00801576ff.shtml&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Jan 2008 19:41:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/strange-snmp-issue/m-p/874260#M84988</guid>
      <dc:creator>tstanik</dc:creator>
      <dc:date>2008-01-09T19:41:22Z</dc:date>
    </item>
    <item>
      <title>Re: Strange snmp issue</title>
      <link>https://community.cisco.com/t5/network-security/strange-snmp-issue/m-p/874261#M84993</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;How are you reading it? In a packet capture?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Jan 2008 14:43:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/strange-snmp-issue/m-p/874261#M84993</guid>
      <dc:creator>David Stanford</dc:creator>
      <dc:date>2008-01-10T14:43:51Z</dc:date>
    </item>
    <item>
      <title>Re: Strange snmp issue</title>
      <link>https://community.cisco.com/t5/network-security/strange-snmp-issue/m-p/874262#M84996</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No just a snmp-walk from a linux host and then grep on the snmp string.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Jan 2008 14:57:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/strange-snmp-issue/m-p/874262#M84996</guid>
      <dc:creator>hendriksm</dc:creator>
      <dc:date>2008-01-10T14:57:42Z</dc:date>
    </item>
  </channel>
</rss>

