- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Mon, 24 Apr 2023 17:00:30 +0000
- To: public-webappsec@w3.org
- Message-Id: <E1pqzYE-00Fjku-8Q@uranus.w3.org>
Issues ------ * w3c/webappsec (+2/-3/💬4) 2 issues created: - suleymantokman92@gmail.com (by tokmansulo) https://github.com/w3c/webappsec/issues/623 - Planning 2023-05-17. (by mikewest) https://github.com/w3c/webappsec/issues/622 3 issues received 4 new comments: - #623 suleymantokman92@gmail.com (2 by tokmansulo) https://github.com/w3c/webappsec/issues/623 - #622 Planning 2023-05-17. (1 by plehegar) https://github.com/w3c/webappsec/issues/622 - #620 Planning the 2023-04-19. (1 by DCtheTall) https://github.com/w3c/webappsec/issues/620 3 issues closed: - suleymantokman92@gmail.com https://github.com/w3c/webappsec/issues/623 - suleymantokman92@gmail.com https://github.com/w3c/webappsec/issues/623 - Planning the 2023-04-19. https://github.com/w3c/webappsec/issues/620 * w3c/webappsec-subresource-integrity (+1/-1/💬2) 1 issues created: - base64-related requirements are broken (by annevk) https://github.com/w3c/webappsec-subresource-integrity/issues/121 2 issues received 2 new comments: - #60 Require that proxies do not modify integrity checked assets (1 by annevk) https://github.com/w3c/webappsec-subresource-integrity/issues/60 [question] - #49 SRI is a Rec! What next? (1 by annevk) https://github.com/w3c/webappsec-subresource-integrity/issues/49 1 issues closed: - SRI is a Rec! What next? https://github.com/w3c/webappsec-subresource-integrity/issues/49 * w3c/webappsec-csp (+0/-0/💬2) 2 issues received 2 new comments: - #592 host-char mismatches with the URL Standard (1 by clelland) https://github.com/w3c/webappsec-csp/issues/592 - #423 Inconsistent treatment of base64url-encoded hash sources in CSP vs SRI (1 by annevk) https://github.com/w3c/webappsec-csp/issues/423 * w3c/webappsec-credential-management (+1/-0/💬1) 1 issues created: - Prevent silent access flag is not used in algorithms (by npm1) https://github.com/w3c/webappsec-credential-management/issues/216 1 issues received 1 new comments: - #216 Prevent silent access flag is not used in algorithms (1 by npm1) https://github.com/w3c/webappsec-credential-management/issues/216 Pull requests ------------- * w3c/webappsec-csp (+0/-0/💬3) 2 pull requests received 3 new comments: - #597 Fix issue with host-matching and non-ascii hosts (2 by arichiv) https://github.com/w3c/webappsec-csp/pull/597 - #596 Revise port matching logic (1 by arichiv) https://github.com/w3c/webappsec-csp/pull/596 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, 24 April 2023 17:00:32 UTC