nanog mailing list archives
Re: Facebook insecure by design
From: Jimmy Hess <mysidia () gmail com>
Date: Sun, 2 Oct 2011 11:36:20 -0500
On Sun, Oct 2, 2011 at 10:38 AM, Michael Thomas <mike () mtcc com> wrote:
I'm not sure why lack of TLS is considered to be problem with Facebook. The man in the middle is the other side of the connection, tls or otherwise.
That's where the X509 certificate comes in. A man in the middle would not have the proper private key to impersonate the Facebook server that the certificate was issued to. Supporting TLS in their case is not good enough... they would need to force all connections to be over TLS, to achieve security against MITM. As soon as an app causes the end user to switch to a non-TLS connection, they are vulnerable.
Mike
-- -JH
Current thread:
- Re: Facebook insecure by design Michael Thomas (Oct 02)
- Re: Facebook insecure by design Jimmy Hess (Oct 02)
- Re: Facebook insecure by design William Allen Simpson (Oct 02)
- Re: Facebook insecure by design Michael Thomas (Oct 02)
- Re: Facebook insecure by design Patrick Sumby (Oct 03)
- Re: Facebook insecure by design Jason Leschnik (Oct 03)
- Re: Facebook insecure by design Michael Thomas (Oct 03)
- Re: Facebook insecure by design William Allen Simpson (Oct 02)
- Re: Facebook insecure by design Jimmy Hess (Oct 02)
- Re: Facebook insecure by design Jimmy Hess (Oct 02)
- Re: Facebook insecure by design Joel jaeggli (Oct 02)
- Re: Facebook insecure by design Joel jaeggli (Oct 02)
- Re: Facebook insecure by design Bill.Pilloud (Oct 04)