W3C home > Mailing lists > Public > public-usable-authentication@w3.org > April 2006

Re: Secure Chrome

From: Mary Ellen Zurko <Mary_Ellen_Zurko@notesdev.ibm.com>
Date: Tue, 11 Apr 2006 18:30:55 -0400
To: George Staikos <staikos@kde.org>
Cc: public-usable-authentication@w3.org
Message-ID: <OF10DABC6A.A78594C0-ON8525714D.007B8C8C-8525714D.007BBBFA@notesdev.ibm.com>
No active content at all. Zippo. No javascript. No Java. No ActiveX. 

Web browsing the way nature intended :-). 

Yes, there's a lot of things you couldn't do with such a browser. But it 
has the benefit of simplicity.
        Mez

Mary Ellen Zurko, STSM, IBM Lotus CTO Office       (t/l 333-6389)
IBM Lotus/WPLC Security Strategy and Architecture




George Staikos <staikos@kde.org> 
Sent by: public-usable-authentication-request@w3.org
04/11/2006 01:07 PM

To
public-usable-authentication@w3.org
cc

Subject
Re: Secure Chrome







On Monday 10 April 2006 13:30, Thomas Roessler wrote:

> This kind of work would cover best practices in terms of what
> sites should or should not be able to control in a browser's
> user interface, and, possibly, a switching mechanism between a
> rich and a safe browser mode, as discussed at various occasions
> in New York.

  For those who have been advocating this approach, what do you envision 
in 
this mode?  What would make it "safe"?

-- 
George Staikos
KDE Developer                                                            
http://www.kde.org/
Staikos Computing Services Inc.                          
http://www.staikos.net/
Received on Thursday, 13 April 2006 02:46:25 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:53:15 UTC