secure snmp: too much bang for the buck?

Article View: comp.protocols.snmp

Article #123

Back to comp.protocols.snmp Previous Next

#123

From: 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

Technical Details

Message-ID: <1992Sep12.213808.27554@gordian.com>

Path: arc1-ca.pugleaf.net!sparky!uunet!spool.mu.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!usc!news.service.uci.edu!gordius!dan

Show Full Headers

Complete Article Headers

Newsgroups: comp.protocols.snmp
Path: arc1-ca.pugleaf.net!sparky!uunet!spool.mu.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!usc!news.service.uci.edu!gordius!dan
From: dan@gordian.com (Dan Lambright)
Subject: secure snmp: too much bang for the buck?
Message-ID: <1992Sep12.213808.27554@gordian.com>
Organization: Gordian; Costa Mesa, CA
Date: Sat, 12 Sep 1992 21:38:08 GMT
Lines: 17