hanskorg / google-authenticator-rust Goto Github PK

I've been playing around with the discrepancy parameter, and it definitely doesn't work in seconds, but in a larger time interval.
I think because the time is first divided by 30, and then you create the range [x-discrepancy, x+discrepancy], then the actual discrepancy is multiplied by 30?

The description in the docs saying The parameter discrepancy indicates number of seconds ago that a code may be generated. is incorrect, as what it really indicates is the number of half-minutes ago and in the future that the code may be generated?

I think the docs or the usage of the parameter discrepancy should be modified, no?

how can i check when the qr code is scanned to run something afterwards?

thank you for this project, it helps me a lot

can you remove println code or replace it with log?

Calling let code = auth.get_code(secret,0).unwrap();
it's broken on my machine it always return the same code. This line https://github.com/hanskorg/google-authenticator-rust/blob/master/src/google_authenticator.rs#L102 return always 0
`
If I try to pass the timestamp/30 instead of zero to the function sometime the code matches sometimes does not (probably rounding problem).

When I add v0.4.0 in Cargo.toml, I get the following error:

error[E0433]: failed to resolve: use of undeclared crate or module `google_authenticator`
   --> src/path/to/file.rs:229:20
    |
229 |         let totp = google_authenticator::GoogleAuthenticator::new();
    |                    ^^^^^^^^^^^^^^^^^^^^ use of undeclared crate or module `google_authenticator`

# Cargo.toml
[dependencies]
google-authenticator = { version = "0.4" }

One thing I am confused about is there is a v0.3.0 and v0.4.0 release at crates.io, but as best I can tell, there is no commit in the history of this repo where Cargo.toml had a version of v0.3.0 or v0.4.0.

I don't get the same error for v0.3.0 or v0.2.0.