Skip to content

base64-related requirements are broken #121

Open
@annevk

Description

@annevk

Let's track this part of #84 separately.

It's currently unclear what kind of base64 decoding is used and what kind of restrictions are enforced.

From code inspection in WebKit it appears that both base64 and base64url decoding are attempted, both without enforcing padding restrictions. That doesn't strike me as great from a security perspective. If we could model it as instead as encoding and then comparing for strict equality that would be vastly preferable, but there are some tests that would be impacted by this.

Corresponding CSP issue: w3c/webappsec-csp#423.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions