Skip to content

Conversation

@borisbsv
Copy link

After being frustrated for embarassingly long, I figured out that the JWT algorithm replacement attack only accepts actual public keys, not certs. I hope to spare someone else the headbanging.

Reworked the way public key files are ingested for the rsa/hs confusion
attack, so that passing a .509 certificate works as well.
This was done in order to equalise the behaviour with option "8: Verify
RSA sifnature against a Public Key", which accepts certificate .pem
files.
This changelist does not change the current behaviour of the tool - passing in a public key file still works as expected.

Reworked the way public key files are ingested for the rsa/hs confusion
attack, so that passing a .509 certificate works as well.
This was done in order to equalise the behaviour with option "8: Verify
RSA sifnature against a Public Key", which accepts certificate .pem
files.
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.

1 participant