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

Base64UrlSafe doesn't strip trailing = #9

Closed
kelunik opened this issue Sep 22, 2017 · 3 comments
Closed

Base64UrlSafe doesn't strip trailing = #9

kelunik opened this issue Sep 22, 2017 · 3 comments

Comments

@kelunik
Copy link

kelunik commented Sep 22, 2017

Base64Url doesn't have tailing = at the end, but Base64UrlSafe::encode produces those padding chars.

@paragonie-scott
Copy link
Member

Base64Url doesn't have trailing = at the end

Yes it does.

@paragonie-scott
Copy link
Member

I've added an encodeUnpadded() method to the base32 and base64 classes, for requirements that don't conform strictly to RFC 4648, so developers don't feel tempted to just rtrim($output, '='); since it's unknown if rtrim() is cache-timing-safe.

@paragonie-scott
Copy link
Member

New API methods are exposed in v2.2.0.

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

2 participants