- From: Close, Tyler J. <tyler.close@hp.com>
- Date: Thu, 7 Dec 2006 19:32:22 -0600
- To: <public-wsc-wg@w3.org>
Hi Mez, Thanks, that was helpful. For now, I've summarized that point in the wiki as: "Any recommendation to prohibit the user from interacting with a web page" I also need more information on: "code based techniques to detect spoofing attacks" as well as how that relates to: "calculations, algorithms, and functions that attempt to determine whether or not an attack is underway" Are these two the same? Thanks, Tyler ________________________________ From: public-wsc-wg-request@w3.org [mailto:public-wsc-wg-request@w3.org] On Behalf Of Mary Ellen Zurko Sent: Thursday, December 07, 2006 3:05 PM To: Close, Tyler J. Cc: public-wsc-wg@w3.org Subject: RE: What problems are we trying to solve? Since our charter is recommendations on secure and usable presentation of web security context information, it does not cover recommendations on what browsers should do should they display or determine that web security context information indicates (the potential for) an attack. For example, stating whether or not users should be allowed to go to sites under particular circumstances would be out of charter. Mez "Close, Tyler J." <tyler.close@hp.com> Sent by: public-wsc-wg-request@w3.org 12/05/2006 02:08 PM To <public-wsc-wg@w3.org> cc Subject RE: What problems are we trying to solve? Mary Ellen Zurko wrote: > Out of scope: > * techniques to stop the user from taking an action because > an attack has been discovered Could you clarify the above item? Thanks, Tyler
Received on Friday, 8 December 2006 01:32:43 UTC