-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Option to choose encryption algorithm #46
Comments
Is that for pgp or smime?
|
It's for SMIME @e3rd |
Good idea. If you re in a hurry, I ll welcome a pull request, otherwise, we
ll implement this (not earlier than in a month)
|
I'd love to, i already tried doing it but couldnt make it, here you can see cryptography package introduced following method to its PKCS7EnvelopeBuilder: set_content_encryption_algorithm in the doc it says, Added in version 43.0.0. Currently, cryptography is at version 44.0.1 and for some reason, this function is not available, it is available only in their main branch. So i couldn't figure out a way to use that. If there any other way to enforce AES256 encryption , i'd like to know your insights, so i can prepare a pr. I'm really in hurry and been stuck on this problem for 3 days, i have used hundreds of configurations (both in .py and .ts/node environments) to write a firebase cloud function to send a smime encrypted+signed mail but i cant succeed, i'd be really thankful if someone experienced like you could take a 5 minute on this ( i can contact you thru mail if available). It is a task with extremely short description but i just cant do it and stuck. |
The thing is, I m out of office completely.
If you seqrch for work around, go to the .local lib python sitepackages and
put there the code from their main branch instead of the version. That way
you can monkrypatch the situation for now and we can fix that permanently
when I m back.
|
I need to both encrypt and sign my S/MIME emails. When sending them via SMTP, I explicitly require AES-256 encryption, but I haven’t been able to find a way to do it.
The text was updated successfully, but these errors were encountered: