From: mal at lemburg.com (M.-A. Lemburg)
Date: Tue, 06 Apr 1999 10:41:34 +0200
Subject: SNMPy update
References: <7e1hiq$a71$1@Starbase.NeoSoft.COM>
		<7ear25$ksf$1@news-sj-3.cisco.com> <14089.11820.416453.80124@bitdiddle.cnri.reston.va.us>
Message-ID: <3709C8BE.4257C9F1@lemburg.com>
Content-Length: 1512
X-UID: 1662                                                  

Jeremy Hylton wrote:
> 
> I'll second your sentiment!  I did some work on an X.509 library
> written entirely in Python.  Like you friend's SNMP code, it will
> probably never be released; I don't have time to finish it nor did I
> expect that I'd want to release it given the export control hassles.

Just want to note that SSLeay/OpenSSL includes a pretty complete
X.509 lib and also routines to do ASN.1 encoding an decoding.
The main argument for using OpenSSL in this context is, of course,
that no export control restrictions apply.

> However, it seemed clear to me that an ASN.1 compiler could be written
> to generate the encode/decode routines.  If someone is interested in
> that, I've got some design notes and rough code on how to do the
> encode/decode and on how to build a backend for SNACC.  (A free-ish
> ASN.1 compiler; the only one?)

Not sure what you mean with "ASN.1" compiler. If you want a compiler
that does ASN.1 description -> Python function calling de/encoding
routines kind of thing, then I guess the ASN.1 stuff in OpenSSL
could help you getting started quite fast.

Note that I have a project running with the intention to wrap OpenSSL 
in an OO manner called mxCrypto (see the link below).

-- 
Marc-Andre Lemburg                               Y2000: 269 days left
---------------------------------------------------------------------
          : Python Pages >>> http://starship.skyport.net/~lemburg/  :
           ---------------------------------------------------------





