From woutervanbommel at gmail.com Tue May 5 10:55:15 2009 From: woutervanbommel at gmail.com (Wouter van Bommel) Date: Tue, 5 May 2009 10:55:15 +0200 Subject: [pyOpenSSL] Parsing subjectaltname Message-ID: <3f96c1440905050155r108ec3bbo725ca75136e2cf4@mail.gmail.com> Hi All, Currently I am working on a project in which I need to parse an subjectaltname part of a certificate. It is known that the type of the subjectaltname is of type otherName (2.5.5.5). Code to insert it in the certificate is probably simular to the examples used in the discussion on http://markmail.org/message/b7lmomgglut22sdl To solve this issue I am wondering which approach is the best. Adding an extension to extract subjectaltname and some kind of typeconversion (yet no idea how, but probably can implement something) or are there other possiblities / solutions already available. Currently I am able to generate the correct commandline option for openssl asn1parse to show me only the content of the subjectaltname part (reinterpret by the parser, hence human readable). regards, Wouter -------------- next part -------------- An HTML attachment was scrubbed... URL: From exarkun at divmod.com Tue May 5 14:31:55 2009 From: exarkun at divmod.com (Jean-Paul Calderone) Date: Tue, 5 May 2009 08:31:55 -0400 Subject: [pyOpenSSL] Parsing subjectaltname In-Reply-To: <3f96c1440905050155r108ec3bbo725ca75136e2cf4@mail.gmail.com> Message-ID: <20090505123155.21531.89897004.divmod.quotient.472@henry.divmod.com> On Tue, 5 May 2009 10:55:15 +0200, Wouter van Bommel wrote: >Hi All, > >Currently I am working on a project in which I need to parse an >subjectaltname part of a certificate. >It is known that the type of the subjectaltname is of type otherName >(2.5.5.5). > >Code to insert it in the certificate is probably simular to the examples >used in the discussion on http://markmail.org/message/b7lmomgglut22sdl > >To solve this issue I am wondering which approach is the best. Adding an >extension to extract subjectaltname and some kind of typeconversion (yet no >idea how, but probably can implement something) or are there other >possiblities / solutions already available. > >Currently I am able to generate the correct commandline option for openssl >asn1parse to show me only the content of the subjectaltname part >(reinterpret by the parser, hence human readable). I'm not really sure what you're asking. Are you looking for a pyOpenSSL for getting the subjectAltName from an X509 object? Or are you trying to include a subjectAltName in a new certificate created with pyOpenSSL? Jean-Paul From woutervanbommel at gmail.com Wed May 6 07:54:30 2009 From: woutervanbommel at gmail.com (Wouter) Date: Wed, 06 May 2009 07:54:30 +0200 Subject: [pyOpenSSL] Parsing subjectaltname In-Reply-To: <20090505123155.21531.89897004.divmod.quotient.472@henry.divmod.com> References: <20090505123155.21531.89897004.divmod.quotient.472@henry.divmod.com> Message-ID: <4A012616.7040300@gmail.com> Hi, My question is how to get a subjectaltname from an existing x509 object, using pyopenssl.. The issue I expect is that subjectaltname on this object is encoded as an othername type (oid 2.5.5.5) and I have no idea how I am expected to get is parsed correctly. Does this involve writing an extention? or are there already meganisms provided with pyopenssl to indicate the type of an subjectaltname? regards, Wouter Jean-Paul Calderone schreef: > On Tue, 5 May 2009 10:55:15 +0200, Wouter van Bommel wrote: > >> Hi All, >> >> Currently I am working on a project in which I need to parse an >> subjectaltname part of a certificate. >> It is known that the type of the subjectaltname is of type otherName >> (2.5.5.5). >> >> Code to insert it in the certificate is probably simular to the examples >> used in the discussion on http://markmail.org/message/b7lmomgglut22sdl >> >> To solve this issue I am wondering which approach is the best. Adding an >> extension to extract subjectaltname and some kind of typeconversion (yet no >> idea how, but probably can implement something) or are there other >> possiblities / solutions already available. >> >> Currently I am able to generate the correct commandline option for openssl >> asn1parse to show me only the content of the subjectaltname part >> (reinterpret by the parser, hence human readable). >> > > I'm not really sure what you're asking. > > Are you looking for a pyOpenSSL for getting the subjectAltName from an > X509 object? > > Or are you trying to include a subjectAltName in a new certificate created > with pyOpenSSL? > > Jean-Paul > > > ------------------------------------------------------------------------------ > The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your > production scanning environment may not be a perfect world - but thanks to > Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 > Series Scanner you'll get full speed at 300 dpi even with all image > processing features enabled. http://p.sf.net/sfu/kodak-com > _______________________________________________ > pyopenssl-list mailing list > pyopenssl-list at lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/pyopenssl-list > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From roastie at rochester.rr.com Wed May 20 20:47:22 2009 From: roastie at rochester.rr.com (Uncle Roastie) Date: Wed, 20 May 2009 13:47:22 -0500 Subject: [pyOpenSSL] Initial install of pyOpenSSL Message-ID: <793a17940905201147s7c492f36u7ecf204ce81146d3@mail.gmail.com> I'm trying to do an install of pyOpenSSL for Twisted in Python 2.5.4 on Windows XP. I installed PyCrypto, OpenSSL for Windows, and PyOpenSLL. When I enter the Python interpreter and say >>> import OpenSLL I get the following error: "The procedure entry point SSL_CTX_set_info_callback could not be located in the dynamic link library ssleay32.dll." The DLL lives inside the OpenSLL/bin directory, which is also on the search path. OpenSSL: openssl-0.9.8e_WIN32.zip pyOpenSSL: pyOpenSSL-0.7.win32-py2.5.exe I also tried: > easy_install pyOpenSSL Any ideas? Uncle Roastie roastie at rochester.rr.com -------------- next part -------------- An HTML attachment was scrubbed... URL: