Re: [tkined] SNMPv3, SNMPv2usec privacy

Dan Razzell (razzell@cs.ubc.ca)
Fri, 23 Jan 1998 14:02:53 -0800

> From: "Dan Razzell" <razzell@cs.ubc.ca>
> Date: Wed, 21 Jan 1998 13:32:35 -0800
> To: David Poole <davep@fortytwo.tierranet.com>, tkined@ibr.cs.tu-bs.de
> Subject: Re: [tkined] SNMPv3, SNMPv2usec privacy
>
> The trick seems to be to add cryptography to Tcl in a well defined and
> separable way, so that applications which use it can be freely exported
> even from countries which don't permit the export or use of the actual
> cryptography.

I just noticed in comp.lang.tcl.announce that a Tcl interface to SSLeay
has become available as an extension to the socket command. This is not
as versatile as having encryption directly available to Tcl programs,
and therefore doesn't address the SNMPv2usec issue, but it may be useful
in other cases. For example, it's essentially the same approach as I
followed in modifications to Scotty before binary data became available
in Tcl.

--
!! 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.