Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

1Password for SSH and Git (Beta)

developer.1password.com

Post reply on HN
Print view View original

1–10 of 406 posts

Re: 1Password for SSH and Git (Beta)

#2

Post by tiernano »

hmmm.... this could make me move from LastPass to 1Password... after krypt.co got bought by Akamai and discontinued work on their developer stuff, i have been looking for a better way of managing SSH keys... this might be it...

Re: 1Password for SSH and Git (Beta)

#5

Post by nerdawson »

I’ve been treating SSH keys in the same way I would a password. Each service gets a new key generated for it.

From doing some reading though it sounds like I might be wasting my time. Apparently it’s fine to have one key for an individual machine and to use that for everything.

What’s everyone else’s take on that? Are you reusing a single key or generating each time?

Re: 1Password for SSH and Git (Beta)

#6

Post by geewee »

nerdawson wrote: post #5

I’ve been treating SSH keys in the same way I would a password. Each service gets a new key generated for it. From doing some reading though it sounds like I might be wasting my time. Apparently it’s fine to have one key for an individual machine and to use that for everything. What’s everyone else’s take on that? Are you reusing a single key or generating each time?

I'm reusing the same key per machine - but it's mostly just due to convenience and laziness.

Re: 1Password for SSH and Git (Beta)

#7

Post by kafrofrite »

tiernano wrote: post #2

hmmm.... this could make me move from LastPass to 1Password... after krypt.co got bought by Akamai and discontinued work on their developer stuff, i have been looking for a better way of managing SSH keys... this might be it...

I use both, almost daily (paid versions) since ~2015ish. IMHO, 1password is way better than lastpass. That being said, lately 1password has shifted some of their focus towards more enterprise features (secrets etc.) so I don't know for how long my opinion will remain valid :)

Re: 1Password for SSH and Git (Beta)

#8

Post by fredley »

nerdawson wrote: post #5

I’ve been treating SSH keys in the same way I would a password. Each service gets a new key generated for it. From doing some reading though it sounds like I might be wasting my time. Apparently it’s fine to have one key for an individual machine and to use that for everything. What’s everyone else’s take on that? Are you reusing a single key or generating each time?

A mix. Typically I'll use one key per machine and add those keys in the places they need to be. This is good as you're reasonably well protected if that machine gets lost or stolen. The nature of public key cryptography means there's no risk associated with handing over your public key to many different places.

However sometimes it's practical to use the same (private) key in multiple places. I do this for access to low-risk stuff like ssh access to my raspberry pis. I wouldn't ever move a private key around for anything remotely dangerous though.

Re: 1Password for SSH and Git (Beta)

#9

Post by ammmir »

nerdawson wrote: post #5

I’ve been treating SSH keys in the same way I would a password. Each service gets a new key generated for it. From doing some reading though it sounds like I might be wasting my time. Apparently it’s fine to have one key for an individual machine and to use that for everything. What’s everyone else’s take on that? Are you reusing a single key or generating each time?

default SSH key is the same one for GitHub (since they leak users’ pubkeys anyway), and private repos (eg. hosted GitLab instances) get their own keys. not really sure if it buys any privacy though.
Post reply on HN