public-wsc-wg@w3.org from January 2008 by date

Thursday, 31 January 2008

• » Even SSL Gmail can get sidejacked | Zero Day | ZDNet.com Yngve Nysaeter Pettersen
• Re: ACTION-380: Text for ISSUE-131 Thomas Roessler
• Re: ACTION-380: Text for ISSUE-131 Ian Fette
• ACTION-381: ISSUE-130 (consistent across devices) done Thomas Roessler
• ACTION-380: Text for ISSUE-131 Thomas Roessler

Wednesday, 30 January 2008

• Please review ACTION-367 results Thomas Roessler
• Re: Agenda: WSC WG weekly 2008-01-30 Serge Egelman
• ACTION-360: Mez's editorial nits; petnames in identity signal? Thomas Roessler

Tuesday, 29 January 2008

• RE: Agenda: WSC WG weekly 2008-01-30 Dan Schutzer
• weekly call on 30 January Timothy Hahn
• Re: Agenda: WSC WG weekly 2008-01-30 Johnathan Nightingale
• Agenda: WSC WG weekly 2008-01-30 Thomas Roessler
• Regrets for Jan-30 call Hal Lockhart

Saturday, 26 January 2008

• Re: ACTION-334: Propose language on Bookmarks API Thomas Roessler
• ACTION-334: Propose language on Bookmarks API Anil Saldhana
• Re: IE Favorites Feature May Allow Phishing Anil Saldhana

Friday, 25 January 2008

• ACTION-373 Poll al G about shoulder surfing attacks in context of assistive technologies Mary Ellen Zurko

Thursday, 24 January 2008

• RE: ACTION-374 - proposed re-written text for 6.3, Page Security Score Mary Ellen Zurko
• Re: ACTION-374 - proposed re-written text for 6.3, Page Security Score Johnathan Nightingale
• Re: Troubles with KCM Ian Fette
• RE: ACTION-374 - proposed re-written text for 6.3, Page Security Score William Eburn
• RE: ACTION-374 - proposed re-written text for 6.3, Page Security Score michael.mccormick@wellsfargo.com
• Re: ACTION-374 - proposed re-written text for 6.3, Page Security Score Serge Egelman
• Re: ACTION-374 - proposed re-written text for 6.3, Page Security Score Serge Egelman
• Re: ACTION-374 - proposed re-written text for 6.3, Page Security Score Ian Fette
• RE: ACTION-374 - proposed re-written text for 6.3, Page Security Score michael.mccormick@wellsfargo.com
• RE: ACTION-374 - proposed re-written text for 6.3, Page Security Score Dan Schutzer
• Re: Troubles with KCM Stephen Farrell
• Re: ACTION-374 - proposed re-written text for 6.3, Page Security Score Ian Fette
• Re: ACTION-374 - proposed re-written text for 6.3, Page Security Score Timothy Hahn

Wednesday, 23 January 2008

• Re: ACTION-374 - proposed re-written text for 6.3, Page Security Score Ian Fette
• Re: ACTION-374 - proposed re-written text for 6.3, Page Security Score Timothy Hahn
• Re: ACTION-374 - proposed re-written text for 6.3, Page Security Score Ian Fette
• Re: ACTION-374 - proposed re-written text for 6.3, Page Security Score Timothy Hahn
• Re: ACTION-374 - proposed re-written text for 6.3, Page Security Score Mary Ellen Zurko
• Re: Troubles with KCM Serge Egelman
• Meeting record: WSC WG weekly 2008-01-16 Thomas Roessler
• ACTION-377: Hook for UIs in seciton 7.8 Thomas Roessler
• RE: ACTION-374 - proposed re-written text for 6.3, Page Security Score michael.mccormick@wellsfargo.com
• ACTION-374 - proposed re-written text for 6.3, Page Security Score Timothy Hahn
• Re: Agenda: WSC WG distributed meeting, Wednesday, 2008-01-23 Timothy Hahn
• RE: Agenda: WSC WG distributed meeting, Wednesday, 2008-01-23 Dan Schutzer
• How to write a good issue Mary Ellen Zurko
• Troubles with KCM Thomas Roessler

Tuesday, 22 January 2008

• Agenda: WSC WG distributed meeting, Wednesday, 2008-01-23 Mary Ellen Zurko
• Open Issues added to xit Anil Saldhana

Monday, 21 January 2008

• WSC-XIT review Rachna Dhamija

Friday, 18 January 2008

• call for demos for the f2f Mary Ellen Zurko
• wsc-xit next steps Mary Ellen Zurko
• WSC Open Action Items Mary Ellen Zurko
• Re: ACTION-336 OPEN Propose material for ISSUE-106 Stephen Farrell 2007-12-21 Mary Ellen Zurko
• Re: Form editor question Stephen Farrell
• Re: Form editor question Johnathan Nightingale
• Re: ACTION-356: picture-in-picture attacks Thomas Roessler
• Form editor question Stephen Farrell

Thursday, 17 January 2008

• Re: ACTION-356: picture-in-picture attacks Ian Fette
• Re: ACTION-372: Proposed replacement for 7.6 Thomas Roessler
• Re: ACTION-372: Proposed replacement for 7.6 Ian Fette
• Re: ACTION-369: webarch implications of 7.2 Thomas Roessler
• ISSUE-181: Should there be an authoring practice suggesting http/https URI space consistency [wsc-xit] Web Security Context Working Group Issue Tracker
• Re: ACTION-369: webarch implications of 7.2 Ian Fette
• ACTION-369: webarch implications of 7.2 Thomas Roessler
• ACTION-356: picture-in-picture attacks Thomas Roessler
• ACTION-317: Different notions of KCM in different parts of the document Thomas Roessler
• ACTION-372: Proposed replacement for 7.6 Thomas Roessler
• ACTION-357: less conspicuous hovering effects Thomas Roessler

Wednesday, 16 January 2008

• Re: ACTION-344, ISSUE-120: Proposed normative material on audio logotypes Mary Ellen Zurko
• Meeting record: WSC WG weekly 2008-01-09 Thomas Roessler
• WSC WG distributed meeting, Wednesday, 2008-01-16 William Eburn
• Re: Agenda: WSC WG distributed meeting, Wednesday, 2008-01-16 Ian Fette
• Re: Agenda: WSC WG distributed meeting, Wednesday, 2008-01-16 Serge Egelman

Tuesday, 15 January 2008

• Agenda: WSC WG distributed meeting, Wednesday, 2008-01-16 Mary Ellen Zurko

Monday, 14 January 2008

• RE: Is the padlock a page security score? Robert Yonaitis
• ISSUE-180 (wsc-xit spelling mistakes ): wsc-xit spelling mistakes (public comment) [wsc-xit] Web Security Context Working Group Issue Tracker
• RE: Is the padlock a page security score? Dan Schutzer
• ISSUE-179 (wsc-xit comment section 10.2.3): general comment section 10.2.3 (public comment) [wsc-xit] Web Security Context Working Group Issue Tracker
• ISSUE-178 (wsc-xit comment section 10.2.2): general comment section 10.2.2 conceptual model (public comment) [wsc-xit] Web Security Context Working Group Issue Tracker
• ISSUE-177 (wsc-xit comment section 6.5 tls/ssl pt2): general comment section 6.5 tls/ssl pt2 (public comment) [wsc-xit] Web Security Context Working Group Issue Tracker
• ISSUE-176 (wsc-xit comment section 6.5 tls/ssl): general comment section 6.5 tls/ssl processing (public comment) [wsc-xit] Web Security Context Working Group Issue Tracker
• ISSUE-175 (wsc-xit comment section 6.5): general comment section 6.5 table and bullet list (public comment) [wsc-xit] Web Security Context Working Group Issue Tracker
• ISSUE-174 (5.4 wsc-xit comments): review wsc-xit - general comments section 5.4 (public comment) [wsc-xit] Web Security Context Working Group Issue Tracker
• Fw: A review of Web Security Context's Scope and Use Cases -- Last Call Mary Ellen Zurko
• RE: Is the padlock a page security score? Dan Schutzer

