W3C home > Mailing lists > Public > public-webappsec@w3.org > March 2021

Weekly github digest (WebAppSec specs)

From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
Date: Mon, 22 Mar 2021 17:00:28 +0000
To: public-webappsec@w3.org
Message-Id: <E1lONum-0006W2-Em@uranus.w3.org>



Issues
------
* w3c/webappsec-csp (+0/-1/💬3)
  2 issues received 3 new comments:
  - #472 More robust handling of non-executable <script> nodes (1 by arturjanc)
    https://github.com/w3c/webappsec-csp/issues/472 
  - #458 Accessing the `nonce` from JS, effectively makes all nonce based CSPs `strict-dynamic` (2 by arturjanc, ctidd)
    https://github.com/w3c/webappsec-csp/issues/458 

  1 issues closed:
  - More robust handling of non-executable <script> nodes https://github.com/w3c/webappsec-csp/issues/472 

* w3c/webappsec-mixed-content (+1/-0/💬1)
  1 issues created:
  - Clarify treatment of CORS-enabled requests (by letitz)
    https://github.com/w3c/webappsec-mixed-content/issues/50 

  1 issues received 1 new comments:
  - #50 Clarify treatment of CORS-enabled requests (1 by annevk)
    https://github.com/w3c/webappsec-mixed-content/issues/50 

* w3c/webappsec-credential-management (+1/-0/💬1)
  1 issues created:
  - Examples in the wild (by SilentImp)
    https://github.com/w3c/webappsec-credential-management/issues/164 

  1 issues received 1 new comments:
  - #164 Examples in the wild (1 by SilentImp)
    https://github.com/w3c/webappsec-credential-management/issues/164 

* w3c/webappsec-clear-site-data (+1/-0/💬2)
  1 issues created:
  - Status of Clear-Site-Data spec? Implementor interest? (by sideshowbarker)
    https://github.com/w3c/webappsec-clear-site-data/issues/71 

  1 issues received 2 new comments:
  - #71 Status of Clear-Site-Data spec? Implementor interest? (2 by annevk, sideshowbarker)
    https://github.com/w3c/webappsec-clear-site-data/issues/71 

* w3c/webappsec-suborigins (+1/-0/💬0)
  1 issues created:
  - Mark spec as no longer being worked on? And archive this repo? (by sideshowbarker)
    https://github.com/w3c/webappsec-suborigins/issues/81 

* w3c/webappsec-cspee (+1/-0/💬0)
  1 issues created:
  - Status of CSPEE spec? Implementor interest? (by sideshowbarker)
    https://github.com/w3c/webappsec-cspee/issues/19 

* w3c/webappsec-fetch-metadata (+2/-1/💬5)
  2 issues created:
  - Sec-Fetch-Site's use of "initiator" is misleading (by domenic)
    https://github.com/w3c/webappsec-fetch-metadata/issues/72 
  - Sec-Fetch-User and Sec-Fetch-Site for user-initiated UI navigations (by annevk)
    https://github.com/w3c/webappsec-fetch-metadata/issues/71 

  2 issues received 5 new comments:
  - #72 Sec-Fetch-Site's use of "initiator" is misleading (2 by domenic, mikewest)
    https://github.com/w3c/webappsec-fetch-metadata/issues/72 
  - #71 Sec-Fetch-User and Sec-Fetch-Site for user-initiated UI navigations (3 by annevk, arturjanc, domenic)
    https://github.com/w3c/webappsec-fetch-metadata/issues/71 

  1 issues closed:
  - Sec-Fetch-Site's use of "initiator" is misleading https://github.com/w3c/webappsec-fetch-metadata/issues/72 

* w3c/webappsec-unofficial-drafts (+1/-0/💬0)
  1 issues created:
  - Delete this repo? (by sideshowbarker)
    https://github.com/w3c/webappsec-unofficial-drafts/issues/1 

