-
Notifications
You must be signed in to change notification settings - Fork 5
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
feature: more attribute support #22
base: main
Are you sure you want to change the base?
Conversation
Hey @secDre4mer, thank you for opening the PR. I'll have a look at this soon. I'm curious about the |
Hey @hslatman , yes, you've described the use case well.
Defining this on the struct itself would make sense IMO, and returning a full
Maybe we can combine this? Like: Make One other issue with the current API, now that I'm looking at it: There's no way to iterate over all attributes (signed or unsigned) yet. Should I add some functions for this? |
b018e1a
to
c3bf0ff
Compare
Added |
Thank @secDre4mer for the update ! What do you think @hslatman ? |
Name of feature:
Support for reading / changing unsigned attributes
Pain or issue this feature alleviates:
Unsigned attributes can contain mutable information. E.g. adding a 2nd signature to a PKCS7 struct is done by adding an additional unsigned attribute that contains the PKCS7 for the secondary signature.
Why is this important to the project (if not answered above):
Reading and changing unsigned signatures is a valuable extension, especially since support for adding unsigned signatures at signing time already exists.
Is there documentation on how to use this feature? If so, where?
In what environments or workflows is this feature supported?
In what environments or workflows is this feature explicitly NOT supported (if any)?
Supporting links/other PRs/issues:
saferwall/pe#95
💔Thank you!