> On Fri, 23 Dec 2005 11:48:08 + (GMT), saifulla Mohd Abdul <[EMAIL
> PROTECTED]> said:
saifulla> But as per RFC 3414 section 3.2, it has to return a valid
saifulla> error message based on the error found in the query, right?
Only if you can determine that an error occurred. In the
> On Wed, 21 Dec 2005 12:35:28 +, Dave Shield <[EMAIL PROTECTED]> said:
>> Please give your suggestion.
Dave> Don't use pass phrases with repeated patterns :-)
All passwords can eventually repeat ;-)
However, the trick is to use a long enough password in the first place
(with no repeati
Thanks a lot Dave for the information. One more issue:
snmp v3 walk with incorrect privacy password returns
timeout error.
Let us say, if i configure a privacy password as
"priv_pass"
and do snmpwalk with incorrect privacy password as
below:
Command: "snmpwalk -v 3 -u user12 -l authPriv -a md5
-
On Wed, 2005-12-21 at 11:18 +, saifulla Mohd Abdul wrote:
>There is an issue with authentication password and
> privacy password used with SNMP v3 in net-snmp.
This isn't specific to Net-SNMP.
It's inherent in the way pass phrases are mapped to
authentication and encryption keys.
> Isn't
Hi,
There is an issue with authentication password and
privacy password used with SNMP v3 in net-snmp. Please
give your
suggestion.
When a user is added with:
net-snmp-config --create-snmpv3-user -a "12345678" -x
"12345678" -A MD5 user1
All the snmp queries with any number of repeated
patte
