From anthonyphis at gmail.com  Thu Feb  7 05:50:28 2019
From: anthonyphis at gmail.com (Antonio De Falco)
Date: Thu, 7 Feb 2019 11:50:28 +0100
Subject: [Cryptography-dev] Info Salsa20
Message-ID: <CADossYiw0mC+=8buG6HWX9W14Arrzvs+3DBEaKPCJGGV_BLtjQ@mail.gmail.com>

Hello,
I am a university student and for a project I was asked to integrate the
Salsa20 cipher into your library. But I noticed that the core of the
ciphers is invoked by OpenSSL, and since OpenSSL does not implement the
Salsa20 cipher, I wanted to ask you if an alternative way to integrate it
is possible.
Thank you
Best regards
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/cryptography-dev/attachments/20190207/b61b456f/attachment.html>

From cmcaine at gmail.com  Thu Feb  7 06:03:44 2019
From: cmcaine at gmail.com (Colin Caine)
Date: Thu, 7 Feb 2019 11:03:44 +0000
Subject: [Cryptography-dev] Info Salsa20
In-Reply-To: <13be88d5fe774ce48c0b25594c51ed0f@CASP08.ds.man.ac.uk>
References: <13be88d5fe774ce48c0b25594c51ed0f@CASP08.ds.man.ac.uk>
Message-ID: <CADwQTQbH-kh42e3PQTPdugaOQF3nyLZpQyxmKaGG1dT3bqmsAA@mail.gmail.com>

Salsa20 is implemented by nacl. You could link to that and throw an error
if the system doesn't have nacl.

