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
To allow applications to validate user input before sending it to the device (see d-e-s-o/nitrocli#161), it would be nice to be able to access some OTP- and PWS-related properties using libnitrokey:
TOTP and HOTP slot counts
PWS slot count
maximum OTP name and secret length
maximum PWS name, login and password length
As far as I know, these values are the same for all supported devices, but are likely to change in the future. Therefore I suggest to not have them as constants but to add functions that return the value for the currently connected device instead.
If you don’t object, I’ll prepare a PR soon.
The text was updated successfully, but these errors were encountered:
This patch adds getters for the number of PWS, TOTP and HOTP slots on
the current device and the maximum length of a PWS slot name, login and
password as well as a OTP slot name and secret.
FixesNitrokey#197.
This patch adds getters for the number of PWS, TOTP and HOTP slots on
the current device and the maximum length of a PWS slot name, login and
password as well as a OTP slot name and secret.
FixesNitrokey#197.
To allow applications to validate user input before sending it to the device (see d-e-s-o/nitrocli#161), it would be nice to be able to access some OTP- and PWS-related properties using libnitrokey:
As far as I know, these values are the same for all supported devices, but are likely to change in the future. Therefore I suggest to not have them as constants but to add functions that return the value for the currently connected device instead.
If you don’t object, I’ll prepare a PR soon.
The text was updated successfully, but these errors were encountered: