Re: Summary of "What is a secure page?" discussion, first draft

Hi Yngve, 

> Criteria currently used by clients (clients may use a selection)
> 
>     - Symmetric encryption strength used by the connection
>     - Strength of authentication used by server (such as public key 
length
> and certificate chain)
>     - Security of the protocol
>     - Sequence of redirects used to get to the document
>     - The security of documents loaded as part of the document
>     - The security of resources loaded by external software (plugins, 
Java)
> through the client

How does this last item work in current security display criteria? What's 
taken into consideration? 

> Criteria some think should be included
> 
>     - Information about the service's reputation
>     - Previously registered information about the server
>     - Is the document using content from third party services?

How would that last one get taken into account? What data is available on 
that today? Or is that a pure futures statement?


Nice writeup. In some of the sections, I'm not 100% sure how all of the 
details tie into our charter. But I think that will become clear as we 
flesh out what security context information should be displayed, and how, 
and how it should be protected. 

ACTION-178, for tracker