-
Notifications
You must be signed in to change notification settings - Fork 35
Specify hash function naming #89
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
Comments
I think this is somewhat valid however the spec does make some differences in their usages. https://www.w3.org/TR/CSP2/#source-list-valid-hashes explains the mapping of However there is one other usage which is perhaps confusing:
I suspect these I think there are two points that seem valid here:
|
Ah I see there is #84 (comment) which covers most of my comment. That sentence is still an issue though. |
Can I convince you to send a PR? :)
…On Fri, Jan 3, 2020, 12:58 PM Jonathan Kingston ***@***.***> wrote:
Ah I see there is #84 (comment)
<#84 (comment)>
which covers most of my comment. That sentence is still an issue though.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#89?email_source=notifications&email_token=AABBOGKVPDHIDLUM5TGIBK3Q36RIPA5CNFSM4KCRWQF2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEICCEQY#issuecomment-570696259>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABBOGPUUA4KXXHPTEGKDX3Q36RIPANCNFSM4KCRWQFQ>
.
|
fixed per above. |
The current specification shows the example:
But elsewhere it refers to the same hash function as "SHA-384". Please specify which spelling is normative.
The text was updated successfully, but these errors were encountered: