You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TrayTOTP for KeePass (.NET) on desktop systems might sometimes store formats such as 30;6;https://www.google.com/ in TOTP Settings, with the intent to use the Date header from a HTTP query as a source for a time delta. Currently, in KeePassium, these entries seem to be skipped entirely, and treated as if there's no TOTP.
Diag.warning("Unexpected TOTP settings number [expected: 2, got: \(settings.count)]")
returnnil
}
Keepass2Android, for example, does not implement this, but shows a warning instead when viewing one of these entries notifying the user that, indeed, time correction is not implemented:
It is tempting to implement this properly, with actual network requests. However, I am not sure whether arbitrary network requests would be an acceptable behavior for KeePassium... Will probably just ignore the URL parameter for now...
TrayTOTP for KeePass (.NET) on desktop systems might sometimes store formats such as
30;6;https://www.google.com/
inTOTP Settings
, with the intent to use theDate
header from a HTTP query as a source for a time delta. Currently, in KeePassium, these entries seem to be skipped entirely, and treated as if there's no TOTP.KeePassium/KeePassiumLib/KeePassiumLib/db/totp/TOTPGenerator.swift
Lines 106 to 109 in be35b22
Keepass2Android, for example, does not implement this, but shows a warning instead when viewing one of these entries notifying the user that, indeed, time correction is not implemented:
https://github.com/PhilippC/keepass2android/blob/ee6b7c4fe0257af35eed0eed09c83721db72e94c/src/keepass2android/Totp/TrayTotpPluginAdapter.cs#L147-L148
The text was updated successfully, but these errors were encountered: