- From: Dan Schutzer <dan.schutzer@fstc.org>
- Date: Mon, 10 Apr 2006 14:19:01 -0400
- To: "'Thomas Roessler'" <tlr@w3.org>, <public-usable-authentication@w3.org>
The latter, although more complex, seems more promising to me from a security perspective -----Original Message----- From: public-usable-authentication-request@w3.org [mailto:public-usable-authentication-request@w3.org] On Behalf Of Thomas Roessler Sent: Monday, April 10, 2006 1:31 PM To: public-usable-authentication@w3.org Subject: Secure Metadata Hello, as another area that, as an outcome from the workshop, looks like it might be a good candidate for future work, I'd like to ask for your feed-back on Secure Metadata. The basic question that this work would be asked to answer would be: What can content providers expect browsers to display in terms of metadata? And how can these metadata be secured against faking? There appear to be several possible routes that this work could take, including, on the simple side, an agreement and recommendation to display logotype certificate attribute; on the more complex end of the scale, this work could also look at formats for complex trustmark-like objects, and a recommendation to display these in the browser chrome. Your thoughts would be most welcome. Regards, -- Thomas Roessler, W3C <tlr@w3.org>
Received on Monday, 10 April 2006 18:19:13 UTC