Open nakedible-p opened 6 years ago
Agreed, these parameters can also be conveniently set in the team policy in the sigchain. Since they have to be known at key generation time, it might make sense to generate a new SSH keypair for team-related accesses.
Currently Krypton support only requires the phone to be unlocked to allow acceptance of an operation - this is kind of two-factor, but not really:
There are many policies which require strict two-factor authentication (such as PCI DSS), which is currently not possible with Krypton.
The proposal would be to add
setUserAuthenticationRequired
to a key, which allows for either biometric authentication (fingerprint) or secure lock screen authentication (PIN code). Also,setUserAuthenticationValidityDurationSeconds
is used to control how long any PIN code authentication is valid. These would need to be set when generating the key.