Sunday, 13 January 2008

• Re: Is the padlock a page security score? Thomas Roessler

Friday, 11 January 2008

• RE: Is the padlock a page security score? Michael Versace
• RE: Is the padlock a page security score? michael.mccormick@wellsfargo.com
• Re: Is the padlock a page security score? Serge Egelman
• Re: Is the padlock a page security score? Anil Saldhana
• Re: Is the padlock a page security score? Ian Fette
• Re: Is the padlock a page security score? Anil Saldhana
• Meeting record: WSC WG weekly 2007-12-19 Thomas Roessler
• Re: Is the padlock a page security score? Mike Beltzner
• RE: Is the padlock a page security score? michael.mccormick@wellsfargo.com
• Re: Is the padlock a page security score? Mike Beltzner
• RE: Is the padlock a page security score? michael.mccormick@wellsfargo.com
• RE: Is the padlock a page security score? michael.mccormick@wellsfargo.com
• RE: Is the padlock a page security score? Timothy Hahn
• WSC Open Action Items Mary Ellen Zurko
• RE: Is the padlock a page security score? William Eburn
• Re: Is the padlock a page security score? Ian Fette
• RE: Is the padlock a page security score? William Eburn
• RE: Is the padlock a page security score? Doyle, Bill
• Re: ACTION-362 OPEN review wsc-xit William Eburn 2008-01-01 Mary Ellen Zurko
• Re: ACTION-361 OPEN review wsc-xit Phillip Hallam-Baker 2008-01-01 Mary Ellen Zurko
• Re: ACTION-343 OPEN Begin examining some of the recommendations, write down the underlying assumptions for success, then list any prior studies that have already examined those assumptions, and possibly how to test the untested assumptions Serge Egelman 2007-12-21 User Studies Mary Ellen Zurko
• RE: Is the padlock a page security score? Robert Yonaitis
• Re: ACTION-336 OPEN Propose material for ISSUE-106 Stephen Farrell 2007-12-21 Mary Ellen Zurko
• RE: ACTION-214 solicit commentary on Threat Trees from MITRE INFOSEC community Bill Doyle Mary Ellen Zurko
• Re: Is the padlock a page security score? Mary Ellen Zurko
• Re: Is the padlock a page security score? Mike Beltzner
• RE: Is the padlock a page security score? Dan Schutzer
• RE: Is the padlock a page security score? Dan Schutzer
• Re: Is the padlock a page security score? Serge Egelman

Thursday, 10 January 2008

