search

tadfisher / pass-otp

A pass extension for managing one-time-password (OTP) tokens
GNU General Public License v3.0
1.3k stars 86 forks source link

generated otp code is not correct #183

Closed formula-spectre closed 1 year ago

formula-spectre commented 1 year ago

I have the same uri on aegis autheticator on my phone and on pass on my desktop, and there is a mismatch; I don't know what to provide, so pass version: 1.7.4 zbar version: 0.23.92 oath-toolkit version: 2.6.7 distro: gentoo

yohannd1 commented 1 year ago

I've recently noticed my OTP codes are not matching the ones I have in Authy. Not fully sure when this started to happen, but it used to work fine before. Also using pass 1.7.4.

zoj613 commented 1 year ago

Same here. I recently experienced this on linkedin. Using OTP with Aegis as the authentication app works well, but if I take the same URI and insert in on pass-otp, the generated OTP does not work.

EDIT: I was able to resolve this using the suggestion made here: https://github.com/tadfisher/pass-otp/issues/138#issuecomment-782767357

@formula-spectre

sereinity commented 1 year ago

TOTP (timed one time password) relies on the clock to generate the code, it's mandatory to have a device that has its clock correctly configured. It's not a bug of pass-otp.

One way to ensure that a device has its clock correctly configured is to rely on a NTP service as said in https://github.com/tadfisher/pass-otp/issues/138#issuecomment-782767357

formula-spectre commented 1 year ago

apologies for the late response. I'm not gonna lie, I forgot about this issue completely.
installed chrony as an NTP, and now the generated tokens are correct. thanks!