secure snmp: too much bang for the buck?

Thread View: comp.protocols.snmp

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by Dan Lambright Sat, 12 Sep 1992 21:38

#123

Author: Dan Lambright
Date: Sat, 12 Sep 1992 21:38

16 lines
1068 bytes

I've been studying rfc 1352 (secure snmp) and am trying to
decide if its worth implementing.  We want to support snmp
sets, but up until 1352 came out it was too risky.  Now 
however,  I am starting to wonder if 1352 is overkill.  I
mean its got DAP, encryption, passwords, and synchronized
clocks.  Its secure allright,  but it sure is alot of overhead
for the little platform that I am writing snmp for. 
Has anyone out there had any experience with secure snmp?
How much code space did it take?  How much complexity did
it add to your platform?  And more in general,  what are
peoples opinions about the new security mechanisms outlined
in 1352?  

Dan Lambright
dan@gordian.com

Re: secure snmp: too much bang for the buck?

#130

Author: Ed Alcoff - Prod Mtg
Date: Mon, 14 Sep 1992 23:21

21 lines
1166 bytes

Pls realize that SMP provides for a slight mod to
the Secure SNMP as spec'd in the RFCs.

Also, I disagree that a vendor should not support SETs
because of a lack of security.  Leave the security of
the net to the user- they can choose to use SETs or not
with an appropriate entry in a typical snmpd.conf (use
READ instead of READ-WRITE)

Also, SMP/Secure SNMP does not provide a perfectly secure
environment.  Due to possible export restrictions, some
vendors may choose not to implement encryption.  Also,
one cannot set the value of the life delay to 0 so that
one will be able to intercept the packet and retransmit
it from a rogue implementation.

So it's much better, but certainly not overkill.

Cheers,

/era

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads