stateless-workstation-config
secretive
stateless-workstation-config | secretive | |
---|---|---|
1 | 23 | |
22 | 6,892 | |
- | - | |
6.4 | 7.4 | |
3 months ago | 18 days ago | |
Jinja | Swift | |
- | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
stateless-workstation-config
-
How often should I rotate my SSH keys?
> An even more robust approach is to use some kind of hardware token that can sign short-lived ssh keys, and teach all your servers how to deal with those. That’s neat, but it’s hard to deploy (needs custom ssh settings).
Ahem, no. I use Yubikeys for a few years now. They are literally braindead to use, and works out of the box in recent Ubuntu. Here is an Absible role to get started: https://github.com/cristiklein/stateless-workstation-config/...
Stop making excuses and start protecting your SSH keys!
Disclaimer: I'm not compensated in any way by Yubico, but their product is so darn good that I really want people to start using it.
secretive
-
GitHub Passkeys are generally available
Secretive might be what you're looking for: https://github.com/maxgoedjen/secretive
-
Zero Effort Private Key Compromise: Abusing SSH-Agent for Lateral Movement
Good find! I was always curious how this worked.
I'm a big fan of tools like secretive[1] that can help solve this problem by using biometrics to shift the UX/security trade-off and thus make it feasible to always require some kind of authentication to sign a token with a key.
I'm not aware of any tools that do the same for Linux, and a quick Google search doesn't turn up much[2]. It does look like you can at least get a notification[3], though.
This could provide another layer of protection on the user's endpoint device in addition the network monitoring called out in the article. Defense in depth, and all that.
[1] https://github.com/maxgoedjen/secretive
[2] https://unix.stackexchange.com/questions/705144/unlock-an-ss...
[3] https://www.insecure.ws/2013/09/25/ssh-agent-notification.ht...
-
Tell HN: 1Password 8.10.8 update corrupted data
https://github.com/maxgoedjen/secretive
> Secretive is an app for storing and managing SSH keys in the Secure Enclave
-
Software Developer Mac Apps
Secretive, which replaces painfully managing SSH keys from the command line / editor. Getting a Touch ID prompt is so much better, though migrating computers will suck.
-
SSH keys setup, use, and proper OpSec
consider using a higher-security setup. Secretive is an SSH agent for MacOS that stores keys within the host's secure enclave, where they can't be copied off, and can optionally require touchid validation before the key is used. This way, if you forward it the key to an compromised host and an attacker tries to use them, it'll still require a fingerprint (but, balance it with the fact that Secretive doesn't have nearly as many eyeballs checking it, yet!). Likewise, yubikeys can be setup to store SSH keys inside them and require touch to use.
- Secretive: Store SSH Keys in the Secure Enclave
-
Russhian Roulette: 1/6 chance of posting your SSH private key on pastebin
You can store them in the Secure Enclave on OSX and require TouchID to use the key for signing.
See: https://github.com/maxgoedjen/secretive
-
Use TouchID to Authenticate Sudo on macOS
Not exactly connected but the same crowd interested in this topic may also be interested in this tool to store SSH private keys in the Secure Enclave, kind of like what can be done with a YubiKey:
https://github.com/maxgoedjen/secretive
I've been looking for something like this for 3-4 years but only found it six months ago (in an HN thread). I use separate keys for every use case, and now know every time a key is used for any purpose, whether it's connecting to source control or my text editor is connecting to a remote VM.
Only thing I haven't figured out is how to do git signatures with these sorts of keys, but I haven't debugged it at all.
-
A sane SSH(1) key management example
On Macs, Secretive [0] is great. It creates keys in the secret enclave, from where they can't be read, only used for signing requests. TouchID authorisation is optional but it's so quick and easy that I keep it on for all keys.
It can also use Smart Cards (Yubikeys are called out by name in the readme).
A forwarded agent will have the same level of security, meaning that if the forwarded agent needs to use a key in Secretive, it will have to be authorised locally - and even if TouchID is disabled, you are notified if a key is used.
[0] https://github.com/maxgoedjen/secretive/
What are some alternatives?
sekey - Use Touch ID / Secure Enclave for SSH Authentication!
bless - Repository for BLESS, an SSH Certificate Authority that runs as a AWS Lambda function
YubiKey-Guide - Guide to using YubiKey for GnuPG and SSH
sharkey - Sharkey is a service for managing certificates for use by OpenSSH
openssh-sk-winhello - A helper for OpenSSH to interact with FIDO2 and U2F security keys through native Windows Hello API
Vault - A tool for secrets management, encryption as a service, and privileged access management
vault-plugin-secrets-onepasswor
rust-u2f - U2F security token emulator written in Rust
pass-import - A pass extension for importing data from most existing password managers
krypton-ios - DEPRECATED Krypton turns your iOS device into a WebAuthn/U2F Authenticator: strong, unphishable 2FA.