(I am not a developer of this library, I don't know how they feel about
adding new c dependencies, but I'd guess not keen)

You could also just implement it in python, which will be a better learning
exercise, but may turn out to be too slow. Worth a try, though.


On Thu, 7 Feb 2019, 10:50 Antonio De Falco <anthonyphis at gmail.com wrote:

> Hello,
> I am a university student and for a project I was asked to integrate the
> Salsa20 cipher into your library. But I noticed that the core of the
> ciphers is invoked by OpenSSL, and since OpenSSL does not implement the
> Salsa20 cipher, I wanted to ask you if an alternative way to integrate it
> is possible.
> Thank you
> Best regards
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/cryptography-dev/attachments/20190207/a71644d4/attachment.html>

From paul.l.kehrer at gmail.com  Thu Feb  7 09:19:18 2019
From: paul.l.kehrer at gmail.com (Paul Kehrer)
Date: Thu, 7 Feb 2019 15:19:18 +0100
Subject: [Cryptography-dev] Info Salsa20
In-Reply-To: <CADwQTQbH-kh42e3PQTPdugaOQF3nyLZpQyxmKaGG1dT3bqmsAA@mail.gmail.com>
References: <13be88d5fe774ce48c0b25594c51ed0f@CASP08.ds.man.ac.uk>
 <CADwQTQbH-kh42e3PQTPdugaOQF3nyLZpQyxmKaGG1dT3bqmsAA@mail.gmail.com>
Message-ID: <CABj5TKTgNfCsxJSnZNznZ42RAijn+8jbXae36LGnrfnJtaP2kA@mail.gmail.com>

Yes, using pynacl to get salsa20 is what we would recommend.

-Paul

On February 7, 2019 at 7:59:41 AM, Colin Caine (cmcaine at gmail.com) wrote:

Salsa20 is implemented by nacl. You could link to that and throw an error
if the system doesn't have nacl.

(I am not a developer of this library, I don't know how they feel about
adding new c dependencies, but I'd guess not keen)

You could also just implement it in python, which will be a better learning
exercise, but may turn out to be too slow. Worth a try, though.


On Thu, 7 Feb 2019, 10:50 Antonio De Falco <anthonyphis at gmail.com wrote:

> Hello,
> I am a university student and for a project I was asked to integrate the
> Salsa20 cipher into your library. But I noticed that the core of the
> ciphers is invoked by OpenSSL, and since OpenSSL does not implement the
> Salsa20 cipher, I wanted to ask you if an alternative way to integrate it
> is possible.
> Thank you
> Best regards
>
_______________________________________________
Cryptography-dev mailing list
Cryptography-dev at python.org
https://mail.python.org/mailman/listinfo/cryptography-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/cryptography-dev/attachments/20190207/171e63b7/attachment.html>

From BKinsella at advantech-bb.com  Fri Feb  8 11:52:29 2019
From: BKinsella at advantech-bb.com (Ben Kinsella)
Date: Fri, 8 Feb 2019 16:52:29 +0000
Subject: [Cryptography-dev] Adding custom attributes to a CSR
Message-ID: <PU1PR02MB256920BF4014A233DD08238987690@PU1PR02MB2569.apcprd02.prod.outlook.com>

In pyOpenSSL and pyca/cryptography, I can't find any way to add custom attributes to a CSR.
i.e. I want to pass some extra information to the CA, but these will NOT appear as Extensions in the final cert.
Is this possible?

Regards,
Ben.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/cryptography-dev/attachments/20190208/49a82f84/attachment.html>

From alex.gaynor at gmail.com  Fri Feb  8 16:43:20 2019
From: alex.gaynor at gmail.com (Alex Gaynor)
Date: Fri, 8 Feb 2019 16:43:20 -0500
Subject: [Cryptography-dev] Adding custom attributes to a CSR
In-Reply-To: <PU1PR02MB256920BF4014A233DD08238987690@PU1PR02MB2569.apcprd02.prod.outlook.com>
References: <PU1PR02MB256920BF4014A233DD08238987690@PU1PR02MB2569.apcprd02.prod.outlook.com>
Message-ID: <CAFRnB2XBY2VaeBe_WTZHY9ObnQDW_9OKn+U5PRpf2ZGw9bsuKQ@mail.gmail.com>

Neither cryptography nor pyOpenSSL support CSR attributes. There is a long
standing issue about it: https://github.com/pyca/cryptography/issues/3384

Alex

On Fri, Feb 8, 2019 at 4:42 PM Ben Kinsella <BKinsella at advantech-bb.com>
wrote:

> In pyOpenSSL and pyca/cryptography, I can?t find any way to add custom
> attributes to a CSR.
>
> i.e. I want to pass some extra information to the CA, but these will NOT
> appear as Extensions in the final cert.
>
> Is this possible?
>
>
>
> Regards,
>
> Ben.
>
>
> _______________________________________________
> Cryptography-dev mailing list
> Cryptography-dev at python.org
> https://mail.python.org/mailman/listinfo/cryptography-dev
>


-- 
All that is necessary for evil to succeed is for good people to do nothing.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/cryptography-dev/attachments/20190208/8f01b76a/attachment.html>

From gmendoza at gmail.com  Mon Feb 11 19:06:55 2019
From: gmendoza at gmail.com (Gilbert Mendoza)
Date: Mon, 11 Feb 2019 16:06:55 -0800
Subject: [Cryptography-dev] x509 Certificate Fingerprint Format
Message-ID: <CAGCFJgB-e6JQE-tNDiHNJncVQvZjqxTBg_h4u4vv6r=oSMDLCQ@mail.gmail.com>

Greets!

I'm working with x509 certificates in Python, and I'm trying to see if
there's a more elegant approach to producing a fingerprint string that is
formatted similar to the OpenSSL fingerprint output.

openssl x509 -noout -fingerprint -sha1 -inform pem -in certificate.pem
SHA1 Fingerprint=76:E1:81:9F:AD:F0:6A:55:EF:4B:12:6A:2E:F7:43:C2:BA:E8:A1:51

Reading the documentation on the X.509 Certificate Object class [1], I
learned how to return the fingerprint value as a bytes object, which I then
converted to a hex string object, and then manipulated the string to look
like a colon separated fingerprint.

[1]
https://cryptography.io/en/latest/x509/reference/#x-509-certificate-object

cert = x509.load_pem_x509_certificate(pem_block, default_backend())

hash_bytes = cert.fingerprint(hashes.SHA1())
print(hash_bytes)
b'v\xe1\x81\x9f\xad\xf0jU\xefK\x12j.\xf7C\xc2\xba\xe8\xa1Q'

hash_hex = bytearray(cert.fingerprint(hashes.SHA1())).hex()
print(hash_hex)
76e1819fadf06a55ef4b126a2ef743c2bae8a151

hash = ":".join(hash_hex[i:i+2] for i in range(0,len(hash_hex),2)).upper()
print(hash)
76:E1:81:9F:AD:F0:6A:55:EF:4B:12:6A:2E:F7:43:C2:BA:E8:A1:51

So is there an easier way to get the fingerprint in this format, or am I
already there?

Many thanks in advance!

Gilbert
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/cryptography-dev/attachments/20190211/9e4cc396/attachment.html>

From python-cryptography at qu3.org  Tue Feb 12 06:39:42 2019
From: python-cryptography at qu3.org (Alexander Nigl)
Date: Tue, 12 Feb 2019 12:39:42 +0100
Subject: [Cryptography-dev] x509 Certificate Fingerprint Format
In-Reply-To: <CAGCFJgB-e6JQE-tNDiHNJncVQvZjqxTBg_h4u4vv6r=oSMDLCQ@mail.gmail.com>
References: <CAGCFJgB-e6JQE-tNDiHNJncVQvZjqxTBg_h4u4vv6r=oSMDLCQ@mail.gmail.com>
Message-ID: <0d54c801-e8e4-b627-3d69-bcfd9b241d5e@qu3.org>

Hi Gilbert,

I initially searched for a codec solution but this seems more like a
string formating exercise. Here is my short solution:

> cert = x509.load_pem_x509_certificate(pem_block, default_backend())
> 
> hash_bytes = cert.fingerprint(hashes.SHA1())
> print(hash_bytes)
> b'v\xe1\x81\x9f\xad\xf0jU\xefK\x12j.\xf7C\xc2\xba\xe8\xa1Q'

hash = ":".join([hex(h)[2:].upper() for h in hash_bytes])
print(hash)
'76:E1:81:9F:AD:F0:6A:55:EF:4B:12:6A:2E:F7:43:C2:BA:E8:A1:51'

Regards

Alexander

From gmendoza at gmail.com  Tue Feb 12 10:28:40 2019
From: gmendoza at gmail.com (Gilbert Mendoza)
Date: Tue, 12 Feb 2019 07:28:40 -0800
Subject: [Cryptography-dev] x509 Certificate Fingerprint Format
In-Reply-To: <0d54c801-e8e4-b627-3d69-bcfd9b241d5e@qu3.org>
References: <CAGCFJgB-e6JQE-tNDiHNJncVQvZjqxTBg_h4u4vv6r=oSMDLCQ@mail.gmail.com>
 <0d54c801-e8e4-b627-3d69-bcfd9b241d5e@qu3.org>
Message-ID: <CAGCFJgA_du+dC0m=6JKU=B8UhEo2rKOh3KgSaMxL-ed7bpPdwg@mail.gmail.com>

Thank you, Alexander. Your solution is much cleaner.  Your Python Kung Fu
is strong.  :-)

hash = ":".join([hex(h)[2:].upper() for h in hash_bytes])
> print(hash)
> '76:E1:81:9F:AD:F0:6A:55:EF:4B:12:6A:2E:F7:43:C2:BA:E8:A1:51'
>

Thanks, again!

Sincerely,

Gilbert
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/cryptography-dev/attachments/20190212/0c65ff65/attachment.html>

From andre.l.caron at gmail.com  Tue Feb 12 11:27:25 2019
From: andre.l.caron at gmail.com (=?UTF-8?B?QW5kcsOpIENhcm9u?=)
Date: Tue, 12 Feb 2019 11:27:25 -0500
Subject: [Cryptography-dev] x509 Certificate Fingerprint Format
In-Reply-To: <CAGCFJgA_du+dC0m=6JKU=B8UhEo2rKOh3KgSaMxL-ed7bpPdwg@mail.gmail.com>
References: <CAGCFJgB-e6JQE-tNDiHNJncVQvZjqxTBg_h4u4vv6r=oSMDLCQ@mail.gmail.com>
 <0d54c801-e8e4-b627-3d69-bcfd9b241d5e@qu3.org>
 <CAGCFJgA_du+dC0m=6JKU=B8UhEo2rKOh3KgSaMxL-ed7bpPdwg@mail.gmail.com>
Message-ID: <CALKBF2gAgm9xyM-XhiwuiN8s281pL1=S_GzpTcS8Nk25v4KsBA@mail.gmail.com>

FYI, you might also like this version:

Python 3:
':'.join('%02x' % b for b in s)

Python 2:
':'.join('%02x' % ord(b) for b in s)


On Tue, Feb 12, 2019 at 10:29 AM Gilbert Mendoza <gmendoza at gmail.com> wrote:

> Thank you, Alexander. Your solution is much cleaner.  Your Python Kung Fu
> is strong.  :-)
>
> hash = ":".join([hex(h)[2:].upper() for h in hash_bytes])
>> print(hash)
>> '76:E1:81:9F:AD:F0:6A:55:EF:4B:12:6A:2E:F7:43:C2:BA:E8:A1:51'
>>
>
> Thanks, again!
>
> Sincerely,
>
> Gilbert
> _______________________________________________
> Cryptography-dev mailing list
> Cryptography-dev at python.org
> https://mail.python.org/mailman/listinfo/cryptography-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/cryptography-dev/attachments/20190212/205b4a82/attachment.html>

