google-authenticator-android | Open source fork of the Google Authenticator Android app | Authentication library

by google Java Version: v5.00 License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | google-authenticator-android Summary

google-authenticator-android is a Java library typically used in Security, Authentication applications. google-authenticator-android has a Permissive License and it has medium support. However google-authenticator-android has 23 bugs, it has 1 vulnerabilities and it build file is not available. You can download it from GitHub.

The Google Authenticator project includes implementations of one-time passcode generators for several mobile platforms, as well as a Pluggable Authentication Module (PAM). One-time passcodes are generated using open standards developed by the Initiative for Open Authentication (OATH) (which is unrelated to OAuth). Further documentation is available in the Wiki.

Support

Quality

Security

License

Reuse

Support

google-authenticator-android has a medium active ecosystem.

It has 1477 star(s) with 469 fork(s). There are 113 watchers for this library.

It had no major release in the last 12 months.

There are 40 open issues and 52 have been closed. On average issues are closed in 111 days. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of google-authenticator-android is v5.00

Quality

google-authenticator-android has 23 bugs (1 blocker, 0 critical, 10 major, 12 minor) and 510 code smells.

Security

google-authenticator-android has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

google-authenticator-android code analysis shows 1 unresolved vulnerabilities (0 blocker, 1 critical, 0 major, 0 minor).

There are 4 security hotspots that need review.

License

google-authenticator-android is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

google-authenticator-android releases are available to install and integrate.

google-authenticator-android has no build file. You will be need to create the build yourself to build the component from source.

Installation instructions, examples and code snippets are available.

google-authenticator-android saves you 21238 person hours of effort in developing the same functionality from scratch.

It has 41724 lines of code, 1099 functions and 403 files.

It has medium code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed google-authenticator-android and discovered the below as its top functions. This is intended to give you an instant insight into google-authenticator-android implemented functionality, and help decide if they suit your requirements.

Initialize the Authenticator
Sets the contextual action bar for the user
Swaps the ids of two AccountIndexs
Called when a context item is clicked
Initializes the activity
Creates a styled pincode with a 4 - digit string
Removes trailing and trailing newlines
Generates a passcode for the given secret
Handle a touch event
Binds all the field values provided by the constructor
On touch events
Callback for the drag event
Creates a bitmap with the specified position
This method is called when the application is granted
Invoked when the activity is finished
Create the status bar
Intercept the touch event
Create dialog
Initializes the view
Initializes the AuthenticatorActivity
Sets the size of the barcode
Puts the check state of an item
Encodes a byte array into a string
Region > drawable
Draw the divider
Updates the dimension with the desired width and height

Get all kandi verified functions for this library.

google-authenticator-android Key Features

No Key Features are available at this moment for google-authenticator-android.

google-authenticator-android Examples and Code Snippets

No Code Snippets are available at this moment for google-authenticator-android.

Community Discussions

Trending Discussions on google-authenticator-android

Matching TOTP implementation with Google Authenticator

QUESTION

Matching TOTP implementation with Google Authenticator

Asked 2020-Apr-07 at 20:57

(Solution) TL;DR: Google assumes the key string is base32 encoded; replacing any 1 with I and 0 with O. This must be decoded prior to hashing.

Original Question

I'm having difficulty having my code match up with GA. I even went chasing down counters +/- ~100,000 from the current time step and found nothing. I was very excited to see my function pass the SHA-1 tests in the RFC 6238 Appendix, however when applied to "real life" it seems to fail.

I went so far as to look at the open source code for Google Authenticator at Github (here). I used the key for testing: "qwertyuiopasdfgh". According to the Github code:

...

ANSWER

Answered 2020-Apr-07 at 20:51

I was tempted to make my own Android application to implement TOTP for my project. I did continue looking at the Java code. With aid of downloading the git repository and grep -R to find function calls I discovered my problem. To get the same pin codes as Google Authenticator the key is assumed to be base32 encoded and must be decoded prior to passing it to the hash algorithm.

There was a hint of this in getEnteredKey() by replacing the 0 and 1 characters as these are not present in the base32 alphabet.

Source https://stackoverflow.com/questions/61072406

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install google-authenticator-android

The APKs for the official version and the open source version of Authenticator are hosted separately. Installing the app should be as simple as downloading the APK from your desired source.
You can install the official (proprietary) version of Google Authenticator from the Google Play Store.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: