issues
search
WICG
/
signature-based-sri
Signature-based Resource Loading Restrictions
https://wicg.github.io/signature-based-sri/
Other
20
stars
2
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Add deployment scenarios section to document two primary use cases for signature-based SRI
#24
ddworken
opened
18 hours ago
0
Allow enforcement of _all_ rather than _any_ signature matches.
#23
mikewest
opened
20 hours ago
0
Public key discoverability
#22
ddworken
opened
1 day ago
4
Public keys in request headers
#21
ddworken
opened
1 day ago
2
Multiple signature support
#20
ddworken
closed
20 hours ago
6
Signatures and hashes
#19
yoavweiss
opened
1 day ago
6
Shifting to a Structured Header-like syntax?
#18
mikewest
opened
1 day ago
7
CORS integration
#17
annevk
opened
1 day ago
6
Signature representation.
#16
mikewest
opened
1 day ago
5
Moving demo/server.py to Python3
#15
Frosne
closed
2 days ago
0
Add CSP-Reporting into the example
#14
NL-William
closed
1 day ago
1
Support PGP
#13
NL-William
closed
2 years ago
1
`require-sri-for` removed from the SRI spec
#12
Malvoz
closed
1 day ago
2
Make resource identifier part of signed contents
#11
aidantwoods
opened
6 years ago
0
Inline scripts, CSP, and SRI
#10
devd
opened
6 years ago
2
Allow a default public key to use
#9
devd
opened
6 years ago
3
Key Rotation/Multiple keys
#8
devd
closed
1 day ago
0
Not CDNs
#7
mnot
closed
7 years ago
1
The explainer should live at only 1 url.
#6
jyasskin
opened
7 years ago
4
Signed content should include resource names
#5
jyasskin
opened
7 years ago
14
How does this interact with CSP?
#4
otherdaniel
closed
1 day ago
3
Who Is Strongest?
#3
otherdaniel
closed
1 day ago
3
Integrity Signature Header is Under-Specified
#2
otherdaniel
closed
1 day ago
4
crossorigin attribute is not optional
#1
annevk
closed
7 years ago
0