Author

Topic: Problems seeting up 2 factor auth on BTC-E (Help please!) (Read 823 times)

member
Activity: 102
Merit: 10
After alot of googling and some trial and error I figured out the problem.

BTC-E provide you an unpadded key basically. Some apps will deal with this others won't.

In my gauth app I had to pad out the key to make it dividable by 8. This was done in my case by adding one extra "=" to the end of the key they provided. Thats the accepted padding for BASE32. You can add any amount of extra "=" to make the total key length dividable by 8.

So there you are, hope this helps someone out! If it did and you are in a generous mood please consider a small donation for my efforts! Smiley

1EQMmUirpFwvQdooD7qR6u9sxRhSgR6cVk
member
Activity: 102
Merit: 10
As per the subject title I can't get 2 factor up and running on my BTC-E account.

For clarity I'm familiar with how 2 factor works and have it setup on my Bitstamp account and several other websites.

My problem is that 1) I don't have the ability to scan QR codes so I always just manually enter the private key (np usually but...), 2) the private key on BTC-E is bizarrely longer than 16 characters / they give a private key and a BASE32 private key. Both the keys they provide are longer than 16 characters and neither produce a 6 digit code when entered into my gauth app.

I've googled and read up a bit on gauth codes but can't find any mention of keys ever being longer than 16 characters. I've tried mailing BTC-E but they replied with a generic "how to setup 2 factor response".

Anyone have this issue with BTC-E? Is there a way to use the long private keys they provide? Thanks for any help!
Jump to: