Hi, > > the reason is that cryptography (https://cryptography.io/en/latest/) > > only supports two states: unencrypted, and encrypted with its own > > choice of algorithm ("best available algorithm"): > > https://cryptography.io/en/latest/hazmat/primitives/asymmetric/serialization/#serialization-encryption-types > > > > Thank you, Felix! I guess I'll have to submit a pull > request[1]. Is there a particular reason Ansible is deprecating > pyOpenSSL? It seems it has more features and is still an active > project[2]. (The last change was not too long ago in November 2019.)
well, there's the big fat note in https://github.com/pyca/pyopenssl/blob/master/README.rst: > **Note:** The Python Cryptographic Authority **strongly suggests** the > use of pyca/cryptography where possible. If you are using pyOpenSSL for > anything other than making a TLS connection **you should move to > cryptography and drop your pyOpenSSL dependency**. Besides that, working with pyOpenSSL is really not that much fun. I'd rather get rid of the pyOpenSSL backends yesterday than somewhen in the future... Cheers, Felix -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/20200602235427.417d732c%40rovaniemi.
