On Fri, Aug 17, 2001 at 06:42:35PM +0200, Lutz Jaenicke wrote: > > I first found them because I wanted my wrapping x509req.get_subject() to > > exist even when x509req is destroyed, so therefore the rather odd "do I > > need them?" question. > Hmm, seems that *_dup() might fulfill your requirement... Yes, and no, it turns out. If I let x509req.get_subject() return a X509_NAME_dup()ed pointer I can't do stuff like req.get_subject().CN = 'me' which would be rather nice (req.set_subject() would work, but it's rather un-Pythonic) :-) I wrote a copy "constuctor" instead, that takes an x509name object and returns a X509_NAME_dup()ed pointer. Thanks Martin -- Martin Sjögren [EMAIL PROTECTED] ICQ : 41245059 Phone: +46 (0)31 7710870 Cell: +46 (0)739 169191 GPG key: http://www.strakt.com/~martin/gpg.html ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
