David> I'm working on a product managed via SNMPv1. I'm starting work
David> on a SNMPv2, SNMPv3 agent primarily to take advantage of the
David> privacy abilities to get portable secure management. Are there
David> any plans to integrate the 40-bit encryption abilities of
David> SNMPv2usec and SNMPv3 into Scotty?
I am not going to do any work on SNMPv2u. If we do SNMPv3, than we
will most likely implement authentication and encryption. I am
currently thinking about removing SNMPv2u support once we start to put
SNMPv3 into the code. Would this be a real problem for someone out
there?
David> I know that there are signifigant legal problems with data
David> encryption, but the default 40-bit DES used for privacy is USA
David> exportable (can't speak for other countries policies).
One solution would be to find an FTP server in a country which allows
to export everything or we could just provide the API calls and you
have to pickup the DES library from somewhere else. These export laws
are nasty but not a real problem.
Juergen
-- Juergen Schoenwaelder schoenw@ibr.cs.tu-bs.de http://www.cs.tu-bs.de/~schoenw Technical University Braunschweig, Dept. Operating Systems & Computer Networks Bueltenweg 74/75, 38106 Braunschweig, Germany. (Tel. +49 531 / 391 3283)-- !! This message is brought to you via the `tkined & scotty' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <tkined-request@ibr.cs.tu-bs.de>. !! See http://wwwsnmp.cs.utwente.nl/~schoenw/scotty/ for more information.