| ▲ | yjftsjthsd-h 2 hours ago | ||||||||||||||||||||||||||||||||||
Oh, yes, I missed that the TOTP machine was compromised:\ Would that then imply that it would have been okay if codes came from a separate device, eg. a TOTP app on a Palm OS device with zero network connectivity? (Or maybe these days the easiest airgapped option is an old android phone that stays in airplane mode...) | |||||||||||||||||||||||||||||||||||
| ▲ | dcrazy 2 hours ago | parent | next [-] | ||||||||||||||||||||||||||||||||||
The easiest approach is a provider-issued hardware dongle like a SecurID or Yubikey. Lack of end-user programmability is a feature, not a bug. | |||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||
| ▲ | nurettin 2 hours ago | parent | prev [-] | ||||||||||||||||||||||||||||||||||
Yes, unfortunately authenticator apps just generate TOTP codes based on a binary key sitting in plain sight without any encryption. Not that it would help if the encrypting/decrypting machine is pwned. | |||||||||||||||||||||||||||||||||||