Bitcoin Forum
May 28, 2024, 05:21:41 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: MtGox and Google-Authenticator what happens if phone dies/lost  (Read 5170 times)
matthewh3 (OP)
Legendary
*
Offline Offline

Activity: 1372
Merit: 1003



View Profile WWW
September 09, 2012, 02:54:04 PM
 #1

Hi can anyone tell me what to do if you use MtGox and Google-Authenticator and your phone packs up or you loose it.  Thanks.

Stephen Gornick
Legendary
*
Offline Offline

Activity: 2506
Merit: 1010


View Profile
September 09, 2012, 03:03:03 PM
Last edit: September 11, 2012, 02:39:46 AM by Stephen Gornick
 #2

Hi can anyone tell me what to do if you use MtGox and Google-Authenticator and your phone packs up or you loose it.  Thanks.

If you made a copy of the OTP key at the time you scanned it from Mt. Gox's site, you can add the same key to Google Authenticator (or any OTP app) on another mobile  or as a desktop application if needed, using this:

 - http://code.google.com/p/cuteauthenticator/

or
 - https://github.com/mclamp/JAuth

To keep your backup of the key available online somewhere, you could encrypt it with GPG and store the encrypted version someone where you have access even if your phone is gone.  (e.g., if your e-mail also requires OTP authentication and your phone is gone, you aren't getting into that either to get access to your encrypted Mt. Gox OTP key.)

If you haven't made a backup of the key, be prepared to provide identification (again) matching the verification info the exchange has on file, know recent account history, ..., e.g., last deposits and trades, etc.

Unichange.me

            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █


Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!