[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [TLS] Security today
Fwiw, at Microsoft we mandate the use of "strong crypto" and that includes ciphersuites and bit lengths. In the case of RSA, 2048 minimum, and the only time 1024 is allowed is for backward compat, and that has to be signed off by the crypto board (Ferguson, LaMacchia, Benoloh et al)
Cheers, Michael
Writing Secure Code for Windows Vista: http://www.microsoft.com/MSPress/books/10723.aspx
SDL Book: http://www.microsoft.com/MSPress/books/8753.asp
Blog: http://blogs.msdn.com/michael_howard/
-----Original Message-----
From: tls-bounces@xxxxxxxx [mailto:tls-bounces@xxxxxxxx] On Behalf Of Mike
Sent: Thursday, March 27, 2008 9:28 PM
To: tls@xxxxxxxx
Subject: Re: [TLS] Security today
Michael Howard wrote:
> I think there is a deeper issue than this - people email
> sensitive data all the time with no encryption...
Yes, email security is problematic, but users have to do
a lot of manual configuration even to get set up for it.
And then, they need to convince their correspondents to
set up their system too.
With HTTPS, the infrastructure is already there, and it's
being used. The problem is with server configuration:
key size, cipher suite selection. If servers were simply
better configured, security would automatically improve.
Users wouldn't have to do anything differently; those
who we rely on for security are failing us!
Mike
P.S. and there's nothing you or I can do about it as a
user -- we can't influence the key sizes or cipher suites
offered by a server -- it's either take it or leave it.
_______________________________________________
TLS mailing list
TLS@xxxxxxxx
https://www.ietf.org/mailman/listinfo/tls
_______________________________________________
TLS mailing list
TLS@xxxxxxxx
https://www.ietf.org/mailman/listinfo/tls