w3c/webappsec-cowl issues and pull requests

#81 - Mark spec as no longer being worked on? And archive this repo?

Issue - State: open - Opened by sideshowbarker over 3 years ago - 3 comments

#80 - What is the status of COWL?

Issue - State: open - Opened by bblfish almost 5 years ago - 1 comment

#79 - Giving Abdul push access to repo

Issue - State: closed - Opened by deian over 6 years ago - 2 comments

#78 - Fix build errors

Pull Request - State: closed - Opened by ak-14 over 6 years ago

#77 - Fix example 23 missing parens

Pull Request - State: closed - Opened by ak-14 over 6 years ago - 2 comments

#76 - Linked testing policy and fixed a few links

Pull Request - State: closed - Opened by plehegar over 6 years ago

#75 - Update sandboxing flags section

Pull Request - State: closed - Opened by ak-14 over 6 years ago

#74 - incumbent settings object?

Issue - State: open - Opened by ak-14 almost 7 years ago - 5 comments

#73 - example 23 is uggy

Issue - State: closed - Opened by deian almost 7 years ago - 1 comment

#72 - Fetching images dynamically pitfall

Issue - State: open - Opened by ak-14 almost 7 years ago - 1 comment

#71 - Should Privilege objects be serializable?

Issue - State: open - Opened by ak-14 almost 7 years ago

#70 - Use pr-review tool

Pull Request - State: closed - Opened by plehegar about 7 years ago

#69 - Tie in with feature policy?

Issue - State: open - Opened by deian about 7 years ago

#69 - Tie in with feature policy?

Issue - State: open - Opened by deian about 7 years ago

#68 - Chromium implementation tracking

Issue - State: open - Opened by deian about 7 years ago

#67 - Get APA review before CR

Issue - State: open - Opened by wseltzer over 7 years ago

#67 - Get APA review before CR

Issue - State: open - Opened by wseltzer over 7 years ago

#66 - Overly conservative check in step 8.4 of Algorithm 4.9

Issue - State: closed - Opened by deian about 8 years ago
Labels: bug

#65 - Specify how COWL deals with WebRTC

Issue - State: closed - Opened by deian about 8 years ago - 1 comment

#64 - Extend for Server-Sent Events

Issue - State: closed - Opened by NAndreasson about 8 years ago - 1 comment

#63 - Set top-level navigation sandbox flag

Issue - State: closed - Opened by NAndreasson about 8 years ago
Labels: bug, security

#62 - Leaks via DNS prefetching

Issue - State: open - Opened by deian about 8 years ago
Labels: enhancement, security, f2f-discuss

#62 - Leaks via DNS prefetching

Issue - State: open - Opened by deian about 8 years ago
Labels: enhancement, security, f2f-discuss

#61 - Specify how COWL deals with websockets

Issue - State: open - Opened by deian about 8 years ago - 2 comments
Labels: question, f2f-discuss

#60 - iFrame resizing as covert channel

Issue - State: open - Opened by NAndreasson about 8 years ago - 1 comment
Labels: security, f2f-discuss

#60 - iFrame resizing as covert channel

Issue - State: open - Opened by NAndreasson about 8 years ago - 1 comment
Labels: security, f2f-discuss

#59 - Fix wording for structured cloning of privileges

Issue - State: closed - Opened by deian about 8 years ago
Labels: clarification

#58 - Add sandboxed auxiliary navigation flag for confinement

Issue - State: closed - Opened by NAndreasson about 8 years ago

#57 - Fix receiving labeled objects in XHR extension

Issue - State: open - Opened by NAndreasson about 8 years ago - 3 comments
Labels: bug, security

#57 - Fix receiving labeled objects in XHR extension

Issue - State: open - Opened by NAndreasson about 8 years ago - 3 comments
Labels: bug, security

#56 - Extend Fetch API for labeled objects

Issue - State: open - Opened by NAndreasson about 8 years ago - 2 comments
Labels: enhancement, f2f-discuss

#55 - Clarify why both labeled data and labeled context directives are needed

Issue - State: closed - Opened by NAndreasson over 8 years ago - 2 comments
Labels: question, wontfix, clarification

#55 - Clarify why both labeled data and labeled context directives are needed

Issue - State: closed - Opened by NAndreasson over 8 years ago - 2 comments
Labels: question, wontfix, clarification

#54 - Allow header to omit integrity label

Issue - State: open - Opened by deian over 8 years ago
Labels: bug, f2f-discuss

#53 - Clarify algorithm for serialization of labels

Issue - State: closed - Opened by NAndreasson over 8 years ago - 2 comments
Labels: clarification

#52 - Make LabedObject label optional

Issue - State: closed - Opened by deian over 8 years ago
Labels: enhancement

#51 - Add a Gitter chat badge to README.md

Pull Request - State: closed - Opened by gitter-badger over 8 years ago

#51 - Add a Gitter chat badge to README.md

Pull Request - State: closed - Opened by gitter-badger over 8 years ago

#50 - Add a Gitter chat badge to README.md

Pull Request - State: closed - Opened by gitter-badger over 8 years ago

#50 - Add a Gitter chat badge to README.md

Pull Request - State: closed - Opened by gitter-badger over 8 years ago

#49 - LabeledObject specification

Issue - State: closed - Opened by NAndreasson over 8 years ago - 1 comment
Labels: enhancement

#49 - LabeledObject specification

Issue - State: closed - Opened by NAndreasson over 8 years ago - 1 comment
Labels: enhancement

#48 - Potential addition to context tainting algorithm

Issue - State: closed - Opened by NAndreasson over 8 years ago - 1 comment
Labels: enhancement

#48 - Potential addition to context tainting algorithm

Issue - State: closed - Opened by NAndreasson over 8 years ago - 1 comment
Labels: enhancement

#47 - Specify same-origin IPC vs. shared memory edgecase

Issue - State: closed - Opened by NAndreasson over 8 years ago - 3 comments
Labels: question, f2f-discuss

#46 - Motivate why top-level contexts shouldn't get stuck

Issue - State: closed - Opened by NAndreasson over 8 years ago
Labels: clarification

#45 - Make FreshPrivilege a NamedConstructor

Issue - State: open - Opened by deian over 8 years ago
Labels: enhancement

#45 - Make FreshPrivilege a NamedConstructor

Issue - State: open - Opened by deian over 8 years ago
Labels: enhancement

#44 - Should top-level pages be able to navigate arbitrarily?

Issue - State: closed - Opened by deian over 8 years ago - 3 comments
Labels: question, f2f-discuss

#44 - Should top-level pages be able to navigate arbitrarily?

Issue - State: closed - Opened by deian over 8 years ago - 3 comments
Labels: question, f2f-discuss

#43 - Restrict COWL to secure contexts

Issue - State: closed - Opened by deian over 8 years ago - 1 comment
Labels: enhancement, question, security

#42 - Specify how to deal with permissions

Issue - State: closed - Opened by deian over 8 years ago
Labels: question

#42 - Specify how to deal with permissions

Issue - State: closed - Opened by deian over 8 years ago
Labels: question

#41 - Specify how to deal with notifications

Issue - State: closed - Opened by deian over 8 years ago
Labels: enhancement, question, f2f-discuss

#40 - Change label format in headers

Issue - State: closed - Opened by deian over 8 years ago
Labels: enhancement, f2f-discuss

#40 - Change label format in headers

Issue - State: closed - Opened by deian over 8 years ago
Labels: enhancement, f2f-discuss

#39 - Make sure COWL's request header doesn't reintroduce referrer leaks

Issue - State: closed - Opened by deian over 8 years ago - 1 comment
Labels: question

#38 - Don't use origins for app-specific principals

Issue - State: closed - Opened by deian over 8 years ago
Labels: bug, enhancement

#38 - Don't use origins for app-specific principals

Issue - State: closed - Opened by deian over 8 years ago
Labels: bug, enhancement

#37 - Specify how COWL deals with push

Issue - State: closed - Opened by deian over 8 years ago
Labels: question

#37 - Specify how COWL deals with push

Issue - State: closed - Opened by deian over 8 years ago
Labels: question

#36 - Specify how COWL integrates with ServiceWorkers

Issue - State: closed - Opened by deian over 8 years ago - 1 comment
Labels: question, f2f-discuss

#35 - Parsing headers should fail close

Issue - State: closed - Opened by deian over 8 years ago

#35 - Parsing headers should fail close

Issue - State: closed - Opened by deian over 8 years ago

#34 - Don't allow over-tainting a top-level context

Issue - State: closed - Opened by deian over 8 years ago
Labels: enhancement

#34 - Don't allow over-tainting a top-level context

Issue - State: closed - Opened by deian over 8 years ago
Labels: enhancement

#33 - Disallow communication via obvious covert channels

Issue - State: open - Opened by deian over 8 years ago
Labels: bug, enhancement, security

#32 - #29 protected object of LabeledObject should be cloned

Pull Request - State: closed - Opened by deian over 8 years ago

#31 - Swap out-of-order words

Pull Request - State: closed - Opened by lawnsea over 8 years ago

#31 - Swap out-of-order words

Pull Request - State: closed - Opened by lawnsea over 8 years ago

#30 - Fix typo

Pull Request - State: closed - Opened by lawnsea over 8 years ago

#30 - Fix typo

Pull Request - State: closed - Opened by lawnsea over 8 years ago

#29 - Should a LabeledObject's protected object be cloned as well?

Issue - State: closed - Opened by lawnsea over 8 years ago - 2 comments
Labels: bug

#28 - Fix typo

Pull Request - State: closed - Opened by lawnsea over 8 years ago

#28 - Fix typo

Pull Request - State: closed - Opened by lawnsea over 8 years ago

#27 - Fix typo

Pull Request - State: closed - Opened by lawnsea over 8 years ago

#26 - Fix typo

Pull Request - State: closed - Opened by lawnsea over 8 years ago

#26 - Fix typo

Pull Request - State: closed - Opened by lawnsea over 8 years ago

#25 - proposal to address #24

Pull Request - State: closed - Opened by dret over 8 years ago - 2 comments

#25 - proposal to address #24

Pull Request - State: closed - Opened by dret over 8 years ago - 2 comments

#24 - HTTP Header Field sections

Issue - State: closed - Opened by dret over 8 years ago - 2 comments
Labels: enhancement

#24 - HTTP Header Field sections

Issue - State: closed - Opened by dret over 8 years ago - 2 comments
Labels: enhancement

#23 - Improve flow

Pull Request - State: closed - Opened by lawnsea over 8 years ago

#23 - Improve flow

Pull Request - State: closed - Opened by lawnsea over 8 years ago

#22 - Remove ambiguity

Pull Request - State: closed - Opened by lawnsea over 8 years ago

#22 - Remove ambiguity

Pull Request - State: closed - Opened by lawnsea over 8 years ago

#21 - Fix typos

Pull Request - State: closed - Opened by lawnsea over 8 years ago

#20 - Prepare for FPWD

Pull Request - State: closed - Opened by deian over 8 years ago - 1 comment

#19 - How should a server interpret multiple Sec-COWL headers?

Issue - State: closed - Opened by lawnsea over 8 years ago - 3 comments
Labels: enhancement

#19 - How should a server interpret multiple Sec-COWL headers?

Issue - State: closed - Opened by lawnsea over 8 years ago - 3 comments
Labels: enhancement

#18 - Sec-COWL request header possibly incompatible with RFC 2616

Issue - State: closed - Opened by lawnsea over 8 years ago - 2 comments
Labels: bug

#17 - Add missing article

Pull Request - State: closed - Opened by lawnsea over 8 years ago

#17 - Add missing article

Pull Request - State: closed - Opened by lawnsea over 8 years ago

#16 - Fix subject verb agreement and simplify sentence

Pull Request - State: closed - Opened by lawnsea over 8 years ago

#16 - Fix subject verb agreement and simplify sentence

Pull Request - State: closed - Opened by lawnsea over 8 years ago

#15 - Fix plurality

Pull Request - State: closed - Opened by lawnsea over 8 years ago

#15 - Fix plurality

Pull Request - State: closed - Opened by lawnsea over 8 years ago

#14 - Remove dupe word

Pull Request - State: closed - Opened by lawnsea over 8 years ago

#14 - Remove dupe word

Pull Request - State: closed - Opened by lawnsea over 8 years ago

#13 - Fix verb agreement

Pull Request - State: closed - Opened by lawnsea over 8 years ago

GitHub / w3c/webappsec-cowl issues and pull requests