From gmendoza at gmail.com  Tue Feb 12 11:36:09 2019
From: gmendoza at gmail.com (Gilbert Mendoza)
Date: Tue, 12 Feb 2019 08:36:09 -0800
Subject: [Cryptography-dev] x509 Certificate Fingerprint Format
In-Reply-To: <CALKBF2gAgm9xyM-XhiwuiN8s281pL1=S_GzpTcS8Nk25v4KsBA@mail.gmail.com>
References: <CAGCFJgB-e6JQE-tNDiHNJncVQvZjqxTBg_h4u4vv6r=oSMDLCQ@mail.gmail.com>
 <0d54c801-e8e4-b627-3d69-bcfd9b241d5e@qu3.org>
 <CAGCFJgA_du+dC0m=6JKU=B8UhEo2rKOh3KgSaMxL-ed7bpPdwg@mail.gmail.com>
 <CALKBF2gAgm9xyM-XhiwuiN8s281pL1=S_GzpTcS8Nk25v4KsBA@mail.gmail.com>
Message-ID: <CAGCFJgAk7DYA3t-=ZzLCDDmjVTSVuzu_m_C4vwP56qfcR5i=VA@mail.gmail.com>

Fancy!  :-)

Python 3:
> ':'.join('%02x' % b for b in s)
>
> Python 2:
> ':'.join('%02x' % ord(b) for b in s)
>

':'.join('%02x'.upper() % b for b in hash_bytes)

Works great!  Lot's of fun.

Thanks again,

Gilbert
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/cryptography-dev/attachments/20190212/35e9167d/attachment.html>

From python-cryptography at qu3.org  Tue Feb 12 16:18:13 2019
From: python-cryptography at qu3.org (Alexander Nigl)
Date: Tue, 12 Feb 2019 22:18:13 +0100
Subject: [Cryptography-dev] x509 Certificate Fingerprint Format
In-Reply-To: <CALKBF2gAgm9xyM-XhiwuiN8s281pL1=S_GzpTcS8Nk25v4KsBA@mail.gmail.com>
References: <CAGCFJgB-e6JQE-tNDiHNJncVQvZjqxTBg_h4u4vv6r=oSMDLCQ@mail.gmail.com>
 <0d54c801-e8e4-b627-3d69-bcfd9b241d5e@qu3.org>
 <CAGCFJgA_du+dC0m=6JKU=B8UhEo2rKOh3KgSaMxL-ed7bpPdwg@mail.gmail.com>
 <CALKBF2gAgm9xyM-XhiwuiN8s281pL1=S_GzpTcS8Nk25v4KsBA@mail.gmail.com>
Message-ID: <2a4ac87b-dc80-b750-2085-7bf756c65c60@qu3.org>

