- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Mon, 09 Jul 2018 17:00:08 +0000
- To: public-webappsec@w3.org
- Message-Id: <E1fcZWC-0008SX-Qx@uranus.w3.org>
Issues ------ * w3c/webappsec-csp (+1/-0/💬3) 1 issues created: - CSP policy is visible in response header (by ashok003) https://github.com/w3c/webappsec-csp/issues/317 2 issues received 3 new comments: - #255 Prevent CSP reports being sent if I handle the SecurityPolicyViolation event. (2 by koto, andypaicu) https://github.com/w3c/webappsec-csp/issues/255 - #309 'strict-dynamic' should not be bound to only nonces/hashes (1 by arturjanc) https://github.com/w3c/webappsec-csp/issues/309 * w3c/permissions (+1/-0/💬0) 1 issues created: - Automation: "Get Permission" (by jugglinmike) https://github.com/w3c/permissions/issues/180 * w3c/webappsec-referrer-policy (+1/-0/💬0) 1 issues created: - Referrer-Policy header: "strict-same-origin" value (by baptx) https://github.com/w3c/webappsec-referrer-policy/issues/114 * w3c/webappsec-secure-contexts (+0/-0/💬3) 1 issues received 3 new comments: - #60 Using secure-context gated features with local devices (3 by pinobatch, curry684) https://github.com/w3c/webappsec-secure-contexts/issues/60 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
Received on Monday, 9 July 2018 17:00:11 UTC