Read: Difference between HTTP and HTTPS. Until a few years ago, HTTPS was considered foolproof, until a person named Moxie proved it wrong by spoofing HTTPS. This was done using the interception of data packets in the middle of communication by someone who spoofed the HTTPS security key to make you believe the connection is still encrypted. This article studies HTTPS spoofing where even well-known companies had employed the technique to watch you and to snoop on your activities. Before understanding Man in the Middle attack, you’ll need to know about the HTTPS certificate key, which is spoofed to make you believe nothing is wrong.
What Is HTTPS Website Certificate Key
There are certain Certificate Authorities that offer “fitness” certificates to websites. There are many factors to determine the “fitness” factor: encrypted connection, virus-free downloads, and few other things. HTTPS means your data is secure when transacting. Mainly, the HTTPS is used by e-commerce stores and sites that have data/information that is private for you – such as email sites. Social networking sites like Facebook and Twitter too use the HTTPS. With each certificate, there is a key that is unique to that website. You can view the certificate key of a website by right-clicking on its webpage and selecting PAGE INFO. Based on the browser, you will get different types of dialog boxes. Look for CERTIFICATE and then THUMBPRINT or FINGERPRINT. That will be the website certificate’s unique key.
HTTPS Security and Spoofing
Coming back to how safe you are with HTTPS, the certificate key can be spoofed by third parties in the middle of clients and websites. This technique of prying upon your conversations is called Man in the Middle. Here is how your browser is sent to HTTPS: Either you click on login button/link or you type in the URL. In the first case, you are sent directly to the HTTPS page. In the second case, where you type in the URL unless you type in HTTPS, the DNS will resolve to a page that directs you to the HTTPS page using auto-redirect (302). The Man in the Middle has certain methods to catch your first request to access the website, even if you typed HTTPS. The Man in the Middle could be your browser itself. Opera Mini and BlackBerry browsers do it to catch the communication from the beginning and decrypt it so that they can be compressed for faster browsing. This technique is wrong – in my opinion – as it facilitates eavesdropping but then, the companies say nothing is logged. When you type in an URL, click a link or bookmark, you ask the browser to make a connection (preferably) with the secure version of the website. The Man in the Middle creates a fake certificate that is hard to be identified as faulty as website certificates have the same format irrespective of the Certificate Issuing Authority. The Man in Middle successfully spoofs a certificate and creates a THUMBPRINT that is checked against the “Certificate Authorities that your browser already trusts”. That is, it appears that the certificate was issued by a company that is added to the list of your browsers’ trusted certificate authorities. This makes it believe the certificate key is valid and provides encryption data to the Man in the Middle. Thus, the Man in Middle now has the key to decrypt the information you are sending over that connection. Note that Man in the Middle is also working on the other side by sending your info to the website – sincerely but in a way that it can read it. This explains Website HTTPS spoofing and how it works. It also indicates that HTTPS is not fully secure. There are a few tools that would let us know that there is a Man in the Middle unless one is a highly trained computer expert. For the common man, the GRC website offers a method to retrieve THUMBPRINT. You can check out the certificate THUMBPRINT at GRC and then match it with the one you retrieved using PAGE INFO. If they match, it is okay. If they do not, there is a Man in the Middle.
