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

Add eab key example that enforces base64url #428

Closed
wants to merge 1 commit into from

Conversation

j0ru
Copy link
Contributor

@j0ru j0ru commented Jan 18, 2024

The acme rfc states that clients should interpret supplied eab keys as base64url. To encourage that behavior, this commit adds a key to the example configuration that is only decodable by base64url.

The acme rfc states that clients should interpret supplied eab keys as
base64url. To encourage that behaviour, this commit adds a key to the
example configuration that is only decodable by base64url.
@mcpherrinm
Copy link
Contributor

mcpherrinm commented May 1, 2024

pulled into #459 to use in EAB integration test

@mcpherrinm mcpherrinm closed this May 1, 2024
mcpherrinm added a commit that referenced this pull request May 1, 2024
During the go-jose/v4 upgrade, I accidentally required the same
signature sets for EAB as for the account keys, which is incorrect. This
allows the correct MAC-based algorithms. It drops the custom algorithm
checks, which are now unreachable as go-jose will enforce the
algorithms.

This also adds a new EAB key to Pebble's test config which explicitly
has base64url characters, from #428 

Fixes #455

---------

Co-authored-by: Folke Gleumes <folke@gleumes.org>
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.

None yet

2 participants