[power] simplify 2.1
[MIX] HTTPS -> non-HTTPS redirects
CfC: Publish a FPWD of "Requirements for Powerful Features"
- Re: CfC: Publish a FPWD of "Requirements for Powerful Features"
- Re: CfC: Publish a FPWD of "Requirements for Powerful Features"
[CSP] outbound links
"Requirements for Powerful Features" strawman.
- Re: "Requirements for Powerful Features" strawman.
- Re: "Requirements for Powerful Features" strawman.
- Re: "Requirements for Powerful Features" strawman.
- Re: "Requirements for Powerful Features" strawman.
- Re: "Requirements for Powerful Features" strawman.
- Re: "Requirements for Powerful Features" strawman.
- Re: "Requirements for Powerful Features" strawman.
- Re: "Requirements for Powerful Features" strawman.
- Re: "Requirements for Powerful Features" strawman.
- Re: "Requirements for Powerful Features" strawman.
- Re: "Requirements for Powerful Features" strawman.
- Re: "Requirements for Powerful Features" strawman.
- Re: "Requirements for Powerful Features" strawman.
- Re: "Requirements for Powerful Features" strawman.
- Re: "Requirements for Powerful Features" strawman.
- Re: "Requirements for Powerful Features" strawman.
[MIX] Interaction between HSTS and mixed content blocking
- Re: [MIX] Interaction between HSTS and mixed content blocking
- Re: [MIX] Interaction between HSTS and mixed content blocking
some testing on workers and sandbox
Call for consensus to move forward with proposed rechartering of WebAppSec WG
- Re: Call for consensus to move forward with proposed rechartering of WebAppSec WG
- Re: Call for consensus to move forward with proposed rechartering of WebAppSec WG
- Re: Call for consensus to move forward with proposed rechartering of WebAppSec WG
- Re: Call for consensus to move forward with proposed rechartering of WebAppSec WG
[MIX] Language improvement for authenticated origin defintiion
[MIX] link rel=icon
Re: webappsec-ISSUE-69 (Overt channel control in CSP): Consider directives to manage postMessage and external navigation of iframes [CSP Next]
webappsec-ISSUE-72 (Streaming Integrity): How to apply integrity verification to large / streaming downloads [Subresource Integrity Level 2]
webappsec-ACTION-207: Raise definition of sandboxed worker in html spec
webappsec-ACTION-206: Reply on referrer suggest imperative policy controls in serviceworker
webappsec-ACTION-205: Does link really violate csp guarantees?
webappsec-ACTION-204: Reply to mark watson that 1/2 of his issue is a last call comment to mix
webappsec-ACTION-203: Raise issue for sri large object /streaming integrity
webappsec-ACTION-202: Issue cfc on new draft charter
webappsec-ACTION-201: Add permissions api to draft charter
webappsec-ACTION-200: Investigate git issue tooling with other w3c groups
[webappsec] Agenda for Teleconference, Monday 17 Nov 2014
[Bug 27341] New: consider replacing integrity-metatata ABNF production with a precise prose definition of the datatype/microsyntax
[CSP] PING-- CSP vs. Fetch
[webappsec] "operator eval"
Netflix, MSE, and EME
TPAC survey
[MIX] Initial feedback on Mixed Content
- Re: [MIX] Initial feedback on Mixed Content
Call for Exclusions: Mixed Content
Rechartering: Permissions API
Re: Clarification of CSP sandbox and workers
[Bug 27302] New: Define an elaboration of #may-document-use-powerful-features that checks ancestor browsing contexts
Re: [MIX] RfC: WebAppSec's Last Call Working Draft of Mixed Content; deadline December 11
[MIX] RfC: WebAppSec's Last Call Working Draft of Mixed Content; deadline December 11
Re: RfC: WebAppSec's Last Call Working Draft of Mixed Content; deadline December 11
[webappsec] New W3C process and Last Call
- Re: [webappsec] New W3C process and Last Call
- Re: [webappsec] New W3C process and Last Call
- Re: [webappsec] New W3C process and Last Call
[webappsec] Draft charter for review
[Bug 27291] New: Referrer: Consider a mechanism to specify a referrer URL.
[webappsec] Rechartering: COWL
[webappsec] Rechartering: Entry Point Regulation (EPR)
Early morning thoughts on referrers.
[webappsec] Rechartering: additional cookie data
[webappsec] Rechartering: Web Authentication v.Next
[webappsec] Rechartering: Secure Introduction of Internet-Connected Things
[webappsec] Rechartering: sandboxed cross-origin workers
[webappsec] Rechartering: force secure-only child browsing contexts
- Re: [webappsec] Rechartering: force secure-only child browsing contexts
[webappsec] Rechartering: Sub-Origins
- Re: [webappsec] Rechartering: Sub-Origins
- Re: [webappsec] Rechartering: Sub-Origins
- Re: [webappsec] Rechartering: Sub-Origins
[webappsec] Rechartering: CSP Level 3
[webappsec] Rechartering: MIME-type sniffing
[webappsec] Rechartering: Write-Only Form Elements
[webappsec] Rechartering: Credential Management API
[CSP] <meta> clarifications
Should CSP affect a Notification icon?
- Re: Should CSP affect a Notification icon?
- Re: Should CSP affect a Notification icon?
[CSP] Clarifications regarding the HTTP LINK Header
- Re: [CSP] Clarifications regarding the HTTP LINK Header
- Re: [CSP] Clarifications regarding the HTTP LINK Header
- Re: [CSP] Clarifications regarding the HTTP LINK Header
- Re: [CSP] Clarifications regarding the HTTP LINK Header
- Re: [CSP] Clarifications regarding the HTTP LINK Header
- Re: [CSP] Clarifications regarding the HTTP LINK Header
- Re: [CSP] Clarifications regarding the HTTP LINK Header
- Re: [CSP] Clarifications regarding the HTTP LINK Header
- Re: [CSP] Clarifications regarding the HTTP LINK Header
- Re: [CSP] Clarifications regarding the HTTP LINK Header
- Re: [CSP] Clarifications regarding the HTTP LINK Header
- Re: [CSP] Clarifications regarding the HTTP LINK Header
- Re: [CSP] Clarifications regarding the HTTP LINK Header
- Re: [CSP] Clarifications regarding the HTTP LINK Header
- Re: [CSP] Clarifications regarding the HTTP LINK Header
- Re: [CSP] Clarifications regarding the HTTP LINK Header
- Re: [CSP] Clarifications regarding the HTTP LINK Header
- Re: [CSP] Clarifications regarding the HTTP LINK Header
- Re: [CSP] Clarifications regarding the HTTP LINK Header
- Re: [CSP] Clarifications regarding the HTTP LINK Header
- Re: [CSP] Clarifications regarding the HTTP LINK Header
- Re: [CSP] Clarifications regarding the HTTP LINK Header
Referrer Policy: Same-origin URIs
- Re: Referrer Policy: Same-origin URIs
Re: CfC: Mixed Content to Last Call?
Bug tracking
[CSP] URI/IRI normalization and comparison
[CSP] An outline of a taxonomy of CSP directives
[CSP] Problems with frame-ancestors; X-Frame-Options not obsolete?
Call for Exclusions (Update): Referrer Policy
[CSP] violation reports for sandbox
[CSP] Consistency of CSP hash-source with SRI regarding secure origins
[CSP] Clarifications on nonces
[CSP] Relative/absolute hostname matching
[CSP] URI Query part matching
WebRTC Security Assessment
Re: [SRI] To trust or not to trust a CDN
- Re: [SRI] To trust or not to trust a CDN
Re: [CSP] Additional report field: report-only: "true|false"
Re: [CSP] may we have script-ancestors to protect JSONP call
webappsec-ISSUE-71 (JSONP directives): Consider directives in CSP Level 3 to reduce attack surface of legacy JSONP interaces [CSP Level 3]
Re: [CSP] prevent 401 attach
Re: CSP: Problems with referrer and reflected-xss
webappsec-ISSUE-70 (Using ni:/// as CSP source): Investigate using ni:/// as a CSP source expression [CSP Next]
Re: Frame access
Re: [CSP] Implementer differences: window.open
Avoiding syncronous manifest requests in EPR
[webappsec] TPAC summary
[SRI] Escaping mixed-content blocking for video distribution
- Re: [SRI] Escaping mixed-content blocking for video distribution
- Re: [SRI] Escaping mixed-content blocking for video distribution
- Re: [SRI] Escaping mixed-content blocking for video distribution
- Re: [SRI] Escaping mixed-content blocking for video distribution
- Re: [SRI] Escaping mixed-content blocking for video distribution
- Re: [SRI] Escaping mixed-content blocking for video distribution
- Re: [SRI] Escaping mixed-content blocking for video distribution
- Re: [SRI] Escaping mixed-content blocking for video distribution
[SRI] may only be used in documents in secure origins
- Re: [SRI] may only be used in documents in secure origins
- Re: [SRI] may only be used in documents in secure origins
CSP3: DOM API Strawman
Re: [MIX] Modifications to script APIs
[webappsec] Agenda for Teleconference, Monday 03 Nov 2014
Re: Frame Ancestors and Referrer (Re: [webappsec] Call for Consensus: Stop work on Content Security Policy 1.0, transition to WG Note)
- Re: Frame Ancestors and Referrer (Re: [webappsec] Call for Consensus: Stop work on Content Security Policy 1.0, transition to WG Note)