Friday, 30 March 2007
- Recommendations for "Lightening Discussions" at next week's meeting
- Threat trees & use cases updated
Thursday, 29 March 2007
- RE: Rec Proposal: Separate in-browser editor for entry of Personally Identifiable Information (PII)
- timeline in our wiki
- Re: ACTION-149: FSTC's list of authentication techniques (BMA taxonomy)
- RE: ACTION-149: FSTC's list of authentication techniques (BMA taxonomy)
- Re: Rec Proposal: Separate in-browser editor for entry of Personally Identifiable Information (PII)
- RE: Rough proposal: Contextual Password Warnings
Wednesday, 28 March 2007
- (Corrected) Action item summary: WSC WG weekls 2007-03-28
- Meeting record: WSC WG weekly 2007-03-20
- Next steps on threat trees
- Action item summary: WSC WG weekls 2007-03-28
- [fwd] [fwd] Re: Defining different user agent classes for conformance? (from: ij@w3.org) (from: tlr@w3.org)
- ISSUE-24: [editorial] Add \"known systemic flaws\" to goals
- diffmk
- RE: ACTION-149: FSTC's list of authentication techniques (BMA taxonomy)
- Re: ACTION-156: List of privacy and security indicators
- Re: ACTION-156: List of privacy and security indicators
- ACTION-149: FSTC's list of authentication techniques (BMA taxonomy)
Tuesday, 27 March 2007
- Introduction: Luis Barriga (Ericsson)
- [fwd] Agenda, WEDNESDAY, 28 March, WSC Call (from: Mary_Ellen_Zurko@notesdev.ibm.com)
- Re: Rec Proposal: Separate in-browser editor for entry of Personally Identifiable Information (PII)
Monday, 26 March 2007
- Re: ACTION-106 Propose clarifying language for 8.2.5
- RE: ACTION-106 Propose clarifying language for 8.2.5
- RE: ISSUE-16: Create section 9.2.6 as per ACTION-105
- Re: ACTION-164 - Elaborate Cross Site Scripting in Wiki
- RE: ISSUE-17: Amend section 8.2 as per ACTION-103
- Re: ACTION-164 - Elaborate Cross Site Scripting in Wiki
- RE: ISSUE-17: Amend section 8.2 as per ACTION-103
- RE: ISSUE-20: Potential additions to Available Security Information
- Re: ACTION-156: List of privacy and security indicators
- RE: Rough proposal: Contextual Password Warnings
- Re: ISSUE-22: Rephrase favicon text
- Re: ISSUE-21: Reply to question - what do pword managers do to ensure they don\'t \"leak\" pwords?
- Re: ACTION 152, 113 -- Fun with glossaries
- Re: ISSUE-20: Potential additions to Available Security Information
- ISSUE-23: Rephrase background on usable security in Process secion
- ISSUE-22: Rephrase favicon text
- ISSUE-21: Reply to question - what do pword managers do to ensure they don\'t \"leak\" pwords?
- ISSUE-20: Potential additions to Available Security Information
- ISSUE-19: Arrangement and formatting of use cases
- ISSUE-18: Clarify audience of wsc-usecases
- Re: WSC WG - timeline/roadmap
- Re: Rec Proposal: Separate in-browser editor for entry of Personally Identifiable Information (PII)
- Rough proposal: Contextual Password Warnings
- ACTION-156: List of privacy and security indicators
- Documenting status quo
Friday, 23 March 2007
- Re: ISSUE-6 User Interface Issues for Constrained / Mobile Devices
- Re: ISSUE-11: \"Problems with the status quo\"
- Re: ISSUE-7: Mental models?
- Re: ACTION-164 - Elaborate Cross Site Scripting in Wiki
- Agenda, WEDNESDAY, 28 March, WSC Call
- Re: ACTION-164 - Elaborate Cross Site Scripting in Wiki
- ACTION-155 OPEN Track P3P header related indicators
- ISSUE-6 User Interface Issues for Constrained / Mobile Devices
- Re: ISSUE-7: Mental models?
- Re: ISSUE-8: User Education
- Re: ISSUE-11: \"Problems with the status quo\"
- Re: ISSUE-15: Revise section 9.2.5 as per ACTION-106
- Re: ISSUE-16: Create section 9.2.6 as per ACTION-105
- Re: ISSUE-17: Amend section 8.2 as per ACTION-103
- ACTION-164 - Elaborate Cross Site Scripting in Wiki
- ACTION-165 Copy definition of web user agent to glossary
- Re: WSC WG - timeline/roadmap
Thursday, 22 March 2007
Wednesday, 21 March 2007
Tuesday, 20 March 2007
- Meeting record: WSC WG weekly 2007-03-13
- Action item summary: 2007-02-20
- Re: ACTION-128 Document current practice in terms of security UI robustness
- RE: ACTION-148 Discussion: The role of technology-specific security aids in our recommendations
- hanging out on IRC
- remember, use the issues
- ISSUE-17: Amend section 8.2 as per ACTION-103
- ISSUE-16: Create section 9.2.6 as per ACTION-105
- ISSUE-15: Revise section 9.2.5 as per ACTION-106
Monday, 19 March 2007
- RE: ISSUE-13 OPEN Mez' Note Review 2007-03-02 Note: use cases etc.
- RE: Documenting the status quo
- Summary of action items: 2007-03-13
Friday, 16 March 2007
- Re: ACTION-128 Document current practice in terms of security UI robustness
- RE: ACTION-148 Discussion: The role of technology-specific security aids in our recommendations
- Agenda, 20 March, WSC Call
- ACTION-108 contribute more studies for 8.3
Wednesday, 14 March 2007
- ISSUE-13 OPEN Mez' Note Review 2007-03-02 Note: use cases etc.
- Re: interesting issue found yesterday
- Re: interesting issue found yesterday
- Re: interesting issue found yesterday
- Re: interesting issue found yesterday
- Re: interesting issue found yesterday
- interesting issue found yesterday
- Meeting record: WSC WG weekly 2007-03-06
- Re: Threat Trees
- Phishing attacks target CareerBuilder.com users
- ISSUE-14: Technologies that reduce risk
- Re: Threat Trees
Tuesday, 13 March 2007
- Re: Documenting the status quo
- Re: Is there a way to see differences in our wiki?
- Introduction
- Is there a way to see differences in our wiki?
- RecommendationIndex area
- ACTION 152, 113 -- Fun with glossaries
- Re: ACTION-148 Discussion: The role of technology-specific security aids in our recommendations
- WG members reviewing wsc-usecases
- Re: Documenting the status quo
- Re: ACTION-151 update security context - User agents and robustness of authentication schemes
- Re: ACTION-148 Discussion: The role of technology-specific security aids in our recommendations
- Re: ACTION-148 Discussion: The role of technology-specific security aids in our recommendations
- Fw: Agenda, 13 March, WSC Call
Monday, 12 March 2007
- Threat Trees
- Re: Catching up with the group
- Catching up with the group
- Re: Are we dropping the glossary? (Re: ACTION-96 Draft initial outline of glossary)
- ACTION-151 update security context - User agents and robustness of authentication schemes
- Re: ACTION-140 Propose non-goals material re other app contexts
- Are we dropping the glossary? (Re: ACTION-96 Draft initial outline of glossary)
Friday, 9 March 2007
Thursday, 8 March 2007
- Agenda, 13 March, WSC Call
- ACTION-140 Propose non-goals material re other app contexts
- ACTION-133 Offer text suggestion around "many users"
- ACTION-127 Document current practice in terms of security UI robustness
- ACTION-126 Document current practice in terms of security UI robustness
- ACTION-114 suggesting alternative wording for 8.4.1
- ACTION-110 Create new subsection under 8.2 to classify types of attacks
- Re: ACTION-108 contribute more studies for 8.3
- ACTION-99 draft text for section 8, covering "block pages"
- ACTION-98 Add references for 8.1.2
- ACTION-96 Draft initial outline of glossary
- RE: Documenting the status quo
Wednesday, 7 March 2007
Tuesday, 6 March 2007
Wednesday, 7 March 2007
Tuesday, 6 March 2007
- Produce material on name-based virtual hosting and TLS
- Documenting the status quo
- Fw: US clocks moving to Summer Time this Sunday, 11 March
- Introduction: Pascal Manzano (ENISA)
- Introduction
- ACTION-148 Discussion: The role of technology-specific security aids in our recommendations
- FTC Workshop on reducing identity theft through enhanced authentication
- Re: ACTION-107 : Create a library of testcases / examples of attacks listed in section 8
- Fw: ACTION-128 Document current practice in terms of security UI robustness
- Re: ACTION-107 : Create a library of testcases / examples of attacks listedin section 8
- Re: ACTION-107 : Create a library of testcases / examples of attacks listed in section 8
- Fw: ACTION-128 Document current practice in terms of security UI robustness
- Fw: ACTION-106 Propose clarifying language for 8.2.5
- Fw: ACTION-105 Propose text on notifiaction / information bar
- ACTION-117 : Contribute material re confirmation bias to note
- ACTION-107 : Create a library of testcases / examples of attacks listed in section 8
- ACTION-106 Propose clarifying language for 8.2.5
- ACTION-128 Document current practice in terms of security UI robustness
- ACTION-105 Propose text on notifiaction / information bar
- Re: ACTION-111 Track rob tracking URL scrolling issues
- ACTION-103 Propose descriptive text on firefox anti-phishing UI (for 8.2)
Monday, 5 March 2007
- May f2f in Dublin
- Fw: Experience with usability testing in WGs?
- Transition announcement: First Public Working Draft of WSC WG Note
- reviewing our Note,
- RE: reviewing our Note, part 2
Friday, 2 March 2007
- ISSUE-13: Mez\' Note Review
- reviewing our Note, part 2
- Rescheduling our regular meetings
- Agenda, 06 March, WSC Call
- FPWD of Note is out
Thursday, 1 March 2007
- ACTION-117 Contribute material re confirmation bias to note
- ACTION-116 Check whether security usability of form submission is covered in Note
- ACTION-111 Track rob tracking URL scrolling issues
- ACTION-110 Create new subsection under 8.2 to classify types of attacks
- ACTION-109 to propose more elaborate text for 8.3.1 ("padlock icon")
- ACTION-108 contribute more studies for 8.3
- ACTION-103 Propose descriptive text on firefox anti-phishing UI (for 8.2)
- ACTION-105 Propose text on notifiaction / information bar
- ACTION-106 Propose clarifying language for 8.2.5
- Re: ACTION-99 draft text for section 8, covering "block pages"
- Re: ACTION-98 Add references for 8.1.2
- ACTION-99 draft text for section 8, covering "block pages"
- Re: ACTION-98 Add references for 8.1.2
- Re: ACTION-98 Add references for 8.1.2
- ACTION-98 Add references for 8.1.2
- ACTION-97 Seed and drive process to document current-generation undocumented safeguards in wiki
- ACTION-94 Draft subsections for 8 about "compelling user interface", crypto
- ACTION-90 Ask Rob Franco to document what certification verification errors IE7 displays
- ACTION-72 Track RobFranco proposing use cases to deal with scriptable areas
- ACTION-71 Propose history related use-case
- Techniques to make security indicators robust against spoofing