Skip to content

packdat/multiple signatures + improvements + eu digital signature compliant #7

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

Open
wants to merge 6 commits into
base: signature-feature
Choose a base branch
from

Conversation

matheus-kirchesch
Copy link

This PR is a continuation of the PR #5, I have made these changes to the custom PDF Sharp on our company private project, but thought of bringing it here also.

@matheus-kirchesch
Copy link
Author

@packdat , @julienrffr

@julienrffr
Copy link
Collaborator

julienrffr commented May 12, 2025

Hi @matheus-kirchesch
That's awesome, thank you for sharing!
I'll take a look when I have some time for sure.

Could you also open a PR to the original empira's PdfSharp repo? https://github.com/empira/PDFsharp
I guess now we will wait for the original repo to have a stable 6.2 PROD release (as it is now embedding signature feature) before integrating new features on our pdfsharp-extended branch/nuget. So we don't have a divergence too big.

// Sign the byte range
var contentInfo = new ContentInfo(range);
var signedCms = new SignedCms(contentInfo, true);
var signer = new CmsSigner(options.Certificate)/* { IncludeOption = X509IncludeOption.WholeChain }*/;
signer.UnsignedAttributes.Add(new Pkcs9SigningTime());
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can't remember right now but I think there was a reason to have it as an unsigned attribute.

Copy link
Author

@matheus-kirchesch matheus-kirchesch May 12, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not sure what this reason would be, but it makes sense to have it signed, it is the signature time and making it signed means it can not be changed

@matheus-kirchesch
Copy link
Author

Hi @matheus-kirchesch That's awesome, thank you for sharing! I'll take a look when I have some time for sure.

Could you also open a PR to the original empira's PdfSharp repo? https://github.com/empira/PDFsharp I guess now we will wait for the original repo to have a stable 6.2 PROD release (as it is now embedding signature feature) before integrating new features on our pdfsharp-extended branch/nuget. So we don't have a divergence too big.

Sure, you mean after they merge this PR? empira#48

@julienrffr
Copy link
Collaborator

@matheus-kirchesch 6.2.0 has just been released and it now natively includes the signature part.

I did not check yet if 6.2.0 already supports multiple signatures, but if it's not the case, work from @packdat and yours have to be rebased onto 6.2.0 in order to sync with native signature code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants