FIPS 140 2 compliance

Hi, For a snmp agent to be FIPS 140 2 compliant, i) is it sufficient that the encryption algorithm used by the agent is any of the following (AES / DES /Triple DES). In the or ii) the agent developed should satisfy all the 11 Security Requirements that FIPS 140 2 defines. Could you pleases c

RE: How to deny access from only some hosts usinf vacm

> From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of arijit > Sent: Friday, January 11, 2008 3:54 AM > # ADD THE FOLLOWING FOR EACH OF THE HOST + COMMUNITY > COMBO U WANNA BLOCK! > #sec.namesource >

Re: How to deny access from only some hosts usinf vacm

Dave, Thanks for the insight! Really appreciate it! I think using the standard snmpd.conf configuration directives, I might still be able to deny access to a particular community from a particular host or subnet. Here's what I plan to do. Please, tell me if this is logically wrong! #

Re: A few disk monitoring issues

Thomas Anders wrote: > We're providing binary SVN snapshot packages for a number of distros: > > http://www.net-snmp.org/wiki/index.php/Third-Party_Packages > > but that offer does *not* include packages for RHEL or Gentoo which > you'd appear to require. I'm not sure whether you could get awa

Verification of VACM parameter in case of SNMPv2 request

Hi All , I have one question regarding the checking of SNMPV3 related parameters. Is it not mandatory that only in case of SNMPv3 request the VACM related parameters will be verified . For example in case of getbulk (SNMPv3) request agent has to verify if the next OID is in the correct