I take your

> Python 3:
> ':'.join('%02x' % b for b in s)

and raise you >=Python 3.6

':'.join(f'{b:02X}' for b in s)

Sry, had to do it ;)

Alexander

Ps: 02x is lowercase, 02X uppercase

From rsimmons0 at gmail.com  Tue Feb 12 16:52:29 2019
From: rsimmons0 at gmail.com (Robert Simmons)
Date: Tue, 12 Feb 2019 16:52:29 -0500
Subject: [Cryptography-dev] x509 Certificate Fingerprint Format
In-Reply-To: <2a4ac87b-dc80-b750-2085-7bf756c65c60@qu3.org>
References: <CAGCFJgB-e6JQE-tNDiHNJncVQvZjqxTBg_h4u4vv6r=oSMDLCQ@mail.gmail.com>
 <0d54c801-e8e4-b627-3d69-bcfd9b241d5e@qu3.org>
 <CAGCFJgA_du+dC0m=6JKU=B8UhEo2rKOh3KgSaMxL-ed7bpPdwg@mail.gmail.com>
 <CALKBF2gAgm9xyM-XhiwuiN8s281pL1=S_GzpTcS8Nk25v4KsBA@mail.gmail.com>
 <2a4ac87b-dc80-b750-2085-7bf756c65c60@qu3.org>
Message-ID: <CA+QLa9CHxYFDx7P_U5fFwc6hxMTKWVVAOuPZWpwYgPEtq-sAew@mail.gmail.com>

I raise you python 3.6+ using str.format() for best readability.
':'.join('{:2X}'.format(b) for b in s)

On Tue, Feb 12, 2019 at 4:18 PM Alexander Nigl <python-cryptography at qu3.org>
wrote:

> I take your
>
> > Python 3:
> > ':'.join('%02x' % b for b in s)
>
> and raise you >=Python 3.6
>
> ':'.join(f'{b:02X}' for b in s)
>
> Sry, had to do it ;)
>
> Alexander
>
> Ps: 02x is lowercase, 02X uppercase
> _______________________________________________
> Cryptography-dev mailing list
> Cryptography-dev at python.org
> https://mail.python.org/mailman/listinfo/cryptography-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/cryptography-dev/attachments/20190212/d53ad610/attachment.html>

From rsimmons0 at gmail.com  Tue Feb 12 16:54:01 2019
From: rsimmons0 at gmail.com (Robert Simmons)
Date: Tue, 12 Feb 2019 16:54:01 -0500
Subject: [Cryptography-dev] x509 Certificate Fingerprint Format
In-Reply-To: <CA+QLa9CHxYFDx7P_U5fFwc6hxMTKWVVAOuPZWpwYgPEtq-sAew@mail.gmail.com>
References: <CAGCFJgB-e6JQE-tNDiHNJncVQvZjqxTBg_h4u4vv6r=oSMDLCQ@mail.gmail.com>
 <0d54c801-e8e4-b627-3d69-bcfd9b241d5e@qu3.org>
 <CAGCFJgA_du+dC0m=6JKU=B8UhEo2rKOh3KgSaMxL-ed7bpPdwg@mail.gmail.com>
 <CALKBF2gAgm9xyM-XhiwuiN8s281pL1=S_GzpTcS8Nk25v4KsBA@mail.gmail.com>
 <2a4ac87b-dc80-b750-2085-7bf756c65c60@qu3.org>
 <CA+QLa9CHxYFDx7P_U5fFwc6hxMTKWVVAOuPZWpwYgPEtq-sAew@mail.gmail.com>
Message-ID: <CA+QLa9B93E32q5KLtObe3T2L-BjB0T2y1DSU+QLyaL9c=zh1Sw@mail.gmail.com>

And a tiny bug, so I lose. :)
':'.join('{:02X}'.format(b) for b in s)

On Tue, Feb 12, 2019 at 4:52 PM Robert Simmons <rsimmons0 at gmail.com> wrote:

> I raise you python 3.6+ using str.format() for best readability.
> ':'.join('{:2X}'.format(b) for b in s)
>
> On Tue, Feb 12, 2019 at 4:18 PM Alexander Nigl <
> python-cryptography at qu3.org> wrote:
>
>> I take your
>>
>> > Python 3:
>> > ':'.join('%02x' % b for b in s)
>>
>> and raise you >=Python 3.6
>>
>> ':'.join(f'{b:02X}' for b in s)
>>
>> Sry, had to do it ;)
>>
>> Alexander
>>
>> Ps: 02x is lowercase, 02X uppercase
>> _______________________________________________
>> Cryptography-dev mailing list
>> Cryptography-dev at python.org
>> https://mail.python.org/mailman/listinfo/cryptography-dev
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/cryptography-dev/attachments/20190212/c0398582/attachment.html>

From nirmal.kisan at gmail.com  Tue Feb 19 06:59:39 2019
From: nirmal.kisan at gmail.com (Nirmal Sarkar)
Date: Tue, 19 Feb 2019 17:29:39 +0530
Subject: [Cryptography-dev] Help to build shared libraries on cavium platform
Message-ID: <CACeX4O8VZLAR-Xx8n5+W-nfnt6m2vrW2SCHbjKS-ez1jX9iu=g@mail.gmail.com>

Hello,

