-
Notifications
You must be signed in to change notification settings - Fork 139
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
PDF shows multiple document version for multiple signature #222
Comments
Is this really an issue? |
// PDFsharp - A .NET library for processing PDF using System.Security.Cryptography.X509Certificates; // The minimum assets version required. // When we add a timestamp to the digital signature, PDFsharp must access a timestamp server on the Internet. #if CORE // Create a signed document without a timestamp (which is very common). // PDFsharp 6.2 cannot add a timestamp when using .NET Framework. static async Task CreateSignedDocument(bool addTimestamp = false)
} static X509Certificate2 GetCertificate()
} Above is the code that i have to tried out. We want functionality that append two signature on page 1 with revision 1 for both. |
Could you elaborate on exactly why this is important for your workflow ? With the current implementation, this is not possible because saving and signing is done in an atomic operation; you cannot separate the two.
What you are asking for is to exclude multiple byte-ranges (i.e. signature-values) from the signature-calculation and by that diverging from what the spec recommends. Additionally, when allowing multiple byte-ranges in the way as described, you could potentially create something that would resemble some kind of "Schrödinger's PDF". Recommended approach: |
I have tried out to implement signature functionality, but when i have tried to sign document for one user which has around 2 pages it goes signed successfully but had two different version for documents, look on below image, it should only revision one for both the signature instead of rev.1 and rev.2
The text was updated successfully, but these errors were encountered: