Skip to content
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.

Sign up for GitHub

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

Jump to bottom

FFI: add some API allowing to check whether signature is weak or why validation failed. #1809

Open
ni4 opened this issue Apr 26, 2022 · 1 comment · May be fixed by #2314
Open

FFI: add some API allowing to check whether signature is weak or why validation failed. #1809

ni4 opened this issue Apr 26, 2022 · 1 comment · May be fixed by #2314
Assignees
@ni4
Milestone
v0.18.0

Comments

@ni4
Copy link
Contributor

ni4 commented Apr 26, 2022 •
edited
Loading

Description

Users may wish to know why signature is marked as invalid (including cases with weak hash algorithm/public key algorithm/wrong subpackets/whatever else).
@ni4 ni4 added this to the v0.18.0 milestone Sep 17, 2024
@ni4
Copy link
Contributor Author

ni4 commented Sep 17, 2024

This could be done via some vector as field of the signature, which includes specific signature invalidation error codes, and FFI API which would allow to return those from the signature.

@ni4 ni4 self-assigned this Jan 27, 2025
@ni4 ni4 linked a pull request Feb 20, 2025 that will close this issue
Draft
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ni4 ni4

Labels
None yet
Projects
None yet
Milestone
v0.18.0
Development

Successfully merging a pull request may close this issue.

(WIP) FFI: add function to retrieve details on signature validation errors. rnpgp/rnp
1 participant
@ni4