-
Notifications
You must be signed in to change notification settings - Fork 93
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
regression from >1.4.x (Python3.8) #56
Comments
Yes, the changes are big. The PyPDF2 library is used to create pdf files, and it requires strings, not bytestrings - now you can use ttfs to create a signature with national characters. There is one more parameter "aligned" and if it is equal to 0, the signature has a minimum size, set this parameter to e.g. 16384, you will get a similar file size as in the previous version but you have to take care of the size of this buffer yourself. Try to sign with examples/pdf-sign-cms.py, if you still have errors send both files - signed and unsigned. I don't know anything without them. |
hi @m32 ; I can confirm that setting the However, the signature will still not be recognised by e.g. LibeOffice Impress; looking into the sources of the output PDF, it looks right. I tried adding all of the optional parameters to the |
Add demo2_ca.crt.pem to trusted certificates in your browser. Without this, the document shows up as a blank page and libreoffice says the sign is ok, but it cannot be verified. |
There was an incompatible change for versions of endesive
> 1.4.5
(starting with1.5.0
).working code for
1.4.5
:starting with
1.5.0
, the dict values are expected asstr
s - no problem, changed that.After doing those adjustments, however, the resulting PDF signature is significantly smaller than with
1.4.x
. They are no longer recognised, e.g. by LibreOffice Impress.After looking through the inline-documentation + Code, I could not figure out what else I need to adjust. So my assumption is that this is a bug
The text was updated successfully, but these errors were encountered: