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

51–60 of 406 posts

Re: 1Password for SSH and Git (Beta)

#51

Post by turboponyy »

trabant00 wrote: post #20

My SSH key and passphrase are the holy of holies security wise. It's such a simple, mature, battle tested, open solution. Why would I put that in a proprietary opaque solution that has had multiple recent serious vulnerabilities? And why would I replace the openssh agent with 1password agent? They don't even offer additional functionality over the open tools. "Autofill public keys in your browser for Git and other cl…

cat key | xclip -selection clipboard # is even easier after you alias the second part (edit: or whatever the Wayland equivalent for xclip is)

Re: 1Password for SSH and Git (Beta)

#52

Post by toyg »

vladvasiliu wrote: post #40
SomeHacker44 wrote: post #32

Earlier quoted context omitted.

I tried 8 on Windows. I went back to 7 after a week. * Search is just plain broken. This was the number one reason i scrapped it. * Managing multiple vaults (i have over a dozen) is unusable. * The UI is terrible, it takes way more space to show less information than 7. * The browser integration (FF) seemed to work poorly. Basically, once 1Password stops supporting 7, they will have lost me and anyone I can influence…

While I fully agree with your issues, and have experienced them too, (although comparing v8 on Linux to v7 on Mac – I don't use 1Password on Windows), those are just UI/integration issues. I don't think they're because of electron, but rather because the remake of the UI is poor. FWIW, my main gripe is having to unlock each vault separately, as opposed to a single unlock as used to be the case on Mac / iPhone.

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

Electron makes integration harder.

Re: 1Password for SSH and Git (Beta)

#53

Post by ylyn »

Galanwe wrote: post #46
gspr wrote: post #42

Earlier quoted context omitted.

Because the idea of shipping a goddamn browser for each and every little GUI app is revolting and disturbing. What other crazy decisions have these people made?!

How is it different than using a GUI framework like Qt or GTK?

Qt and GTK apps don't usually spawn 5 processes, 300-400 MB of RAM, and take 100+ MB of disk space (because they always ship an entire copy of Electron) just to show a small window.

Re: 1Password for SSH and Git (Beta)

#54

Post by seanw444 »

Galanwe wrote: post #46
gspr wrote: post #42

Earlier quoted context omitted.

Because the idea of shipping a goddamn browser for each and every little GUI app is revolting and disturbing. What other crazy decisions have these people made?!

How is it different than using a GUI framework like Qt or GTK?

Are we really comparing the bloat of Chromium to Qt & GTK?

Re: 1Password for SSH and Git (Beta)

#55

Post by samarthr1 »

Galanwe wrote: post #46
gspr wrote: post #42

Earlier quoted context omitted.

Because the idea of shipping a goddamn browser for each and every little GUI app is revolting and disturbing. What other crazy decisions have these people made?!

How is it different than using a GUI framework like Qt or GTK?

The runtime is much much smaller, fewer layers of.abstractions away?

Re: 1Password for SSH and Git (Beta)

#58

Post by adventureadmin »

How does it work with with `~/.ssh/config`? Mainly, say I have keys in the vault for many machines, if they all get added to the 1password ssh-agent sock, won't you get "Too Many Auth failures", unless there is a way to pair the key to a `Host`? Maybe `~/.ssh/config` can pair keys to a `Host` by fingerprint instead of file?

Re: 1Password for SSH and Git (Beta)

#59

Post by tzs »

trabant00 wrote: post #20

My SSH key and passphrase are the holy of holies security wise. It's such a simple, mature, battle tested, open solution. Why would I put that in a proprietary opaque solution that has had multiple recent serious vulnerabilities? And why would I replace the openssh agent with 1password agent? They don't even offer additional functionality over the open tools. "Autofill public keys in your browser for Git and other cl…

EDIT: Never mind. I misread and thought he was talking about password managers in general, not specifically for public keys.

> They don't even offer additional functionality over the open tools. "Autofill public keys in your browser for Git and other cloud platforms" - really? cat and copy - paste is now too hard?

In the case of browsers cat and copy/paste is often more risky than having code such as a password manager fill the fields. Password managers are less likely to be fooled by sites using tricks with their names to pose as other sites.

If you are sufficiently careful to be sure you will not be tricked by phishing attempts then cat and copy/paste should be fine.

Re: 1Password for SSH and Git (Beta)

#60

Post by bvm »

trabant00 wrote: post #20

My SSH key and passphrase are the holy of holies security wise. It's such a simple, mature, battle tested, open solution. Why would I put that in a proprietary opaque solution that has had multiple recent serious vulnerabilities? And why would I replace the openssh agent with 1password agent? They don't even offer additional functionality over the open tools. "Autofill public keys in your browser for Git and other cl…

> that has had multiple recent serious vulnerabilities?

has it? could you detail them, i'm OOTL.

Post reply on HN