* w3c/webappsec-post-spectre-webdev (+0/-1/💬1)
  1 issues received 1 new comments:
  - #12 Why is Sec-Fetch-User not mentioned? (1 by arturjanc)
    https://github.com/w3c/webappsec-post-spectre-webdev/issues/12 

  1 issues closed:
  - Why is Sec-Fetch-User not mentioned? https://github.com/w3c/webappsec-post-spectre-webdev/issues/12 



Pull requests
-------------
* w3c/webappsec-csp (+4/-3/💬0)
  4 pull requests submitted:
  - Editorial: Use https URLs in README.md (by sideshowbarker)
    https://github.com/w3c/webappsec-csp/pull/485 
  - CI: (re)Drop Previous Version bikeshed metadata (by sideshowbarker)
    https://github.com/w3c/webappsec-csp/pull/484 
  - CI: Drop the Previous Version bikeshed metadata (by sideshowbarker)
    https://github.com/w3c/webappsec-csp/pull/483 
  - Adapt to the policy container (by antosart)
    https://github.com/w3c/webappsec-csp/pull/482 

  3 pull requests merged:
  - Editorial: Use https URLs in README.md
    https://github.com/w3c/webappsec-csp/pull/485 
  - CI: (re)Drop Previous Version bikeshed metadata
    https://github.com/w3c/webappsec-csp/pull/484 
  - CI: Drop the Previous Version bikeshed metadata
    https://github.com/w3c/webappsec-csp/pull/483 

* w3c/webappsec-mixed-content (+0/-0/💬1)
  1 pull requests received 1 new comments:
  - #49 Remove TR reference from MIX2 (1 by carlosjoan91)
    https://github.com/w3c/webappsec-mixed-content/pull/49 

* w3c/webappsec-cspee (+1/-0/💬0)
  1 pull requests submitted:
  - Update index.src.html (by ericlaw1979)
    https://github.com/w3c/webappsec-cspee/pull/20 

* w3c/webappsec-post-spectre-webdev (+4/-5/💬2)
  4 pull requests submitted:
  - Cite “A guide to enable cross-origin isolation” (by sideshowbarker)
    https://github.com/w3c/webappsec-post-spectre-webdev/pull/23 
  - Editorial: Set 'Level: none' in Bikeshed metadata (by sideshowbarker)
    https://github.com/w3c/webappsec-post-spectre-webdev/pull/22 
  - Editorial: Drop “site-isolation” dupe from biblio (by sideshowbarker)
    https://github.com/w3c/webappsec-post-spectre-webdev/pull/21 
  - Editorial: Fix a couple of typos/misspellings (by sideshowbarker)
    https://github.com/w3c/webappsec-post-spectre-webdev/pull/20 

  2 pull requests received 2 new comments:
  - #23 Cite “A guide to enable cross-origin isolation” (1 by mikewest)
    https://github.com/w3c/webappsec-post-spectre-webdev/pull/23 
  - #22 Editorial: Set 'Level: none' in Bikeshed metadata (1 by mikewest)
    https://github.com/w3c/webappsec-post-spectre-webdev/pull/22 

  5 pull requests merged:
  - Cite “A guide to enable cross-origin isolation”
    https://github.com/w3c/webappsec-post-spectre-webdev/pull/23 
  - Editorial: Set 'Level: none' in Bikeshed metadata
    https://github.com/w3c/webappsec-post-spectre-webdev/pull/22 
  - Editorial: Drop “site-isolation” dupe from biblio
    https://github.com/w3c/webappsec-post-spectre-webdev/pull/21 
  - Editorial: Fix a couple of typos/misspellings
    https://github.com/w3c/webappsec-post-spectre-webdev/pull/20 
  - Align repo-type with documented taxonomy
    https://github.com/w3c/webappsec-post-spectre-webdev/pull/18 


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
* 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-unofficial-drafts
* 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, 22 March 2021 17:00:31 UTC

This archive was generated by hypermail 2.4.0 : Monday, 22 March 2021 17:00:31 UTC