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

Weekly github digest (WebAppSec specs)

From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
Date: Mon, 04 Mar 2019 17:00:19 +0000
To: public-webappsec@w3.org
Message-Id: <E1h0qwt-0007Yt-OA@uranus.w3.org>



Issues
------
* w3c/webappsec (+0/-0/💬1)
  1 issues received 1 new comments:
  - #538 Distrusting the web server (1 by leo-lb)
    https://github.com/w3c/webappsec/issues/538 

* w3c/webappsec-subresource-integrity (+0/-0/💬6)
  2 issues received 6 new comments:
  - #44 Extend SRI to support integrity metadata on inline script/style blocks (4 by annevk, jhabdas)
    https://github.com/w3c/webappsec-subresource-integrity/issues/44 
  - #77 A new IntegrityCheckFailure event (2 by annevk, cvazac)
    https://github.com/w3c/webappsec-subresource-integrity/issues/77 

* w3c/webappsec-csp (+1/-0/💬0)
  1 issues created:
  - Missing description in the Spec for Level 3 (by ayumihamsaki)
    https://github.com/w3c/webappsec-csp/issues/386 

* w3c/webappsec-credential-management (+1/-0/💬0)
  1 issues created:
  - What can be passed as fetch() credentials? (by lgarron)
    https://github.com/w3c/webappsec-credential-management/issues/133 

* w3c/webappsec-clear-site-data (+1/-1/💬2)
  1 issues created:
  - Can you only run this API using HTTPs? (by ayumihamsaki)
    https://github.com/w3c/webappsec-clear-site-data/issues/58 

  1 issues received 2 new comments:
  - #58 Can you only run this API using HTTPs? (2 by mikewest, ayumihamsaki)
    https://github.com/w3c/webappsec-clear-site-data/issues/58 

  1 issues closed:
  - Can you only run this API using HTTPs? https://github.com/w3c/webappsec-clear-site-data/issues/58 

* w3c/webappsec-feature-policy (+0/-0/💬20)
  6 issues received 20 new comments:
  - #281 Policy proposal for unsolicited-permission-request (5 by mounirlamouri, triblondon, clelland, mustaqahmed)
    https://github.com/w3c/webappsec-feature-policy/issues/281 
  - #279 Visibility/Testability of policy interventions (4 by triblondon, clelland, loonybear)
    https://github.com/w3c/webappsec-feature-policy/issues/279 
  - #197 consider whether inverting color is the right enforcement behavior for image policies (3 by clelland, loonybear, eeeps)
    https://github.com/w3c/webappsec-feature-policy/issues/197 
  - #282 Proposal: Define new feature types (3 by annevk, triblondon, clelland)
    https://github.com/w3c/webappsec-feature-policy/issues/282 
  - #189 Proposal: define default for all (3 by Salamander3, ojanvafai, sstelfox)
    https://github.com/w3c/webappsec-feature-policy/issues/189 
  - #280 Feature Policy: Service Worker fetch handling (2 by mattto, clelland)
    https://github.com/w3c/webappsec-feature-policy/issues/280 



Pull requests
-------------
* w3c/webappsec-feature-policy (+1/-1/💬0)
  1 pull requests submitted:
  - fix typo in ReportingObserver example (by paulirish)
    https://github.com/w3c/webappsec-feature-policy/pull/283 

  1 pull requests merged:
  - fix typo in ReportingObserver example
    https://github.com/w3c/webappsec-feature-policy/pull/283 


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-feature-policy
Received on Monday, 4 March 2019 17:00:21 UTC

This archive was generated by hypermail 2.3.1 : Monday, 4 March 2019 17:00:22 UTC