public-wsc-wg@w3.org from June 2007 by subject

Action 180 - Make pass through SharedBookmarks and other material; map testing results to status quo

Action 213: write a lightning proposal on wiki

ACTION 215: Revisit threat trees

ACTION 219 - Update IdentitySignal to conform to template

ACTION-205: Update PageInfo Proposal after discussion

ACTION-208: "Site Identifying Images in Chrome" display recommendation

ACTION-208: "Site Identifying Images in Chrome" displayrecommendation

ACTION-208: "Site Identifying Images in Chrome"displayrecommendation

ACTION-208: "Site Identifying Images inChrome"displayrecommendation

ACTION-209: What is a secure page?

ACTION-210: "Security Protocol Error Presentation" display recommendation

ACTION-220 Introduce Secure Letterhead in the Wiki

ACTION-231 OPEN Start a discussion about including descriptions of the information divulged to websites by user-agents

ACTION-233 Make sure Jagatic et al on social phishing is in SharedBookmarks

ACTION-234 Add www2006 jakobsson, Florencio & Hursley MSR paper to our shared bookmarks list

ACTION-237: Drive the process of Matching SharedBookmark content to Recommendations

ACTION-240 :TLS errors...

ACTION-242 OPEN add file extension remark to security context information list Stephen Farrell 2007-06-01

ACTION-243 Propose link from note to threat trees

ACTION-246 description of the recommendation sections drafted

ACTION-247: "Mark in wiki what proposals have been transferred into the note"

ACTION-250: propose breaking out 2.4 into its own proposal.recommendation

ACTION-253 - new recommendation proposal available for comment

ACTION-255 Email beltzner photo of whiteboard

ACTION-262: Share study on effectiveness of trust seals in SharedBookmarks

Added "Empirical Approach to Understanding Privacy Valuation" to SharedBookmarks on wiki

Agenda, Wednesay. 13 June, WSC Call

Agenda, Wednesay. 20 June, WSC Call

Agenda, Wednesay. 27 June, WSC Call

Agenda, Wednesay. 6 June, WSC Call

ANEC'scomments on the “Web Security Experience, Indicators and Trust: Scope and Use Cases” working draft (March 02, 2007)

Anti Phishing Phil

Basic Authentication - what do we have?

Brainstorming notes

Defense in depth was - RE: iframe tag attack

Draft Conformance Clause [ACTION-245]

ETSI: CL07_2554 - Call for Papers for / Invitation to 3rd ETSI Security Workshop

google safe browsing API

Hackers Break Apple's Safari for Windows on First Day

Identity Signal conformance

IETF BoF on trust anchor managment

IETF seeking review: draft-hartman-webauth-phishing-03.txt

iframe tag attack

Image attack on MySpace boosts phishing exposure

infocard icon

ISSUE-18: Clarify audience of wsc-usecases

ISSUE-20 - proposed text for intro section of section 7

ISSUE-23 OPEN Rephrase background on usable security in Process secion

ISSUE-26 OPEN "currently deployed security information"

ISSUE-38: no safe haven in presentation space (from public comments)

ISSUE-40: Drill-down access to all security information is not \'nice,\' it\'s required (by UAAG 1.0). (public comment)

ISSUE-42: Re: 3.2 Non-HTTP Web interactions (public comment)

ISSUE-68: Note summary, goals, and scope should more clearly focus on problem to be solved---impersonation

ISSUE-6: User Interface Issues for Mobile Browsing

ISSUE-70: Scope should be defined in terms of concepts, not in terms of use cases (

ISSUE-72: Replace term \\'Status Quo\\' with something more specific

ISSUE-73: Proposed changes to process chapter

ISSUE-76: add file extension remark to security context information list

ISSUE-77: Reference threat work in wsc-usecases

Liaisons needed

Making use of Threat Trees, and the importance of identifying vulnerabilities

Meeting record: WSC WG weekly 2007-05-23

Meeting record: WSC WG weekly 2007-06-13

Minor template update

Minutes: WSC WG face-to-face 2007-05-31

Minutes: WSC WG face-to-face 30 May 2007

Minutes: WSC WG weekly 2007-06-06

Note use-cases as explanatory device

Open Actions 254 and 261 are closed

Page Security Score proposal

PII bar proposal updated based on telecon feedback

PIIEditorBar

Process point: I'm lazy

Proposals in the wiki

Public comments on threat trees

Recommendations Draft

Regrets for call - 06/20

Regrets from Mozilla

Review of threat trees

Robustness - Review of note - do we need an assumption section?

Safe Web Browsing Recommendation put in template form

Secure storage (was: PIIEditorBar)

Secure storate (was: PIIEditorBar)

Small number of Primary SCI displays

Technology Baseline and Accessibility-Supported in WCAG 2.0

The ANEC comments and: Toward a last call for the Note

threat trees and how they relate to our work

Toward a last call for the Note

Trusted Browser Component (Re: Action 213: write a lightning proposal on wiki)

Update PII editor proposal text

Update to Wiki

Upgrade of W3C database server on 25 June at 13:00 GMT

web-based malware

What Is A Secur ePage - Templateified

What Is A Secure Page - Templateified

WSC Open Action Items

Last message date: Friday, 29 June 2007 17:26:14 UTC