Security Interest Group - Activity in 2019
No matches.
GitHub
w3c/security-questionnaire
-
1 issue opened.
-
Cite the source of the "concrete privacy concerns" w3c/security-questionnaire#71, by @jyasskin.
-
-
2 issues closed.
-
Add a reference to Secure Contexts? w3c/security-questionnaire#69.
-
Unclear which repository issues should be filed in. w3c/security-questionnaire#62.
-
-
1 issue reopened.
-
Cite the source of the "concrete privacy concerns" w3c/security-questionnaire#71, by @lknik.
-
-
3 issues received 4 new comments.
-
Should "drop the feature" be one of our recommended mitigation strategies w3c/security-questionnaire#48 (2 comments by @hober, @masinter)
-
Cite the source of the "concrete privacy concerns" w3c/security-questionnaire#71 (1 comment by @lknik)
-
Unclear which repository issues should be filed in. w3c/security-questionnaire#62 (1 comment by @lknik)
-
-
2 pull requests merged.
-
Remove outdated information w3c/security-questionnaire#68.
-
Update index.src.html w3c/security-questionnaire#67.
-
-
1 pull request received 1 new comment.
GitHub
w3c/security-questionnaire
-
1 pull request opened.
-
fix typos w3c/security-questionnaire#70, by @jasonanovak.
-
-
1 pull request merged.
-
fix typos w3c/security-questionnaire#70.
-
GitHub
w3c/security-questionnaire
-
1 issue opened.
-
Add a reference to Secure Contexts? w3c/security-questionnaire#69, by @Malvoz.
-
-
2 issues received 2 new comments.
-
Should "drop the feature" be one of our recommended mitigation strategies w3c/security-questionnaire#48 (1 comment by @dbaron)
-
1 pull request opened.
-
Remove outdated information w3c/security-questionnaire#68, by @Malvoz.
-
GitHub
w3c/security-questionnaire
-
2 issues opened.
-
Unclear which repository issues should be filed in. w3c/security-questionnaire#62, by @mkruisselbrink.
-
Geofencing link is not helpful w3c/security-questionnaire#61, by @vasilvv.
-
-
1 issue reopened.
-
Unclear which repository issues should be filed in. w3c/security-questionnaire#62, by @hober.
-
-
1 issue received 8 new comments.
-
Unclear which repository issues should be filed in. w3c/security-questionnaire#62 (8 comments by @hober, @lknik, @mkruisselbrink)
-
-
7 pull requests opened.
-
Update index.src.html w3c/security-questionnaire#67, by @lknik.
-
New bikeshed'd w3c/security-questionnaire#66, by @lknik.
-
Revert "Unify issue tracker in w3ctag repo" w3c/security-questionnaire#65, by @lknik.
-
Remove accidental "\" in heading. w3c/security-questionnaire#64, by @mkruisselbrink.
-
Unify issue tracker in w3ctag repo w3c/security-questionnaire#63, by @lknik.
-
Revert "Fix bullets in the audience section to be markdown." w3c/security-questionnaire#60, by @lknik.
-
Fix bullets in the audience section to be markdown. w3c/security-questionnaire#59, by @jasonanovak.
-
-
5 pull requests merged.
-
New bikeshed'd w3c/security-questionnaire#66.
-
Revert "Unify issue tracker in w3ctag repo" w3c/security-questionnaire#65.
-
Remove accidental "\" in heading. w3c/security-questionnaire#64.
-
Unify issue tracker in w3ctag repo w3c/security-questionnaire#63.
-
Fix bullets in the audience section to be markdown. w3c/security-questionnaire#59.
-
-
1 pull request closed.
-
Revert "Fix bullets in the audience section to be markdown." w3c/security-questionnaire#60.
-
-
1 pull request received 1 new comment.
GitHub
w3c/security-questionnaire
-
1 issue closed.
-
"editor's draft" stylesheet or cue? w3c/security-questionnaire#54.
-
-
2 issues received 5 new comments.
-
Should "drop the feature" be one of our recommended mitigation strategies w3c/security-questionnaire#48 (4 comments by @dbaron, @jyasskin, @lknik)
-
-
4 pull requests opened.
-
Fix most remaining bikeshed warnings and link errors. w3c/security-questionnaire#58, by @dbaron.
-
Fix running with bikeshed w3c/security-questionnaire#57, by @dbaron.
-
Spell check w3c/security-questionnaire#56, by @dbaron.
-
Change NOTE to ED w3c/security-questionnaire#55, by @lknik.
-
-
4 pull requests merged.
-
Fix most remaining bikeshed warnings and link errors. w3c/security-questionnaire#58.
-
Fix running with bikeshed w3c/security-questionnaire#57.
-
Spell check w3c/security-questionnaire#56.
-
Change NOTE to ED w3c/security-questionnaire#55.
-
-
2 pull requests received 2 new comments.
-
Fix most remaining bikeshed warnings and link errors. w3c/security-questionnaire#58 (1 comment by @lknik)
-
GitHub
w3c/security-questionnaire
-
1 issue opened.
-
"editor's draft" stylesheet or cue? w3c/security-questionnaire#54, by @koalie.
-
GitHub
w3c/security-questionnaire
-
3 issues closed.
-
Provide an example of a good "Security Considerations" and "Privacy Considerations" section w3c/security-questionnaire#25.
-
This document should ask the question that helps it improve w3c/security-questionnaire#26.
-
Introduction section needs to be more friendly w3c/security-questionnaire#46.
-
-
2 issues received 2 new comments.
-
[Meta] There should only be one issue tracker w3c/security-questionnaire#47 (1 comment by @samuelweiler)
-
5 pull requests opened.
-
updated/bikshed version w3c/security-questionnaire#53, by @lknik.
-
This will be a NOTE? w3c/security-questionnaire#52, by @lknik.
-
Swap old sections 3 (threars) with 4 (questions) w3c/security-questionnaire#51, by @lknik.
-
Merging 1/2, simplification w3c/security-questionnaire#50, by @lknik.
-
typo + remove link to jason's repo w3c/security-questionnaire#49, by @samuelweiler.
-
-
5 pull requests merged.
-
updated/bikshed version w3c/security-questionnaire#53.
-
This will be a NOTE? w3c/security-questionnaire#52.
-
Swap old sections 3 (threars) with 4 (questions) w3c/security-questionnaire#51.
-
Merging 1/2, simplification w3c/security-questionnaire#50.
-
typo + remove link to jason's repo w3c/security-questionnaire#49.
-
-
1 pull request received 1 new comment.
GitHub
w3c/security-questionnaire
-
3 issues opened.
-
Should "drop the feature" be one of our recommended mitigation strategies w3c/security-questionnaire#48, by @cynthia.
-
[Meta] There should only be one issue tracker w3c/security-questionnaire#47, by @hober.
-
Introduction section needs to be more friendly w3c/security-questionnaire#46, by @torgo.
-
-
1 issue closed.
-
[Meta] There should only be one issue tracker w3c/security-questionnaire#47.
-
-
4 issues received 11 new comments.
-
Should "drop the feature" be one of our recommended mitigation strategies w3c/security-questionnaire#48 (7 comments by @cynthia, @hober, @josephlhall, @lknik, @mnot, @slightlyoff)
-
[Meta] There should only be one issue tracker w3c/security-questionnaire#47 (2 comments by @hober, @lknik)
-
This document should ask the question that helps it improve w3c/security-questionnaire#26 (1 comment by @hober)
-
GitHub
w3c/security-questionnaire
-
16 issues closed.
-
merge 3.15 and 3.3 w3c/security-questionnaire#32.
-
Possible additional question 6 w3c/security-questionnaire#22.
-
Possible additional question 7 w3c/security-questionnaire#23.
-
3.6: what about style? w3c/security-questionnaire#30.
-
Possible additional question 5 w3c/security-questionnaire#21.
-
Possible additional question 1 w3c/security-questionnaire#17.
-
Possible additional question 2 w3c/security-questionnaire#18.
-
Possible additional question 3 w3c/security-questionnaire#19.
-
Possible additional question 4 w3c/security-questionnaire#20.
-
Low level system access w3c/security-questionnaire#10.
-
Consider mitigation for passive network attacker w3c/security-questionnaire#12.
-
Consider making all positive responses an elevation of risk w3c/security-questionnaire#13.
-
Order of per-origin vs cross-origin questions w3c/security-questionnaire#15.
-
How do we get additional review with the wider w3c community? w3c/security-questionnaire#16.
-
script (execution/loading) OR (script execution)/(loading) mechanisms w3c/security-questionnaire#3.
-
Clarify section 3.14 and add Third Party Tracking as an opt-in threat model w3c/security-questionnaire#7.
-
-
3 pull requests closed.
-
First whack at addressing local computing environment TODO. w3c/security-questionnaire#27.
-
Update status to NOTE w3c/security-questionnaire#14.
-
Formatting of index.src.html w3c/security-questionnaire#36.
-