From tavl at cin.ufpe.br  Thu May 22 06:59:17 2014
From: tavl at cin.ufpe.br (Thiago A. V. Lima)
Date: Thu, 22 May 2014 01:59:17 -0300
Subject: [pyOpenSSL-Users] Extensions support in CRL object
Message-ID: <CAP+sHjn+RvJA1zc9a=FrADf2hw9KCoK11hb051XREa4X++3R2A@mail.gmail.com>

Hello all.

How to add extensions to a crypto.CRL object? Is it possible? What about
the version attribute? If not, could someone, please, point me in the best
direction toward adding it to PyOpenSSL?


Thanks in advance,

-- 
Thiago Augusto V. Lima
Computer Engineer @ CIn - UFPE - Brazil
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pyopenssl-users/attachments/20140522/fcc74f65/attachment.html>

From tavl at cin.ufpe.br  Thu May 22 07:04:04 2014
From: tavl at cin.ufpe.br (Thiago A. V. Lima)
Date: Thu, 22 May 2014 02:04:04 -0300
Subject: [pyOpenSSL-Users] OpenSSL Engine support
Message-ID: <CAP+sHjn_NDd_xv1vvgCYcXi2GJ6NDCkPks0HrKM=Sz+W+Ojf9w@mail.gmail.com>

Hello.

Is there anything implemented in PyOpenSSL regarding OpenSSL engines? I was
checking cryptography code and I saw some references there to it. If
PyOpenSSL doesn't support it, what would be the best way to add it?


Best regards,

-- 
Thiago Augusto V. Lima
Computer Engineer @ CIn - UFPE - Brazil
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pyopenssl-users/attachments/20140522/496762ca/attachment.html>

From exarkun at twistedmatrix.com  Thu May 22 14:06:01 2014
From: exarkun at twistedmatrix.com (exarkun at twistedmatrix.com)
Date: Thu, 22 May 2014 12:06:01 -0000
Subject: [pyOpenSSL-Users] OpenSSL Engine support
In-Reply-To: <CAP+sHjn_NDd_xv1vvgCYcXi2GJ6NDCkPks0HrKM=Sz+W+Ojf9w@mail.gmail.com>
References: <CAP+sHjn_NDd_xv1vvgCYcXi2GJ6NDCkPks0HrKM=Sz+W+Ojf9w@mail.gmail.com>
Message-ID: <20140522120601.5287.1753760443.divmod.xquotient.48@top>

On 05:04 am, tavl at cin.ufpe.br wrote:
>Hello.
>
>Is there anything implemented in PyOpenSSL regarding OpenSSL engines? I 
>was
>checking cryptography code and I saw some references there to it. If
>PyOpenSSL doesn't support it, what would be the best way to add it?

There are no APIs in pyOpenSSL for manipulating engines at this time.

Jean-Paul

From richmoore44 at gmail.com  Thu May 22 14:23:34 2014
From: richmoore44 at gmail.com (Richard Moore)
Date: Thu, 22 May 2014 13:23:34 +0100
Subject: [pyOpenSSL-Users] OpenSSL Engine support
In-Reply-To: <20140522120601.5287.1753760443.divmod.xquotient.48@top>
References: <CAP+sHjn_NDd_xv1vvgCYcXi2GJ6NDCkPks0HrKM=Sz+W+Ojf9w@mail.gmail.com>
 <20140522120601.5287.1753760443.divmod.xquotient.48@top>
Message-ID: <CAMp7mVsnuWvbMgXA2+RORzwc5Og09b7xtpgQO8oWaQF=inMtkA@mail.gmail.com>

If you build openssl with the flag OPENSSL_LOAD_CONF then it will always
load the configuration file when it's initialised which means you can setup
and configure any openssl engines without requiring any API in pyopenssl.

Cheers

Rich.


On 22 May 2014 13:06, <exarkun at twistedmatrix.com> wrote:

> On 05:04 am, tavl at cin.ufpe.br wrote:
>
>> Hello.
>>
>> Is there anything implemented in PyOpenSSL regarding OpenSSL engines? I
>> was
>> checking cryptography code and I saw some references there to it. If
>> PyOpenSSL doesn't support it, what would be the best way to add it?
>>
>
> There are no APIs in pyOpenSSL for manipulating engines at this time.
>
> Jean-Paul
> _______________________________________________
> pyopenssl-users mailing list
> pyopenssl-users at python.org
> https://mail.python.org/mailman/listinfo/pyopenssl-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pyopenssl-users/attachments/20140522/e56a88d3/attachment.html>

From exarkun at twistedmatrix.com  Thu May 22 14:05:23 2014
From: exarkun at twistedmatrix.com (exarkun at twistedmatrix.com)
Date: Thu, 22 May 2014 12:05:23 -0000
Subject: [pyOpenSSL-Users] Extensions support in CRL object
In-Reply-To: <CAP+sHjn+RvJA1zc9a=FrADf2hw9KCoK11hb051XREa4X++3R2A@mail.gmail.com>
References: <CAP+sHjn+RvJA1zc9a=FrADf2hw9KCoK11hb051XREa4X++3R2A@mail.gmail.com>
Message-ID: <20140522120523.5287.585152990.divmod.xquotient.47@top>

On 04:59 am, tavl at cin.ufpe.br wrote:
>Hello all.
>
>How to add extensions to a crypto.CRL object? Is it possible? What 
>about
>the version attribute? If not, could someone, please, point me in the 
>best
>direction toward adding it to PyOpenSSL?

This feature is not available in pyOpenSSL at this time.

pyOpenSSL development takes place on github:

    https://github.com/pyca/pyopenssl

You can read about contributing here:

    https://github.com/pyca/pyopenssl/blob/master/CONTRIBUTING.rst

If you have any specific questions, don't hesitate to ask.

Thanks and good luck,
Jean-Paul

From imesgio at gmail.com  Sat May 24 02:55:39 2014
From: imesgio at gmail.com (Gio Zhu)
Date: Sat, 24 May 2014 08:55:39 +0800
Subject: [pyOpenSSL-Users] a question about OpenSSL.crypto.sign()
Message-ID: <001c01cf76ea$e6c92340$b45b69c0$@gmail.com>

Hi, all!

I am using Python3.3 along with "pyOpenSSL-0.14-py3.3.egg".  "cakey.pem" is
the key of the CA that I generate on my win7 PC using openSSL. But when I
run the program in Eclipse, it just stucked in "key =
load_privatekey(FILETYPE_PEM,
open("C:\\Users\\Gio\\SSL\\gioCA\\private\\cakey.pem").read())" giving no
reponse or errors.

Then I run it with command line, an error just occurred saying "TypeError:
initializer for ctype 'void *' must be a cdata pointer, not str". Later I
googled some documentations, and read some codes at the same time. But
there's some differences in the call of function sign(). In a documentation
of pyOpenSSL 0.14 defines OpenSSL.crypto.sign(key,data,digest). However, in
the local file "crypto.py", sign() is defined as sign(self,pkey,digest).

Which version is right?

Yours respectfully,

South China University of Technology,

Guangdong, China,

Gio Zhu

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pyopenssl-users/attachments/20140524/5ab563cc/attachment.html>