• RE: Is the padlock a page security score? Robert Yonaitis
• RE: Is the padlock a page security score? michael.mccormick@wellsfargo.com
• Re: Is the padlock a page security score? Serge Egelman
• RE: Is the padlock a page security score? michael.mccormick@wellsfargo.com
• RE: Is the padlock a page security score? michael.mccormick@wellsfargo.com
• Re: Is the padlock a page security score? Ian Fette
• Re: Is the padlock a page security score? Serge Egelman
• RE: Is the padlock a page security score? William Eburn
• Re: Is the padlock a page security score? Serge Egelman
• Re: Is the padlock a page security score? Serge Egelman
• RE: Is the padlock a page security score? William Eburn
• RE: Is the padlock a page security score? Robert Yonaitis
• Re: Is the padlock a page security score? Anil Saldhana
• Re: Is the padlock a page security score? Serge Egelman
• RE: Is the padlock a page security score? michael.mccormick@wellsfargo.com
• RE: Is the padlock a page security score? William Eburn
• Re: Is the padlock a page security score? Serge Egelman
• RE: Is the padlock a page security score? William Eburn
• Re: Is the padlock a page security score? Serge Egelman
• Re: Is the padlock a page security score? Anil Saldhana
• Re: Is the padlock a page security score? Ian Fette
• RE: Is the padlock a page security score? Robert Yonaitis
• Re: Is the padlock a page security score? Serge Egelman
• Is the padlock a page security score? Anil Saldhana
• Re: Is the padlock a page security score? Anil Saldhana
• FW: Is the padlock a page security score? Robert Yonaitis
• RE: Is the padlock a page security score? William Eburn
• Re: Is the padlock a page security score? Serge Egelman
• RE: Is the padlock a page security score? michael.mccormick@wellsfargo.com
• Re: Is the padlock a page security score? Serge Egelman
• Re: Is the padlock a page security score? Serge Egelman
• Re: Is the padlock a page security score? Ian Fette
• Re: Is the padlock a page security score? Anil Saldhana
• Re: Is the padlock a page security score? Ian Fette
• RE: Is the padlock a page security score? Dan Schutzer
• Re: Is the padlock a page security score? Mike Beltzner
• RE: Is the padlock a page security score? michael.mccormick@wellsfargo.com
• Re: Is the padlock a page security score? Ian Fette
• RE: Is the padlock a page security score? Dan Schutzer
• Re: Is the padlock a page security score? Ian Fette
• Re: Is the padlock a page security score? Ian Fette
• RE: Is the padlock a page security score? michael.mccormick@wellsfargo.com
• RE: Is the padlock a page security score? Timothy Hahn
• Re: Is the padlock a page security score? Ian Fette
• RE: Is the padlock a page security score? michael.mccormick@wellsfargo.com
• RE: Is the padlock a page security score? michael.mccormick@wellsfargo.com
• Re: Is the padlock a page security score? Ian Fette
• Re: Is the padlock a page security score? Mike Beltzner
• RE: Is the padlock a page security score? michael.mccormick@wellsfargo.com
• Re: Is the padlock a page security score? Ian Fette
• Re: Is the padlock a page security score? Anil Saldhana
• RE: Is the padlock a page security score? michael.mccormick@wellsfargo.com
• Re: Is the padlock a page security score? Timothy Hahn
• Re: Is the padlock a page security score? Johnathan Nightingale
• Is the padlock a page security score? Mary Ellen Zurko

Wednesday, 9 January 2008

• Re: ISSUE-161: Be clearer about security indicator images [wsc-xit] Ian Fette
• RE: ISSUE-161: Be clearer about security indicator images [wsc-xit] Doyle, Bill
• meeting conflict - only available for first 1/2 hour Doyle, Bill
• Re: May f2f plans - query on joint meeting with CABForum Johnathan Nightingale

Tuesday, 8 January 2008

• Re: May f2f plans - query on joint meeting with CABForum Ian Fette
• May f2f plans - query on joint meeting with CABForum Mary Ellen Zurko
• Re: TLS/SSL robustness - high, medium, low Stephen Farrell
• RE: TLS/SSL robustness - high, medium, low Doyle, Bill
• RE: TLS/SSL robustness - high, medium, low michael.mccormick@wellsfargo.com
• Re: TLS/SSL robustness - high, medium, low Ian Fette
• RE: TLS/SSL robustness - high, medium, low Michael Versace
• RE: ISSUE-127: Safe Form Bar: Separate MITM handling? [Techniques] Close, Tyler J.
• RE: TLS/SSL robustness - high, medium, low Dan Schutzer
• TLS/SSL robustness - high, medium, low Doyle, Bill
• RE: ISSUE-127: Safe Form Bar: Separate MITM handling? [Techniques] Mary Ellen Zurko
• Agenda: WSC WG distributed meeting, Wednesday, 2008-01-09 Mary Ellen Zurko
• RE: ISSUE-161: Be clearer about security indicator images [wsc-xit] michael.mccormick@wellsfargo.com

