This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
password_management [2024/03/01 16:53] – [key management] qlyoung | password_management [2024/03/01 19:01] (current) – [tldr] qlyoung | ||
---|---|---|---|
Line 5: | Line 5: | ||
==== tldr ==== | ==== tldr ==== | ||
- | {{ : | + | {{ : |
I use [[https:// | I use [[https:// | ||
Line 41: | Line 41: | ||
==== key management ==== | ==== key management ==== | ||
+ | |||
+ | {{ : | ||
This setup requires my personal GPG keypair to unlock the store. This means that the keypair has to be accessible to every device that needs access to passwords. | This setup requires my personal GPG keypair to unlock the store. This means that the keypair has to be accessible to every device that needs access to passwords. | ||
- | A GPG keypair is for practical purposes two files, one containing the public key and the other containing the private key. It's very important to the security of any system involving GPG that they private key file not be exposed to anyone. For this reason it's usually encrypted with a symmetric password. If you use the conventional setup, this symmetric password effectively becomes the " | + | A GPG keypair is for practical purposes two files, one containing the public key and the other containing the private key. It's very important to the security of any system involving GPG that the private key file not be made public. For this reason it's usually encrypted with a symmetric password. If you use the conventional setup, this symmetric password effectively becomes the " |
- | However, even though the keypair is itself encrypted, having it stored on disk isn't ideal from a security perspective - particularly on mobile, which are very exposed and historically very insecure. It's better if we don't store the key on disk at all. To accomplish this I store my keypair on a [[https:// | + | However, even though the keypair is itself encrypted, having it stored on disk isn't ideal from a security perspective - particularly on mobile |
On my desktop and laptop, whenever I need a password, I'm prompted to plug in and unlock my yubikey with a 6 digit pin. The encrypted file containing the password is then sent, over USB, to the embedded processor on the yubikey. The yubikey decrypts it using the GPG private key and sends back the cleartext contents. The flow is the same on my phone, except that communication occurs over NFC so I am prompted to tap my yubikey on the device. | On my desktop and laptop, whenever I need a password, I'm prompted to plug in and unlock my yubikey with a 6 digit pin. The encrypted file containing the password is then sent, over USB, to the embedded processor on the yubikey. The yubikey decrypts it using the GPG private key and sends back the cleartext contents. The flow is the same on my phone, except that communication occurs over NFC so I am prompted to tap my yubikey on the device. | ||
Line 60: | Line 62: | ||
There are plugins that provide browser autofill which I used to use. | There are plugins that provide browser autofill which I used to use. | ||
- | Currently I have a global system shortcut ('' | + | Currently I have a global system shortcut ('' |
For git synchronization, | For git synchronization, |