Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Can HTTPS connections be hijacked with a man-in-the-middle attack?

I'm using gmail from work, but I need to enter a password for a proxy when accesing the first web page. The password is asked from inside the browser. I receive a certificate from the proxy which I must accept in order to make the Internet connection work.

Can my HTTPS connection, between gmail and browser, be tracked in this situation?

like image 808
INS Avatar asked May 22 '10 16:05

INS


People also ask

Does HTTPS stop man in the middle attacks?

This doesn't make you impenetrable to MITM attacks, but it makes life much harder for crooks and will likely cause them to look for an easier target. As with VPNs, HTTPS websites encrypt data and prevent attackers from intercepting communications.

Can HTTPS be eavesdropped?

While HTTPS sessions can be reliably considered secure from eavesdropping attacks, HTTPS by itself does not protect against any other types of attack.

Is SSL and TLS very secure to a man in the middle attack?

As explained in the introduction, to be sure that a man in the middle cannot read the packages, SSL was invented. The messages are now encrypted with a key that only the client and server know of. Though it is still possible to do active eavesdropping on a secured connection.

What attacks does HTTPS protect against?

It protects against man-in-the-middle attacks, and the bidirectional encryption of communications between a client and server protects the communications against eavesdropping and tampering. The authentication aspect of HTTPS requires a trusted third party to sign server-side digital certificates.


1 Answers

Fiddler describes it like this:

Q: The HTTPS protocol was designed to prevent traffic viewing and tampering. Given that, how can Fiddler2 debug HTTPS traffic?

A: Fiddler2 relies on a "man-in-the-middle" approach to HTTPS interception. To your web browser, Fiddler2 claims to be the secure web server, and to the web server, Fiddler2 mimics the web browser. In order to pretend to be the web server, Fiddler2 dynamically generates a HTTPS certificate.

Fiddler's certificate is not trusted by your web browser (since Fiddler is not a Trusted Root Certification authority), and hence while Fiddler2 is intercepting your traffic, you'll see a HTTPS error message in your browser, like so:

like image 179
tangens Avatar answered Oct 22 '22 11:10

tangens