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.

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

Incompatible signature format for openssl #1544

Open
phbelitz opened this issue Apr 3, 2020 · 0 comments
Open

Incompatible signature format for openssl #1544

phbelitz opened this issue Apr 3, 2020 · 0 comments

Comments

@phbelitz
Copy link

phbelitz commented Apr 3, 2020

Hey there. I'm currently working on a project, where I'm trying to contact the notary API, to get some trust data about docker images that is stored there. I want to verify the signature of this trust data on my own, with my local public keys, as a means to prevent man-in-the-middle attacks. I'm using the ecdsa python library for the signature verification and everything works out fine, but would like to switch to the cryptography library eventually, as it is way more powerful and uses openssl as backend. Unfortunately this doesn't work, as openssl does not accept the signatures notary provides. Apparently they are in a wrong format and are missing the ASN.1 frame around them. An exact example of what I'm trying to do can be found here. There you can see, the payload I'm trying to verify, is data that comes from notary. The answer by Nils Wisiol also further explains the whole openssl problematic.

My question/issue would be, can I somehow change the behavior of notary to create proper signatures, that are accepted by openssl? Or are you planning on changing this behavior in the future? Some input from you guys on this matter would be appreciated.

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

No branches or pull requests

1 participant