I am working in a project where I need few libraries for cavium platform.

   1. cryptography/hazmat/bindings/_padding.so
   2. cryptography/hazmat/bindings/_openssl.so
   3. cryptography/hazmat/bindings/_constant_time.so
   4. nacl/_sodium.so
   5. bcrypt/_bcrypt.so
   6. .libs_cffi_backend/libffi-45372312.so.6.0.4
   7. _cffi_backend.so


I tried to find out both ? directly the .so files for cavium platform as
well as the source code from where I can build myself.

But I did not get these.

Can you please guide me on this ?



Regards,

Nirmal Sarkar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/cryptography-dev/attachments/20190219/3e5425d4/attachment.html>

From thomas.s.wolfsburg at freenet.de  Fri Feb 22 03:52:51 2019
From: thomas.s.wolfsburg at freenet.de (Thomas)
Date: Fri, 22 Feb 2019 09:52:51 +0100
Subject: [Cryptography-dev] Error with cryptography 2.5
Message-ID: <000001d4ca8b$feea4d60$fcbee820$@freenet.de>

Hello all.

 

I have a question about the compatibility of cryptography 2.5

 

I use Python 3.4.4 with current packages to create a proxy under the old
Windows XP.

Until now, this has worked flawlessly until and including cryptography
2.4.2.

 

With cryptography 2.5 I get an error reported back when running the Python
script (see also below).

 

File  "C:ProgrammePython34libsite-packagescryptographyhazmatbindingsope

Nsslbinding.py, "line 14, in <module>

    From cryptography.hazmat.bindings. _ openssl import ffi, lib

ImportError: DLL failed load: The specified module was not found.

 

Is this a flaw in cryptography?

Or has support for Python 3.4.4 already been discontinued?

 

Can I do something to continue using current packages of cryptography?

What else needs to be installed?

 

Thanks and regards

 

Thomas Schulze

 

 

 

 

(Original Text in German)

 

Ich habe eine Frage zur Kompatibilit?t von cryptography 2.5

 

Ich verwende Python 3.4.4 mit aktuellen Paketen, um unter dem alten Windows
XP einen Proxy zu erstellen.

Bisher funktionierte dies einwandfrei bis einschlie?lich cryptography 2.4.2.

 

Mit cryptography 2.5 bekomme ich bereits beim Ausf?hren der Python-Scripte
einen Fehler zur?ckgemeldet (siehe auch unten).

 

  File
"C:\Programme\Python34\lib\site-packages\cryptography\hazmat\bindings\ope

nssl\binding.py", line 14, in <module>

    from cryptography.hazmat.bindings._openssl import ffi, lib

ImportError: DLL load failed: Das angegebene Modul wurde nicht gefunden.

 

Ist das ein Fehler in cryptography?

Oder wurde die Unterst?tzung f?r Python 3.4.4 bereits eingestellt?

 

Kann ich etwas unternehmen, um weiterhin aktuelle Pakete von cryptography zu
verwenden?

Was mu? noch  installiert werden?

 

Danke, mit freundlichen Gr??en

 

Thomas Schulze

 

 

 

 

 

 

Console output with cryptography 2.4.2 (Proxy works correct)

 

============================================================================
==

  HTTPSProxy WinXP TLS1.2 support v1.5.2
2018-11-06

 

  cryptography v2.4.2  /  pyOpenSSL v19.0.0  /  urllib3 v1.24.1

 

  HTTPSProxy local client port: localhost:8080

 

  HTTPSProxy log send port: localhost:9020

============================================================================
==

 

Start logging:

 

 

 

 

 

 

Install cryptography 2.5 (incl.  idna)

 

Collecting cryptography[idna]

  Using cached
https://files.pythonhosted.org/packages/a7/5e/bd3cf6fda1860592d52

41ea2b8c6cc4e8c1fb4c576d30a8ab4d43f180121/cryptography-2.5-cp34-cp34m-win32.
whl

Collecting six>=1.4.1 (from cryptography[idna])

  Using cached
https://files.pythonhosted.org/packages/73/fb/00a976f728d0d1fecfe

898238ce23f502a721c0ac0ecfedb80e0d88c64e9/six-1.12.0-py2.py3-none-any.whl

Collecting asn1crypto>=0.21.0 (from cryptography[idna])

  Using cached
https://files.pythonhosted.org/packages/ea/cd/35485615f45f30a5105

76f1a56d1e0a7ad7bd8ab5ed7cdc600ef7cd06222/asn1crypto-0.24.0-py2.py3-none-any
.whl

 

Collecting cffi!=1.11.3,>=1.8 (from cryptography[idna])

  Using cached
https://files.pythonhosted.org/packages/0e/a6/1275e5c1b1af26a5048

b0a596aab56236ea4ff4119e0b89cb36180440d72/cffi-1.12.1-cp34-cp34m-win32.whl

Collecting idna>=2.1; extra == "idna" (from cryptography[idna])

  Using cached
https://files.pythonhosted.org/packages/14/2c/cd551d81dbe15200be1

cf41cd03869a46fe7226e7450af7a6545bfc474c9/idna-2.8-py2.py3-none-any.whl

Collecting pycparser (from cffi!=1.11.3,>=1.8->cryptography[idna])

Installing collected packages: six, asn1crypto, pycparser, cffi, idna,
cryptogra