Monday, 7 January 2008

• Re: ISSUE-127: Safe Form Bar: Separate MITM handling? [Techniques] Ian Fette
• RE: ISSUE-127: Safe Form Bar: Separate MITM handling? [Techniques] Close, Tyler J.
• Re: ISSUE-127: Safe Form Bar: Separate MITM handling? [Techniques] Ian Fette
• RE: ISSUE-127: Safe Form Bar: Separate MITM handling? [Techniques] Mary Ellen Zurko
• RE: ISSUE-127: Safe Form Bar: Separate MITM handling? [Techniques] Close, Tyler J.
• Re: ISSUE-170: 6.3 Seems more like extension/experimentation than standardization [wsc-xit] Mike Beltzner
• Re: ISSUE-167: Should Section 5.3.1 specify normative details for a theoretical technology? Johnathan Nightingale
• Re: ISSUE-167: Should Section 5.3.1 specify normative details for a theoretical technology? Mary Ellen Zurko
• Re: ISSUE-170: 6.3 Seems more like extension/experimentation than standardization [wsc-xit] Timothy Hahn
• ACTION-353: Convert Mozilla FPWD review notes into issues Johnathan Nightingale
• Re: ISSUE-169: Section 5.5.3 creates a burden on browsers to remember past certificates Johnathan Nightingale
• ISSUE-173: 8.1.1 Requires user testing for the purposes of conformance [wsc-xit] Web Security Context Working Group Issue Tracker
• ISSUE-172: 7.9 Normative text assumes a service we don't otherwise mention or expect to exist [wsc-xit] Web Security Context Working Group Issue Tracker
• ISSUE-171: 7.8 Is unclear about data retention requirements [wsc-xit] Web Security Context Working Group Issue Tracker
• ISSUE-170: 6.3 Seems more like extension/experimentation than standardization [wsc-xit] Web Security Context Working Group Issue Tracker
• ISSUE-169: Section 5.5.3 creates a burden on browsers to remember past certificates Web Security Context Working Group Issue Tracker
• ISSUE-168: Section 5.5.2 might be over-restrictive, especially on first-visit-redirect [wsc-xit] Web Security Context Working Group Issue Tracker
• ISSUE-167: Should Section 5.3.1 specify normative details for a theoretical technology? Web Security Context Working Group Issue Tracker
• ISSUE-166: Consider dropping section 5.2 in favour of "standard" matching algo, if appropriate. Web Security Context Working Group Issue Tracker

Sunday, 6 January 2008

• Re: ISSUE-161: Be clearer about security indicator images [wsc-xit] Serge Egelman

Saturday, 5 January 2008

• Re: ISSUE-161: Be clearer about security indicator images [wsc-xit] Ian Fette
• Re: ISSUE-161: Be clearer about security indicator images [wsc-xit] Serge Egelman

Friday, 4 January 2008

• RE: ACTION-340 OPEN Gather data about cost of TLS deployment Phillip Hallam-Baker 2007-12-10 Hallam-Baker, Phillip
• Re: ISSUE-127: Safe Form Bar: Separate MITM handling? [Techniques] Mary Ellen Zurko
• WSC Open Action Items Mary Ellen Zurko
• Re: ACTION-345 OPEN Begin designing lo-fi user study for Browser Lockdown Maritza Johnson 2007-11-30 Mary Ellen Zurko
• Re: ACTION-340 OPEN Gather data about cost of TLS deployment Phillip Hallam-Baker 2007-12-10 Mary Ellen Zurko

Thursday, 3 January 2008

• RE: wsc-xit review Close, Tyler J.
• Re: wsc-xit review Mary Ellen Zurko
• wsc-xit review Close, Tyler J.

Wednesday, 2 January 2008

