Skip to content

Commit 1ff003f

Browse files
author
dvogt23
committed
Notes/tech/security.md
1 parent 18a1b16 commit 1ff003f

File tree

1 file changed

+14
-2
lines changed

1 file changed

+14
-2
lines changed

Notes/tech/security.md

Lines changed: 14 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,8 +13,8 @@ Interest things for security in general:
1313

1414
## Yubikey
1515

16-
Best practice guide: https://github.com/drduh/YubiKey-Guide
17-
Another great guide: https://yubikey.jms1.info
16+
- Best practice guide: [https://github.com/drduh/YubiKey-Guide](https://github.com/drduh/YubiKey-Guide)
17+
- Another great guide: [https://yubikey.jms1.info](https://yubikey.jms1.info)
1818

1919
> [!Warning]
2020
> There is a vulnerability about yubi keys:
@@ -53,6 +53,18 @@ gpg --quick-add-key $KEYID ed25519 auth 1y
5353
gpg --quick-add-key $KEYID cv25519 encrypt 1y
5454
```
5555

56+
## Bitwarden Desktop - ssh key management
57+
doc: [https://bitwarden.com/help/ssh-agent](https://bitwarden.com/help/ssh-agent/#tab-browser-extension-3PjpTaCCPSpz3hcsQ5sznu)
58+
59+
**TLDR;**
60+
1. Open **_bitwarden desktop - settings_** and activate **Enable SSH-Agent**
61+
2. Create a `ssh key` entry in bitwarden _(its enough to paste the private key content)_
62+
1. `\cat id_ed25519 | pbcopy`
63+
3. Set env var export `SSH_AUTH_SOCK=/Users/<user>/Library/Containers/com.bitwarden.desktop/Data/.bitwarden-ssh-agent.sock` (needs to be present for your shell, so add it to your `.zshrc`)
64+
4. Edit your `.ssh/config` and adjust `IdentityFile ~/.ssh/id_ed25519.pub` to use the `.pub` keyfile for reference the private-key of your ssh key agent
65+
66+
To list all available ssh keys, use `ssh-add -L`
67+
5668
## Security quote
5769

5870
> Security is a team sport, and accelerating SFI isn’t just job number one for our security teams – it’s everyone’s top priority and our customers’ greatest need.

0 commit comments

Comments
 (0)