-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
SEC: Switch to AES for encryption #1754
Labels
nf-security
Non-functional change: Security
Comments
MartinThoma
added a commit
that referenced
this issue
Mar 28, 2023
MartinThoma
added a commit
that referenced
this issue
Mar 29, 2023
Is this mean pypdf can do AES decryption without external dependencies? If so, I thought even decryption would only be possible with PyCryptodome. |
That is correct |
MartinThoma
added a commit
that referenced
this issue
Jul 2, 2023
MartinThoma
added a commit
that referenced
this issue
Jul 2, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, pypdf uses the security handler revision number 3 (R=3) and V=2. That means:
RC4 is not secure (source). At the very least we should issue a big warning + document this behavior. By default, we should use secure encryption methods
AES encryption is not implemented so far. Only decryption.
The text was updated successfully, but these errors were encountered: