Security Interest Group - Activity in 2015
No matches.
GitHub
w3c/security-questionnaire
-
2 issues opened.
-
How do we get additional review with the wider w3c community? w3c/security-questionnaire#16, by @torgo.
-
Order of per-origin vs cross-origin questions w3c/security-questionnaire#15, by @dontcallmedom.
-
-
1 issue received 1 new comment.
-
Need a "How to Use This Questionnaire" section w3c/security-questionnaire#5 (1 comment by @dontcallmedom)
-
-
1 pull request received 1 new comment.
GitHub
w3c/security-questionnaire
-
1 issue closed.
-
CSS3-UI Editor's draft updated with self-review answers to questionnaire w3c/security-questionnaire#1.
-
-
1 issue received 3 new comments.
-
1 pull request opened.
-
Update status to NOTE w3c/security-questionnaire#14, by @diracdeltas.
-
GitHub
w3c/security-questionnaire
-
4 issues opened.
-
Consider making all positive responses an elevation of risk w3c/security-questionnaire#13, by @jonathanKingston.
-
Consider mitigation for passive network attacker w3c/security-questionnaire#12, by @jonathanKingston.
-
Low level system access w3c/security-questionnaire#10, by @jonathanKingston.
-
Gender neutral pronouns w3c/security-questionnaire#9, by @jonathanKingston.
-
-
1 issue closed.
-
Gender neutral pronouns w3c/security-questionnaire#9.
-
-
3 issues received 11 new comments.
-
Gender neutral pronouns w3c/security-questionnaire#9 (5 comments by @jonathanKingston, @mikewest, @tabatkins)
-
Publish this at a versioned URL w3c/security-questionnaire#6 (4 comments by @mikewest, @plinss, @tantek)
-
-
1 pull request opened.
-
Changing wording to use gender neutral pronouns. w3c/security-questionnaire#11, by @jonathanKingston.
-
-
1 pull request merged.
-
Changing wording to use gender neutral pronouns. w3c/security-questionnaire#11.
-
-
1 pull request received 1 new comment.
-
Changing wording to use gender neutral pronouns. w3c/security-questionnaire#11 (1 comment by @mikewest)
-
GitHub
w3c/security-questionnaire
-
6 issues opened.
-
Clarify section 3.14 and add Third Party Tracking as an opt-in threat model w3c/security-questionnaire#7, by @diracdeltas.
-
Publish this at a versioned URL w3c/security-questionnaire#6, by @diracdeltas.
-
Need a "How to Use This Questionnaire" section w3c/security-questionnaire#5, by @mnot.
-
script (execution/loading) OR (script execution)/(loading) mechanisms w3c/security-questionnaire#3, by @tantek.
-
Inline issue links in current draft link to mikewest's repo, not w3ctag w3c/security-questionnaire#2, by @tantek.
-
CSS3-UI Editor's draft updated with self-review answers to questionnaire w3c/security-questionnaire#1, by @tantek.
-
-
1 issue closed.
-
Inline issue links in current draft link to mikewest's repo, not w3ctag w3c/security-questionnaire#2.
-
-
4 issues received 10 new comments.
-
Clarify section 3.14 and add Third Party Tracking as an opt-in threat model w3c/security-questionnaire#7 (5 comments by @diracdeltas, @mikeperry-tor, @mnot)
-
script (execution/loading) OR (script execution)/(loading) mechanisms w3c/security-questionnaire#3 (1 comment by @diracdeltas)
-
CSS3-UI Editor's draft updated with self-review answers to questionnaire w3c/security-questionnaire#1 (1 comment by @diracdeltas)
-
-
2 pull requests opened.
-
Add references to the w3ctag github repo w3c/security-questionnaire#8, by @diracdeltas.
-
Minor editorial suggestions w3c/security-questionnaire#4, by @mnot.
-
-
2 pull requests merged.
-
Add references to the w3ctag github repo w3c/security-questionnaire#8.
-
Minor editorial suggestions w3c/security-questionnaire#4.
-
-
1 pull request received 1 new comment.