Re:Launching in 2015: A Certificate Authority to Encrypt the...
by handsomeransoms on Tuesday November 18, 2014 @06:59PM
(#8627246)
How many people are careful to type "https" every time they visit a website? How many people pay close attention to the lock icon/color of the URL bar? This advice seems to ignore the existence of sslstrip [0] and related attacks, and the numerous countermeasures that have been designed to deal with this problem (e.g. HSTS).
Re:Launching in 2015: A Certificate Authority to Encrypt the...
by blendo on Tuesday November 18, 2014 @12:28PM
(#8624994)
This is EXACTLY what I want for my intranet sites. It lets me protect my users from the wireshark in the next cubicle.
Re:Launching in 2015: A Certificate Authority to Encrypt the...
by tacticus on Tuesday November 18, 2014 @03:20PM
(#8626077)
The solution for this is to run your own CA internally and push out the cert to all the machines. (if you have byod stuff it makes it a little harder but you could still have an internal ca signing only a certain subdomain and get people ot install it)
Re:Launching in 2015: A Certificate Authority to Encrypt the...
by motoboi on Tuesday November 18, 2014 @01:37PM
(#8625439)
But that don't protect you from a malicious user hijacking this domain in the next cubicle. Perhaps, if your switches are not properly configured , that the guy in the next cubicle ou do some arp spoofing and https://intranet.yourdomain would be served by a bogus server collecting passwords.
But your users won't notice the difference, because they are used to see the certificate warning on his browser.
If the user typed https://www.mybank.com, show the usual warning for self-signed certificates.