updating Google Chrome's implementation report

Based on email discussions with Ian and Wan-Teh Chang, we're updating the 
Google Chrome implementation report as follows (was TBD). This will be 
part of the overall update to the draft implementation report I'll be 
uploading to the wiki shortly (as I have two other action items on it). 

What TLS [SSLv3][TLSv11][TLSv12] protocol versions and algorithms are 
considered as strong TLS algorithms, and what protocol versions and 
algorithms are supported in TLS negotiation, but not considered strong.
On Linux, we enable only cipher suites with keys of at least 80 bits. On 
Windows, we share system wide SSL settings for supported cipher suites, 
and explicitly disable SSLv2 and MD2 and MD4 on certificate signatures. We 
don?t have anything we accept but consider ?weak?.