phy

  Found existing installation: six 1.12.0

    Uninstalling six-1.12.0:

      Successfully uninstalled six-1.12.0

  Found existing installation: asn1crypto 0.24.0

    Uninstalling asn1crypto-0.24.0:

      Successfully uninstalled asn1crypto-0.24.0

  Found existing installation: pycparser 2.19

    Uninstalling pycparser-2.19:

      Successfully uninstalled pycparser-2.19

  Found existing installation: cffi 1.12.1

    Uninstalling cffi-1.12.1:

      Successfully uninstalled cffi-1.12.1

  Found existing installation: idna 2.8

    Uninstalling idna-2.8:

      Successfully uninstalled idna-2.8

  Found existing installation: cryptography 2.4.2

    Uninstalling cryptography-2.4.2:

      Successfully uninstalled cryptography-2.4.2

Successfully installed asn1crypto-0.24.0 cffi-1.12.1 cryptography-2.5
idna-2.8 p

ycparser-2.19 six-1.12.0

 

 

 

 

 

 

Console output with cryptography 2.5

 

Traceback (most recent call last):

  File "S:\2017-10-31 Projekt HTTPSProxy\3_3_1
HTTPSProxy_py_actual_test_and_bui

ld\HTTPSProxy.py", line 19, in <module>

    import OpenSSL

  File "C:\Programme\Python34\lib\site-packages\OpenSSL\__init__.py", line
8, in

<module>

    from OpenSSL import crypto, SSL

  File "C:\Programme\Python34\lib\site-packages\OpenSSL\crypto.py", line 16,
in