• ISSUE-165: Allow for (non default) configuration of notification of first time TLS interaction with a site [wsc-xit] Web Security Context Working Group Issue Tracker
• ISSUE-164: SSC != CoSL [wsc-xit] Web Security Context Working Group Issue Tracker
• ISSUE-163: Make (sure) 9.4 is internally consistent [wsc-xit] Web Security Context Working Group Issue Tracker
• ISSUE-162: Recognize there are other forms of network security [wsc-xit] Web Security Context Working Group Issue Tracker
• ISSUE-161: Be clearer about security indicator images [wsc-xit] Web Security Context Working Group Issue Tracker
• ISSUE-160: Remove section 7.9 [wsc-xit] Web Security Context Working Group Issue Tracker
• ISSUE-159: Merge 7.8 into 8.2 [wsc-xit] Web Security Context Working Group Issue Tracker
• ISSUE-158: Abstracting and tightening editing of stored history [wsc-xit] Web Security Context Working Group Issue Tracker
• ISSUE-157: Masking only MUST for passwords [wsc-xit] Web Security Context Working Group Issue Tracker
• ISSUE-156: Tighten and abstract seleting the text string [wsc-xit] Web Security Context Working Group Issue Tracker
• ISSUE-155: Remove references to contacts option [wsc-xit] Web Security Context Working Group Issue Tracker
• ISSUE-154: Provide unique labels for each message and use them consistently as references [wsc-xit] Web Security Context Working Group Issue Tracker
• ISSUE-153: Tie SWFE to secondary SCI [wsc-xit] Web Security Context Working Group Issue Tracker
• ISSUE-152: Clarify the point of "distinguishing" between static and other text in messages [wsc-xit] Web Security Context Working Group Issue Tracker
• ISSUE-151: Make "similar" clearer (in choosing petnames) [wsc-xit] Web Security Context Working Group Issue Tracker
• ISSUE-150: Abstract how user navigates to a site for establishing a new relationship Web Security Context Working Group Issue Tracker
• ISSUE-149: Condense 7.2 to its first normative directive only [wsc-xit] Web Security Context Working Group Issue Tracker
• ISSUE-148: Downgrade ability to update an organization's name and address to SHOULD [wsc-xit] Web Security Context Working Group Issue Tracker
• ISSUE-147: Descriptions of certificate matching rules in SWFE need explanations somewhere [wsc-xit] Web Security Context Working Group Issue Tracker
• ISSUE-146: 7.1 to reference where xit talks about how identity is presented [wsc-xit] Web Security Context Working Group Issue Tracker
• Re: ISSUE-131 (Code outside browser): Executing code outside of browser in 8.3.2.3 is vague / scary [All] Mike Beltzner
• Re: ISSUE-131 (Code outside browser): Executing code outside of browser in 8.3.2.3 is vague / scary [All] Ian Fette
• Re: ISSUE-131 (Code outside browser): Executing code outside of browser in 8.3.2.3 is vague / scary [All] Anil Saldhana
• Re: wsc-xit review Stephen Farrell
• Re: ISSUE-131 (Code outside browser): Executing code outside of browser in 8.3.2.3 is vague / scary [All] Ian Fette
• Re: wsc-usecases comments Re: Comments on draft documents posted to the WSC wiki Mary Ellen Zurko
• Re: wsc-xit review Mary Ellen Zurko
• Re: ISSUE-142: Page Security Score does not yet have enough content behind it [wsc-xit] Timothy Hahn
• Re: ISSUE-131 (Code outside browser): Executing code outside of browser in 8.3.2.3 is vague / scary [All] Anil Saldhana
• Re: usecases comments Re: Comments on draft documents posted to the WSC wiki Ian Fette
• Re: usecases comments Re: Comments on draft documents posted to the WSC wiki Ian Fette
• Re: usecases comments Re: Comments on draft documents posted to the WSC wiki Mary Ellen Zurko

Tuesday, 1 January 2008

• wsc-xit review Stephen Farrell

Last message date: Thursday, 31 January 2008 17:10:44 UTC