- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Mon, 21 Nov 2022 17:00:33 +0000
- To: public-webappsec@w3.org
- Message-Id: <E1oxA9p-008ohO-Qp@uranus.w3.org>
Issues
------
* w3c/webappsec-subresource-integrity (+2/-1/💬4)
2 issues created:
- Reference the IANA registry of hash names (by jb-wisemo)
https://github.com/w3c/webappsec-subresource-integrity/issues/119
- Check all hashes (by jb-wisemo)
https://github.com/w3c/webappsec-subresource-integrity/issues/118
3 issues received 4 new comments:
- #119 Reference the IANA registry of hash names (2 by annevk, mozfreddyb)
https://github.com/w3c/webappsec-subresource-integrity/issues/119
- #118 Check all hashes (1 by mozfreddyb)
https://github.com/w3c/webappsec-subresource-integrity/issues/118
- #68 integrity for downloads (1 by jb-wisemo)
https://github.com/w3c/webappsec-subresource-integrity/issues/68 [SRI-next] [feature-request]
1 issues closed:
- Reference the IANA registry of hash names https://github.com/w3c/webappsec-subresource-integrity/issues/119
* w3c/webappsec-csp (+1/-0/💬2)
1 issues created:
- Broken references in Content Security Policy Level 3 (by dontcallmedom-bot)
https://github.com/w3c/webappsec-csp/issues/576
2 issues received 2 new comments:
- #576 Broken references in Content Security Policy Level 3 (1 by mikewest)
https://github.com/w3c/webappsec-csp/issues/576
- #434 Clarify/test which quote characters may be used (1 by evilpie)
https://github.com/w3c/webappsec-csp/issues/434
* w3c/webappsec-upgrade-insecure-requests (+1/-0/💬1)
1 issues created:
- Specify value of Origin header (CORS) after a scheme upgrade (by Rob--W)
https://github.com/w3c/webappsec-upgrade-insecure-requests/issues/32
1 issues received 1 new comments:
- #32 Specify value of Origin header (CORS) after a scheme upgrade (1 by annevk)
https://github.com/w3c/webappsec-upgrade-insecure-requests/issues/32
* w3c/permissions-registry (+0/-0/💬1)
1 issues received 1 new comments:
- #17 Update "change process" now that <dfn permission> is a thing (1 by miketaylr)
https://github.com/w3c/permissions-registry/issues/17
* w3c/webappsec-cspee (+1/-0/💬0)
1 issues created:
- Broken references in Content Security Policy: Embedded Enforcement (by dontcallmedom-bot)
https://github.com/w3c/webappsec-cspee/issues/27
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/permissions-registry
* 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
* https://github.com/w3c/webappsec-permissions-policy
* https://github.com/w3c/webappsec-fetch-metadata
* https://github.com/w3c/webappsec-trusted-types
* https://github.com/w3c/webappsec-change-password-url
* https://github.com/w3c/webappsec-post-spectre-webdev
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 21 November 2022 17:00:35 UTC