<module>

    from OpenSSL._util import (

  File "C:\Programme\Python34\lib\site-packages\OpenSSL\_util.py", line 6,
in <m

odule>

    from cryptography.hazmat.bindings.openssl.binding import Binding

  File
"C:\Programme\Python34\lib\site-packages\cryptography\hazmat\bindings\ope

nssl\binding.py", line 14, in <module>

    from cryptography.hazmat.bindings._openssl import ffi, lib

ImportError: DLL load failed: Das angegebene Modul wurde nicht gefunden.

 

 

 

 

 

 

All packages

 

altgraph==0.16.1

appdirs==1.4.3

asn1crypto==0.24.0

blessings==1.7

bpython==0.17.1

certifi==2018.11.29

cffi==1.12.1

chardet==3.0.4

colorama==0.4.1

configparser==3.7.1

cryptography==2.5

curtsies==0.3.0

dill==0.2.9

future==0.17.1

greenlet==0.4.15

idna==2.8

JsonForm==0.0.2

jsonschema==2.6.0

JsonSir==0.0.2

macholib==1.11

multiprocess==0.70.7

packaging==19.0

pefile==2018.8.8

pip==19.0.3

print==1.3.0

pyasn1==0.4.5

pycparser==2.19

Pygments==2.3.1

PyInstaller==3.4

pyOpenSSL==19.0.0

pyparsing==2.3.1

pyreadline==2.1

PySocks==1.6.8

Python-EasyConfig==0.1.7

pywin32==221

pywin32-ctypes==0.2.0

PyYAML==3.13

queuelib==1.5.0

requests==2.21.0

Resource==0.2.1

setuptools==40.8.0

six==1.12.0

typing==3.6.6

urllib3==1.24.1

wcwidth==0.1.7

wheel==0.33.1

 

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/cryptography-dev/attachments/20190222/2ba9c50a/attachment-0001.html>

From paul.l.kehrer at gmail.com  Fri Feb 22 18:21:41 2019
From: paul.l.kehrer at gmail.com (Paul Kehrer)
Date: Sat, 23 Feb 2019 07:21:41 +0800
Subject: [Cryptography-dev] Error with cryptography 2.5
In-Reply-To: <000001d4ca8b$feea4d60$fcbee820$@freenet.de>
References: <000001d4ca8b$feea4d60$fcbee820$@freenet.de>
Message-ID: <CDFE015F-7CBB-4FBE-91EC-2927DDEB5949@gmail.com>

What version of cffi do you have installed in your environment?

> On Feb 22, 2019, at 4:52 PM, Thomas <thomas.s.wolfsburg at freenet.de> wrote:
> 
> Hello all.
>  
> I have a question about the compatibility of cryptography 2.5
>  
> I use Python 3.4.4 with current packages to create a proxy under the old Windows XP.
> Until now, this has worked flawlessly until and including cryptography 2.4.2.
>  
> With cryptography 2.5 I get an error reported back when running the Python script (see also below).
>  
> File  "C:ProgrammePython34libsite-packagescryptographyhazmatbindingsope
> Nsslbinding.py, "line 14, in <module>
>     From cryptography.hazmat.bindings. _ openssl import ffi, lib
> ImportError: DLL failed load: The specified module was not found.
>  
> Is this a flaw in cryptography?
> Or has support for Python 3.4.4 already been discontinued?
>  
> Can I do something to continue using current packages of cryptography?
> What else needs to be installed?
>  
> Thanks and regards
>  
> Thomas Schulze
>  
>  
>  
>  
> (Original Text in German)
>  
> Ich habe eine Frage zur Kompatibilit?t von cryptography 2.5
>  
> Ich verwende Python 3.4.4 mit aktuellen Paketen, um unter dem alten Windows XP einen Proxy zu erstellen.
> Bisher funktionierte dies einwandfrei bis einschlie?lich cryptography 2.4.2.
>  
> Mit cryptography 2.5 bekomme ich bereits beim Ausf?hren der Python-Scripte einen Fehler zur?ckgemeldet (siehe auch unten).
>  
>   File "C:\Programme\Python34\lib\site-packages\cryptography\hazmat\bindings\ope
> nssl\binding.py", line 14, in <module>
>     from cryptography.hazmat.bindings._openssl import ffi, lib
> ImportError: DLL load failed: Das angegebene Modul wurde nicht gefunden.
>  
> Ist das ein Fehler in cryptography?
> Oder wurde die Unterst?tzung f?r Python 3.4.4 bereits eingestellt?
>  
> Kann ich etwas unternehmen, um weiterhin aktuelle Pakete von cryptography zu verwenden?
> Was mu? noch  installiert werden?
>  
> Danke, mit freundlichen Gr??en
>  
> Thomas Schulze
>  
>  
>  
>  
>  
>  
> Console output with cryptography 2.4.2 (Proxy works correct)
>  
> ==============================================================================
>   HTTPSProxy WinXP TLS1.2 support v1.5.2                            2018-11-06
>  
>   cryptography v2.4.2  /  pyOpenSSL v19.0.0  /  urllib3 v1.24.1
>  
>   HTTPSProxy local client port: localhost:8080
>  
>   HTTPSProxy log send port: localhost:9020
> ==============================================================================
>  
> Start logging:
>  
>  
>  
>  
>  
>  
> Install cryptography 2.5 (incl.  idna)
>  
> Collecting cryptography[idna]
>   Using cached https://files.pythonhosted.org/packages/a7/5e/bd3cf6fda1860592d52
> 41ea2b8c6cc4e8c1fb4c576d30a8ab4d43f180121/cryptography-2.5-cp34-cp34m-win32.whl
> Collecting six>=1.4.1 (from cryptography[idna])
>   Using cached https://files.pythonhosted.org/packages/73/fb/00a976f728d0d1fecfe
> 898238ce23f502a721c0ac0ecfedb80e0d88c64e9/six-1.12.0-py2.py3-none-any.whl
> Collecting asn1crypto>=0.21.0 (from cryptography[idna])
>   Using cached https://files.pythonhosted.org/packages/ea/cd/35485615f45f30a5105
> 76f1a56d1e0a7ad7bd8ab5ed7cdc600ef7cd06222/asn1crypto-0.24.0-py2.py3-none-any.whl
>  
> Collecting cffi!=1.11.3,>=1.8 (from cryptography[idna])
>   Using cached https://files.pythonhosted.org/packages/0e/a6/1275e5c1b1af26a5048
> b0a596aab56236ea4ff4119e0b89cb36180440d72/cffi-1.12.1-cp34-cp34m-win32.whl
> Collecting idna>=2.1; extra == "idna" (from cryptography[idna])
>   Using cached https://files.pythonhosted.org/packages/14/2c/cd551d81dbe15200be1
> cf41cd03869a46fe7226e7450af7a6545bfc474c9/idna-2.8-py2.py3-none-any.whl
> Collecting pycparser (from cffi!=1.11.3,>=1.8->cryptography[idna])
> Installing collected packages: six, asn1crypto, pycparser, cffi, idna, cryptogra
> phy
>   Found existing installation: six 1.12.0
>     Uninstalling six-1.12.0:
>       Successfully uninstalled six-1.12.0
>   Found existing installation: asn1crypto 0.24.0
>     Uninstalling asn1crypto-0.24.0:
>       Successfully uninstalled asn1crypto-0.24.0
>   Found existing installation: pycparser 2.19
>     Uninstalling pycparser-2.19:
>       Successfully uninstalled pycparser-2.19
>   Found existing installation: cffi 1.12.1
>     Uninstalling cffi-1.12.1:
>       Successfully uninstalled cffi-1.12.1
>   Found existing installation: idna 2.8
>     Uninstalling idna-2.8:
>       Successfully uninstalled idna-2.8
>   Found existing installation: cryptography 2.4.2
>     Uninstalling cryptography-2.4.2:
>       Successfully uninstalled cryptography-2.4.2
> Successfully installed asn1crypto-0.24.0 cffi-1.12.1 cryptography-2.5 idna-2.8 p
> ycparser-2.19 six-1.12.0
>  
>  
>  
>  
>  
>  
> Console output with cryptography 2.5
>  
> Traceback (most recent call last):
>   File "S:\2017-10-31 Projekt HTTPSProxy\3_3_1 HTTPSProxy_py_actual_test_and_bui
> ld\HTTPSProxy.py", line 19, in <module>
>     import OpenSSL
>   File "C:\Programme\Python34\lib\site-packages\OpenSSL\__init__.py", line 8, in
> <module>
>     from OpenSSL import crypto, SSL
>   File "C:\Programme\Python34\lib\site-packages\OpenSSL\crypto.py", line 16, in
> <module>
>     from OpenSSL._util import (
>   File "C:\Programme\Python34\lib\site-packages\OpenSSL\_util.py", line 6, in <m
> odule>
>     from cryptography.hazmat.bindings.openssl.binding import Binding
>   File "C:\Programme\Python34\lib\site-packages\cryptography\hazmat\bindings\ope
> nssl\binding.py", line 14, in <module>
>     from cryptography.hazmat.bindings._openssl import ffi, lib
> ImportError: DLL load failed: Das angegebene Modul wurde nicht gefunden.
>  
>  
>  
>  
>  
>  
> All packages
>  
> altgraph==0.16.1
> appdirs==1.4.3
> asn1crypto==0.24.0
> blessings==1.7
> bpython==0.17.1
> certifi==2018.11.29
> cffi==1.12.1
> chardet==3.0.4
> colorama==0.4.1
> configparser==3.7.1
> cryptography==2.5
> curtsies==0.3.0
> dill==0.2.9
> future==0.17.1
> greenlet==0.4.15
> idna==2.8
> JsonForm==0.0.2
> jsonschema==2.6.0
> JsonSir==0.0.2
> macholib==1.11
> multiprocess==0.70.7
> packaging==19.0
> pefile==2018.8.8
> pip==19.0.3
> print==1.3.0
> pyasn1==0.4.5
> pycparser==2.19
> Pygments==2.3.1
> PyInstaller==3.4
> pyOpenSSL==19.0.0
> pyparsing==2.3.1
> pyreadline==2.1
> PySocks==1.6.8
> Python-EasyConfig==0.1.7
> pywin32==221
> pywin32-ctypes==0.2.0
> PyYAML==3.13
> queuelib==1.5.0
> requests==2.21.0
> Resource==0.2.1
> setuptools==40.8.0
> six==1.12.0
> typing==3.6.6
> urllib3==1.24.1
> wcwidth==0.1.7
> wheel==0.33.1
>  
>  
>  
> _______________________________________________
> Cryptography-dev mailing list
> Cryptography-dev at python.org
> https://mail.python.org/mailman/listinfo/cryptography-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/cryptography-dev/attachments/20190223/1d8036cf/attachment-0001.html>

From alex.gaynor at gmail.com  Wed Feb 27 09:09:09 2019
From: alex.gaynor at gmail.com (Alex Gaynor)
Date: Wed, 27 Feb 2019 09:09:09 -0500
Subject: [Cryptography-dev] PyCA cryptography 2.6
Message-ID: <CAFRnB2Xs3ME984M6kR2s4sSNFF9745=i0-3O=K8cnR5MKkF6mA@mail.gmail.com>

PyCA cryptography 2.5 has been released to PyPI. cryptography includes both
high level recipes and low level interfaces to common cryptographic
algorithms such as symmetric ciphers, asymmetric algorithms, message
digests, X509, key derivation functions, and much more. We support Python
2.7, Python 3.4+, and PyPy.

Changelog (https://cryptography.io/en/latest/changelog/#v2-6):


   - *BACKWARDS INCOMPATIBLE:* Removed
   cryptography.hazmat.primitives.asymmetric.utils.encode_rfc6979_signature
    and
   cryptography.hazmat.primitives.asymmetric.utils.decode_rfc6979_signature,
   which had been deprecated for nearly 4 years. Use encode_dss_signature()
   <https://cryptography.io/en/latest/hazmat/primitives/asymmetric/utils/#cryptography.hazmat.primitives.asymmetric.utils.encode_dss_signature>
    and decode_dss_signature()
   <https://cryptography.io/en/latest/hazmat/primitives/asymmetric/utils/#cryptography.hazmat.primitives.asymmetric.utils.decode_dss_signature>
   instead.
   - *BACKWARDS INCOMPATIBLE*: Removed cryptography.x509.Certificate.serial,
   which had been deprecated for nearly 3 years. Use serial_number
   <https://cryptography.io/en/latest/x509/reference/#cryptography.x509.Certificate.serial_number>
    instead.
   - Updated Windows, macOS, and manylinux1 wheels to be compiled with
   OpenSSL 1.1.1b.
   - Added support for Ed448 signing
   <https://cryptography.io/en/latest/hazmat/primitives/asymmetric/ed448/> when
   using OpenSSL 1.1.1b or newer.
   - Added support for Ed25519 signing
   <https://cryptography.io/en/latest/hazmat/primitives/asymmetric/ed25519/>
when
   using OpenSSL 1.1.1b or newer.
   - load_ssh_public_key()
   <https://cryptography.io/en/latest/hazmat/primitives/asymmetric/serialization/#cryptography.hazmat.primitives.serialization.load_ssh_public_key>
can
   now load ed25519 public keys.
   - Add support for easily mapping an object identifier to its elliptic
   curve class viaget_curve_for_oid()
   <https://cryptography.io/en/latest/hazmat/primitives/asymmetric/ec/#cryptography.hazmat.primitives.asymmetric.ec.get_curve_for_oid>
   .
   - Add support for OpenSSL when compiled with the no-engine (
   OPENSSL_NO_ENGINE) flag.

Alex


-- 
All that is necessary for evil to succeed is for good people to do nothing.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/cryptography-dev/attachments/20190227/b2af73ac/attachment.html>

From paul.l.kehrer at gmail.com  Wed Feb 27 18:44:56 2019
From: paul.l.kehrer at gmail.com (Paul Kehrer)
Date: Wed, 27 Feb 2019 18:44:56 -0500
Subject: [Cryptography-dev] PyCA cryptography 2.6.1 released
Message-ID: <CABj5TKSAEH2kTj6e-MKG3vzqreK4t8Zi4CUU2f0EwN=s=M_REQ@mail.gmail.com>

PyCA cryptography 2.6.1 has been released to PyPI. cryptography includes
both high level recipes and low level interfaces to common cryptographic
algorithms such as symmetric ciphers, asymmetric algorithms, message
digests, X509, key derivation functions, and much more. We support Python
2.7, Python 3.4+, and PyPy.

Changelog (https://cryptography.io/en/latest/changelog/#v2-6-1):

* Resolved an error in our build infrastructure that broke our Python3
wheels for macOS and Linux.

-Paul Kehrer (reaperhulk)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/cryptography-dev/attachments/20190227/b07c4bda/attachment.html>