Live data from Hacker News

1Password for SSH and Git (Beta)

developer.1password.com

331–340 of 406 posts

Re: 1Password for SSH and Git (Beta)

#331

Earlier quoted context omitted.

I believe you can attach files, so that might be an option for keys/certs.

Attaching files is the worst functionality of 1password. I put images of my health insurance card in 1pw. do this. now, pretend you want to upload those image to a web portal that's asking for your insurance information. To pretend, just try and put the images of your insurance card into an email body to yourself. See how many clicks it takes.

I find it to be a decent experience (and use it for exactly what you mentioned).

Comparing the two methods I've personally used to store my insurance card below. What are you comparing to?

1Password:

  - Search
  - Click on the relevant entry
  - Click "Quick Look"
  - Click down menu
  - Click show in Finder
  - Drag onto upload form field
Google Drive:

  - Search
  - Right click
  - Download
  - Right click on downloaded file botton
  - Show in finder
  - Drag onto upload form field
  - Right click on file
  - Delete
Local Filesystem

Not really worth comparing. Could be made much quicker than anything else.

Re: 1Password for SSH and Git (Beta)

#332
post #331

Earlier quoted context omitted.

Attaching files is the worst functionality of 1password. I put images of my health insurance card in 1pw. do this. now, pretend you want to upload those image to a web portal that's asking for your insurance information. To pretend, just try and put the images of your insurance card into an email body to yourself. See how many clicks it takes.

I find it to be a decent experience (and use it for exactly what you mentioned). Comparing the two methods I've personally used to store my insurance card below. What are you comparing to? 1Password: - Search - Click on the relevant entry - Click "Quick Look" - Click down menu - Click show in Finder - Drag onto upload form field Google Drive: - Search - Right click - Download - Right click on downloaded file botton -…

I do really hate how links between attachments and password entries get broken pretty easily, though. I think this is an area for improvement.

Re: 1Password for SSH and Git (Beta)

#333

Earlier quoted context omitted.

Not really. What is the case for not using well vetted best practices and replacing those with an unvetted proprietary solution? What problems does 1PW solve that necessitates taking on such risk? We're not talking about social media PWs. ssh keys are not something to add risk to, eh.

Who says your best practices are well tested?

Who says they are my best practices? They are established industry best practices.

So again I'll ask: what case does 1PW make to deviate from those?

Re: 1Password for SSH and Git (Beta)

#334
post #17

Earlier quoted context omitted.

I don't get the hate on Electron. Is it often bloated? Yes, sure. Has it allowed some of these excellent third party apps to make the move to Linux? Absolutely. I've been utterly surprised and excited by how much better 1Password has gotten over the last two years on Linux. We're seeing real parity with the OSX side of the house. Would I love native apps? Again, sure. But I really don't care. It runs pretty fast on m…

Apparently 1password is developed Linux-first now.

Nah it's browser/javascript first using Electron :(

Re: 1Password for SSH and Git (Beta)

#335

Earlier quoted context omitted.

Maybe I don’t understand, but couldn’t you use the notes section? Wrap whatever you need in triple backticks to create a code block?

Maybe I have an ssh key and notes. With this setup I can only do 1.

I store my ssh keys, with notes, in the same note. I wrap the ssh key in backticks and put the relevant notes above or below the key. Granted I can't just triple click to select the entire note then copy, I have to interact with it more to copy it, but I very rarely copy my ssh keys. Like once every few years when I'm setting up a new machine. So maybe you're copying them more than I am and it's more of an issue

Re: 1Password for SSH and Git (Beta)

#338

Earlier quoted context omitted.

SSH keys have both a private and a public file. The private file is multi-line text. I don't like putting the private key in the notes field, because its name is still "notes" (but I'd prefer the label be the key's file name), it's actually markdown formatted text, not literal text, and what if I still want to write a note, but I've already used the notes field for the key? HTTPS certificates including multiple certi…

Thank you for the feedback! We spoke about it internally many times in the past but couldn't get the solution implemented because there was always something in the way. After reading your comments and I talked to the team and we just merged a change that should appear in the nightly build and make the handling of the multi-line fields better. Having a single core in 1Password 8 makes things so much easier when it com…

Amazing, I wanted this too. Thank you.

1Password has literally blown me away every second that I've used it. And the ability to sync MFA between all your devices was the push that I needed to start using MFA.

I do have a feature request though - any chance we could lock our 1Password wallet using 2FA with SMS (like Office365 or banks) rather than a device authentication key? Main concern is that personal devices are breaking all the time ... SMS is "strong enough" and yet pretty much the only second factor that is convenient to recover in the event of a disaster.

Re: 1Password for SSH and Git (Beta)

#339
post #52

Earlier quoted context omitted.

> those are just UI/integration issues. I don't think they're because of electron Electron makes integration harder.

Fair enough, but I expect browser integration and so forth to be done via the backend, which is rust, so native.

Rust is hardly a "desktop-native" language. I expect it will have to jump through all sorts of hoops to interface with the Obj-C underpinnings of MacOS desktop libraries.

Regardless, even if the backend were pure Obj-C, the point is still that now you have a UI stack and a backend stack, instead of a single desktop-native stack, and you have to manage their communications. But I guess the money they save by not managing desktop-specific codebases eventually adds up...

Re: 1Password for SSH and Git (Beta)

#340
post #52

Earlier quoted context omitted.

> those are just UI/integration issues. I don't think they're because of electron Electron makes integration harder.

Why? You don't have to use Electron for everything, you can integrate using whatever language you want and some RPC, like Keybase did.

And that's still more involved (and slower) than "just use this function that desktop vendors helpfully provided for the purpose".
Post reply on HN