Using https via proxy to transfer financial data

I have a problem now. I need to access realtime senstive financial data. Username/password on large banking and trading account. However the server is not accessble from all locations. IP package loss is 80% and PING is 1000ms from some locations. So I have to use a proxy to get faster and more reliable connection.

The problem I had with HTTP proxy was that HTTP proxy uses their own DNS. So if I log in to etrade.ru via a Russian proxy, the russian proxy can set DNS of etrade.ru to 192.168.0.101 and basically let 192.168.0.101 to receive my username and password on port 443.

Secondly, I remember seeing HTTPS communication was using Public Keys method, but the transmission of Public Keys can be hacked. Let's say A<->B and there is a middle. Middle can do this:

A->middle: give my public key to B
Middle: changed the public key of A to a faked one
Middle->B: this is the faked A key

B->middle: this is the secured message to send to A using faked key
Middle: decode message using faked key then encode with A's key
Middle->A: here is the secured message, I did not read it. Haha.

Does this senario applys to all HTTPS?

 

 

 

 

Top