I'm trying to get my head around SNMPv3, specifically the security aspects. I've read
the FAQ and skimmed the RFCs but I need a little more orientation, if someone could
oblige.
The/a big differenece between v2c and v3 is that v2c uses a community string, passed
in the clear whereas v3 uses a user and password passed on an encrypted channel. Is
that right? I believe I know that v3 uses SSL for its encryption. And I think I know
that if I use the net-snmp API or command-line tools on a client to contact net-snmp
agent on a remote host, that all the encryption is handled for me under the covers.
What I don't understand -- if that's all true -- is where the keys come from for
establishing the connection. Do I have to generate keys? Do the agent and the API
have keys that they know and use to trust each other? If there's a FAQ or tutorial on
this, I'd be happy for the pointer but I haven't found anything that says, "If you
want to use v3, you have to generate keys and install them like this...".
TIA.
Chris
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php
_______________________________________________
Net-snmp-users mailing list
[EMAIL PROTECTED]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
