logoalt Hacker News

thecopy • today at 7:09 AM • 7 replies • view on HN

I recommend everyone to move your plantext secrets from ~/.kube/config, ~/.ssh etc into a password-manager. You can tell Claude to adjust the config files to get the secrets from 1Password when they are needed with TouchID requirements etc.


Replies

dewey • today at 7:50 AM

These days I’m getting so many 1Password prompts for agents pulling env variables out of it and with very little context of what is being accessed by who (The dialog 1Password shows is pretty bad) that it would be very easy for something to slip in there.

➕ show 1 reply
jwr • today at 8:31 AM

I have been using Yubikeys for years, according to this guide: https://github.com/drduh/yubikey-guide

The nice thing is that using the private key requires physical touch. That means that AI itself (or a remote attacker, for that matter) can't do things unless I confirm.

➕ show 1 reply
sally_glance • today at 7:22 AM

How would that help when your workstation is compromised? They can just steal your authentication the moment you log in through the password manager

➕ show 1 reply
AdamN • today at 10:49 AM

My secret is `4`. Is that ok? Do I still need to move it??

➕ show 1 reply
littlecranky67 • today at 7:38 AM

as for ssh keys, you can generate your keypair in secure enclave and reuiqre touchId for every new ssh session. The private key never leaves the secure enclave.

➕ show 1 reply
speedgoose • today at 7:35 AM

Isn’t the password manager a prime target too?

febusravenga • today at 7:49 AM

you know most password managers have open sockets, or other channels to other local processes to interact with and allow stealing entries?

you know most tools like gcloud, bitwarden, etc store auth keys just in dotfiles too?

Local compromise is KO now, and we can't do shit on platforms like MacOs didn't research Linux recently