Author

Topic: MtGox SSL certificate security warning on Android (Read 3291 times)

Jan
legendary
Activity: 1043
Merit: 1002
Seems fixed now.
rjk
sr. member
Activity: 448
Merit: 250
1ngldh
The main site's certificate is signed by Verisign, but the socket connection for displaying the current price is served with a StartSSL certificate. Likely, the StartSSL root cert isn't trusted on your device.
but it says that the problem cert is issued by verisign
Yeah I noticed that, but I guessed maybe that the "view certificate" dialog defaulted to opening the main site cert, instead of the one that was causing the error. Not sure, but in any case you need to compare the cert fingerprint with one from a trusted computer/connection, and make sure they match.

I had the same issue on my Blackberry until I added the StartSSL CA cert to my trusted roots, and then I stopped getting errors. YMMV.

legendary
Activity: 2058
Merit: 1431
The main site's certificate is signed by Verisign, but the socket connection for displaying the current price is served with a StartSSL certificate. Likely, the StartSSL root cert isn't trusted on your device.
but it says that the problem cert is issued by verisign
hero member
Activity: 640
Merit: 500
Vanity of vanities; all is vanity...
Did anyone tell Mt Gox about this?
sr. member
Activity: 334
Merit: 250
getting same SSL error on mobile client on android, when trying to see BTC history. Everything else seems to work - weird.
legendary
Activity: 924
Merit: 1004
Firstbits: 1pirata
maybe they forgot to add the intermediate cert For StartSSL, http://www.startssl.com/?app=25#31
rjk
sr. member
Activity: 448
Merit: 250
1ngldh
The main site's certificate is signed by Verisign, but the socket connection for displaying the current price is served with a StartSSL certificate. Likely, the StartSSL root cert isn't trusted on your device.
Jan
legendary
Activity: 1043
Merit: 1002

Visiting https://mtgox.com using the web-browser on my Android 2.2 device gives me a security warning.



Certificate details:



This does not happen on my iPhone, desktop Chrome/Firefox browser.

I don't think that this was the case a few days ago.

I wonder whether they have recently updated their certificate and that it has been issued by a root certificate that my device does not know.
Jump to: