-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Only first TOTP is valid #82
Comments
This might be fixed in #27 . Do you have a chance to compile the App from master? |
Hi @MaVo159 ! |
App version: 0.2, Firmware version 0.7 I may get to compiling it from master a couple of days from now. Will report back if I do. If you update the .deb on the website, I can try immediately. |
I can't build with your build instructions. I am not very familiar with QT, otherwise I could probably figure it out. Are you sure your qt4 instructions still work? The problem is that QtWidgets isn't found. |
I think qt4 is obsolete. Pl try qt5 instead. |
Issue is still present in git. I have encountered this on a variety of machines in the meantime. Both Debian testing and stable are affected. How has this not come up yet? It seems easily reproducible. On another note, please remove the wrong build instructions and provide instructions that don't require jumping through hoops like downloading qt5 from a 3rd party website. There are qt5 dev packages in recent distributions. |
In my opinion it is the best way to compile against the "Up to Date" Sources which you can pull from the original website of the QT Project. Handling all the specific distributions and the different requirements inside the documentation is much more complicated and makes a readme bigger as needed. But what is your special Problem? Which step fails? |
@jans23 you set the status to prio:medium. In reason of the build instructions or the TOTP issue? |
Regarding the TOTP issue. As you mentioned, more information would be |
Sorry, I should have written that more clearly: With "Issue still present in git" I meant that I can reproduce the TOTP issue with the latest revision. Furthermore, I have reproduced the TOTP issue on many machines (at least 4) with different Debian versions. |
I cant reproduce it cause i didn't have an Nitrokey Pro. |
I don't care about QT4, but a list of packages for QT5 like the one that used to work for QT4 would be pretty great. I tried for a bit but couldn't figure it out. |
I think QT4 won't work anymore so it should be removed from the README |
@jans23 Full Agree |
Unfortunately it doesn't look like I'll have time to debug the app anytime soon. Jan, I assume you have a nitrokey pro. Can you reproduce this? |
Hi @MaVo159 ! |
Hi @MaVo159 ! Please check is it working for you. I have checked it with scenario written in pull request. #88 |
Yep, works for me. |
I am using a Nitrokey Pro on Debian, and I am not sure if this is a firmware or app issue.
After using TOTP once only 000000 returned on subsequent uses.
Unplugging or quitting the app resolves the issue for one use.
Seems odd, since I would have expected other people to notice this.
I have not tested if the issue occurs with HOTP.
Anything I can provide to help debugging?
The text was updated successfully, but these errors were encountered: