- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Mon, 26 Nov 2018 17:00:11 +0000
- To: public-webappsec@w3.org
- Message-Id: <E1gRKF1-0006AU-Jj@uranus.w3.org>
Issues
------
* w3c/webappsec-subresource-integrity (+0/-0/💬11)
2 issues received 11 new comments:
- #20 Consider integrity check violation reporting (9 by ScottHelme, mikewest, devd)
https://github.com/w3c/webappsec-subresource-integrity/issues/20
- #76 What about RDF ? (2 by mozfreddyb, awwright)
https://github.com/w3c/webappsec-subresource-integrity/issues/76
* w3c/webappsec-csp (+1/-1/💬17)
1 issues created:
- Make CSP inheritance for javascript: more explicit (by ckerschb)
https://github.com/w3c/webappsec-csp/issues/368
8 issues received 17 new comments:
- #368 Make CSP inheritance for javascript: more explicit (9 by annevk, mikewest, andypaicu)
https://github.com/w3c/webappsec-csp/issues/368
- #361 CSP 3 draft does not conform to the HTTP/1.1 standard for headers (2 by arturjanc, markushausammann)
https://github.com/w3c/webappsec-csp/issues/361
- #322 Handling of javascript: navigations is not interoperable, spec doesn't match most implementations (1 by andypaicu)
https://github.com/w3c/webappsec-csp/issues/322
- #323 Feature Request: Support for cross-domain downloads (1 by Malvoz)
https://github.com/w3c/webappsec-csp/issues/323
- #364 Initialize document CSP in html needs to be updated (1 by andypaicu)
https://github.com/w3c/webappsec-csp/issues/364
- #366 Bug in directive-value grammar (1 by andypaicu)
https://github.com/w3c/webappsec-csp/issues/366
- #367 Broken references in "Integration with Fetch" section (1 by andypaicu)
https://github.com/w3c/webappsec-csp/issues/367
- #87 Allow dynamically enabling/disabling unsafe-eval (1 by devd)
https://github.com/w3c/webappsec-csp/issues/87
1 issues closed:
- Broken references in "Integration with Fetch" section https://github.com/w3c/webappsec-csp/issues/367
* w3c/webappsec-clear-site-data (+1/-0/💬1)
1 issues created:
- [Q] What happens when "executionContexts" is present along with Location header? (by ashucg)
https://github.com/w3c/webappsec-clear-site-data/issues/56
1 issues received 1 new comments:
- #56 [Q] What happens when "executionContexts" is present along with Location header? (1 by annevk)
https://github.com/w3c/webappsec-clear-site-data/issues/56
Pull requests
-------------
* w3c/webappsec-csp (+3/-2/💬0)
3 pull requests submitted:
- image-src => img-src (by gapple)
https://github.com/w3c/webappsec-csp/pull/371
- Added javascript: scheme specifically and fixed a small comment (by andypaicu)
https://github.com/w3c/webappsec-csp/pull/370
- Updated references from main fetch (by andypaicu)
https://github.com/w3c/webappsec-csp/pull/369
2 pull requests merged:
- image-src => img-src
https://github.com/w3c/webappsec-csp/pull/371
- Updated references from main fetch
https://github.com/w3c/webappsec-csp/pull/369
Repositories tracked by this digest:
-----------------------------------
* https://github.com/w3c/webappsec
* https://github.com/w3c/webappsec-subresource-integrity
* https://github.com/w3c/webappsec-csp
* https://github.com/w3c/webappsec-mixed-content
* https://github.com/w3c/webappsec-upgrade-insecure-requests
* https://github.com/w3c/webappsec-credential-management
* https://github.com/w3c/permissions
* https://github.com/w3c/webappsec-referrer-policy
* https://github.com/w3c/webappsec-secure-contexts
* https://github.com/w3c/webappsec-clear-site-data
* https://github.com/w3c/webappsec-cowl
* https://github.com/w3c/webappsec-epr
* https://github.com/w3c/webappsec-suborigins
* https://github.com/w3c/webappsec-cspee
Received on Monday, 26 November 2018 17:00:13 UTC