-
Notifications
You must be signed in to change notification settings - Fork 57
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
"OTP failed to fetch time/counter" on airgapped Jade #197
Comments
It's a fair point - how to communicate an initial 'current time' to an airgapped jade so TOTP can work. There is a (bespoke) QR that Jade will accept to set the time - we just need something to create and display it. |
Perhaps a UX screen prompting the user to set the time when required? A QR would need to be scanned within 30s which might not be possible for some users... |
I guess I was thinking a page with a qr which updated every ~5-10s ... but yes, it may be equally easy to just have a simple time entry screen on Jade (either utc only, or with a tz offset). |
both options would fit best, manual input for users having issues scanning fast enough or to read a dynamic QR timestamp for a better UX, Jade could run a timer since the last timestamp update so it can generate several TOPTs in the same session until logout |
Oh yes, once the time is set (after power-up/boot) jade then keeps time internally - it just does not have a clock that is running when powered-off, so needs to be told at every power-on or unlock. |
While it gets implemented, if it happens to be considered, can you provide an example of the string with Unix epoch time that Jade will understand as a set time instruction? I can input it at any FOSS QR generator and scan it. |
When login to Jade Classic with QR PIN or SeedQR it fails to view stored OTPs it says "OTP failed to fetch time/counter" except when connected with Green over Bluetooth.
Is there a workaround preferably over QR to tell Jade the current timestamp so OTP can work 100% offline without relying on a companion app?
Running latest firmware 1.0.33
The text was updated successfully, but these errors were encountered: