Skip to content
This repository has been archived by the owner on Nov 7, 2023. It is now read-only.

Support two-factor authentication #93

Open
nakedible-p opened this issue Apr 8, 2018 · 1 comment
Open

Support two-factor authentication #93

nakedible-p opened this issue Apr 8, 2018 · 1 comment

Comments

@nakedible-p
Copy link

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:

  • lock screens are not mandatory
  • many users have a setting to keep phone unlocked when on body
  • many users have a setting to keep phone unlocked when a certain bluetooth device is near
  • lock screen may be opened by a really simple pattern, or perhaps just a swipe

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.

@kcking
Copy link
Contributor

kcking commented Apr 9, 2018

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants