michealzh / androidtoken Goto Github PK

At the moment we only allow numerical values in the token serial number field. 
This should be changed so that we can allow letters and numbers.

Usage of NTP to correct time within calculation of time based OTPs

What steps will reproduce the problem?
1. when displaying the pin keyboard we are showing a general keyboard when we 
should just display the numerical input keyboard.
2.
3.

What is the expected output? What do you see instead?
Digits keyboard

What version of the product are you using? On what operating system?


Please provide any additional information below.

1. Trying to generate appropriate TOTP for the following URL, for example:

otpauth://totp/android?secret=VPGRENCWPA======

The base32 encoded 'secret' in the above URL had to be padded, and the original 
secret was "abcd12345678" in this example.

2. The 'secret' after parsing the URL will be VPGRENCWPA (i.e the '=' signs in 
the 'secret' are skipped as the '=' sign is used as a token to split the 
parameters in TokenList.java).

3.  Because of that, and because the default padding used in Base32.java is '=' 
sign, the decoded secret will be 'abcd1234563448d159e0' instead of the correct 
value of 'abcdef12345678'.

I was trying to use the androidtoken 2.0.2 on Samsung Galaxy phone, running 
Android 4.2.2, and it was generating wrong TOTP codes.  So, I downloaded the 
androidtoken sources on to Windows machine, and tried it out (after 
retrofitting it for commandline usage) using JDK 1.7 and found the above cause.

I changed the default padding in the Base32.java to use '.' instead of '=' and 
then, it works fine.

What steps will reproduce the problem?
1. Long click the PIN dialog
2. Notice the lack of clipboard copying
3. Make sad face :(

What is the expected output? What do you see instead?
Would expect long pressing to copy the generated pin to the system clipboard.

What version of the product are you using? On what operating system?
Latest.

Please provide any additional information below.

I've created a patch to add this functionality (attached). I've really changed 
3 things:

1. Bump minSdkVersion to "4", this was actually need in the unpatched version 
for the largeScreens... etc android params in the manifest.

2. Removed the 10 second time out (annoyed me that I had to memorize the pin in 
10 seconds and then it's gone forever.

3. Added setOnLongClickListener to the PIN dialog TextView so long pressing the 
PIN copies it to the clipboard (and displays a toast notification that it did 
so).

Not sure if anyone is actively developing this project anymore...

Why isn't the application in android market?
Since I'm an android developer, if you want, i could publish the app (for free 
obviously) :)
Let me know if you're interested! :)

Cheers!

I am using the f-droid build. I was migrating my setup from Google 
Authenticator's database file.

When manually importing seeds in base32, I have encountered that 
16-character-long seeds work correctly, but 26-character-long ones (e.g., 
mt.gox) do not. The tokens displayed are different to those of Google 
Authenticator (those expected by the website).

Workaround: I converted the code to hex using the base32tohex function from
http://gauth.apps.gbraad.nl/ in a JS console. When importing the hex seed to 
androidtoken, the right codes get displayed.

Simplified example: Test the base32 seeds:
ABABABABABABABAB
vs
ABABABABABABABABAB
The first one (16 bytes) works, while the second one does not.

Hi, to simplify provisioning of a token, it would be great if you implemented a 
web-based provisioning through a custom URL format. Bonus points if you get to 
reuse the same format as implemented by the iPhone OATH token open-source 
application:
http://code.google.com/p/oathtoken/wiki/WebProvisioning

What steps will reproduce the problem?
1. I am not a geek guy
2. But I always go on doing something geeky
3. I want use androidtoken for Google 2 step verfication

What is the expected output? What do you see instead?
IMP: THERE MUST BE DEFAULT BARCODE SCANNER APP FOR ANDROID. I HAVE INSTALLED 
BARCODE SCANNER APP OF ZXing Team. No problem it is of GOOGLE.........BUT....IT 
MUST BE ABLE TO DO ALL FUNCTIONS OF QR DROID APP....SO THAT EVERYTHING IS 
POSSIBLY...AS I SPECIALLY INSTALLED IT FOR GOOGLE AUTH AND ANDROID 
TOKEN..OTHERWISE NO USE OF IT..

What version of the product are you using? On what operating system?
Android IceCreamSandwich 4.0.4

Please provide any additional information below.

Widget showing actual OTP

The OTPs are calculated incorrectly, when base32-encoded seeds are entered in 
lowercase instead of uppercase.

This is also an issue when using QR Codes.

Used Version: androidtoken 2.02 on CM11.

What steps will reproduce the problem?
1. HTC One uses ICS which means the menu button is not available.
2.
3.

What is the expected output? What do you see instead?
The UI pattern for the application needs to be updated to included for this 
issue.
http://blog.gsmarena.com/google-urges-developers-to-remove-the-menu-button-from-
android-apps-suggests-using-the-action-bar-instead/

Please use labels and text to provide additional information.