4 ms·
Leveraging that existing key is a downright anti-feature though. You should try to minimize the scope controlled by any given key. You already lean heavily on
by subway 9y ago
Leveraging that existing key is a downright anti-feature though. You should try to minimize the scope controlled by any given key.
You already lean heavily on OpenSSL, so it doesn't make a lot of sense why you wouldn't just generate a dedicated key with a `openssl genrsa -out .spiffytool/private.pem`
- ahnick 9y agoI think this is a good idea, b/c as long as the permissions are set on the generated private key to only be readable by the user, then the same level of security would be provided as accessing the user's private ssh key. It would also be nicer in situations like remote servers where the private key is not available due to security reasons. The intention was in these situations to generate your own keys using SSH, but there's no reason to make the user go through that exercise. I will look at making the change. Thanks for the suggestion.
- leni536 9y agoI couldn't agree more. I don't even use the default ssh key, I have separate keys for separate servers. Even separate keys for separate github repos.