Live data from Hacker News

1Password for SSH and Git (Beta)

developer.1password.com

171–180 of 406 posts

Re: 1Password for SSH and Git (Beta)

#171
post #65

Earlier quoted context omitted.

The data that 1Password stores on their end is encrypted with your personal passphrase. So they can't see it even if they want to. Unless their local client was compromised (not impossible - but if your local is compromised you're in trouble regardless), even if someone hacked them and stole their data, they would not have your clear-text info. It's everyone's choice to make but I am personally OK with this security/…

> The data that 1Password stores on their end is encrypted with your personal passphrase. For now. What happens when they eat enough of the market and displace enough other tools that the government says "Ok, now MitM the encryption." All they would need to do is push an update and re-encrypt the first time you unlock it. Now, this has always been true, but it's not on your servers and source repos yet, right now it'…

> What happens when they eat enough of the market and displace enough other tools that the government says "Ok, now MitM the encryption."

I'll take that risk, given probability over possibility. But thank you for pointing out at least one scenario I hadn't thought of!

> How about internet outages? Service outages? Sure, local cache, but that cache expires.

Local cache doesn't expire, also the probability of me being offline for so long that this becomes a problem is close enough to zero for my comfort.

That said, I am guessing you might be responsible for some kind of critical (even just to you) infrastructure so we probably have different variables in our "is this for me" math..

Re: 1Password for SSH and Git (Beta)

#172

A huge problematic deficiency of 1Password is that it lacks literal multi-line text field types. The items in its database let you define custom fields for them, but there is no literal multi line text field. There's a "File" type, but you can't simply define fields with multi-line text values. However, every item has exactly one built-in "notes" field, but that's actually styled markdown text. And you only get one.…

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?

Re: 1Password for SSH and Git (Beta)

#174

A huge problematic deficiency of 1Password is that it lacks literal multi-line text field types. The items in its database let you define custom fields for them, but there is no literal multi line text field. There's a "File" type, but you can't simply define fields with multi-line text values. However, every item has exactly one built-in "notes" field, but that's actually styled markdown text. And you only get one.…

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.

Re: 1Password for SSH and Git (Beta)

#175
post #146
post #119

Earlier quoted context omitted.

What features/usability/performance was lost with the switch to the Electron app? If the answer is "nothing," then really the argument is purely about aesthetics. I didn't even know it was an Electron app until months after I had installed it.

From my own experience with Electron apps and 1Password beta a few months ago, putting resource usage aside (even if we should not): OS-native spell checking is missing. Lack of OS standard shortcuts. Everything is a single window. UX performance: lots of things has just a little bit longer.

We added spellcheck and text transformations options recently. Our team contributed a few patches to Electron to enable better macOS integration. For example: https://github.com/electron/electron/pull/32024

I believe the UX performance in 1Password 8 is better than any other app we built in the past: https://twitter.com/mitchchn/status/1491253916004147203?s=20

Would love to learn more about the standard shortcuts that are missing — good keyboard shortcuts is a huge priority to us!

-- Roustem 1Password Founder

Re: 1Password for SSH and Git (Beta)

#176
post #129

Earlier quoted context omitted.

Where is the ssh-agent reading your private key from? If from ~/.ssh/, you're just one "npm install" away from the key being exfiltrated by a compromised package. If the private key is on your Yubikey, you're already good. The 1password agent will provide a good hardwareless method of keeping your private keys off the local filesystem, and it'll sync between your devices too.

Why can the compromised package not also access wherever 1p is storing the keys or access the part of memory they're loaded into?

A process can not dump the memory of another process if those processes are executing under different users, or the process performing the dump is root.

On many OS's there are even more strict restrictions, where within a user a process can only dump the memory of processes that are its direct descendants.

Re: 1Password for SSH and Git (Beta)

#177

A huge problematic deficiency of 1Password is that it lacks literal multi-line text field types. The items in its database let you define custom fields for them, but there is no literal multi line text field. There's a "File" type, but you can't simply define fields with multi-line text values. However, every item has exactly one built-in "notes" field, but that's actually styled markdown text. And you only get one.…

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?

I believe on other fields you can click on them to copy their values. With the notes field you have to select the part of the notes yourself and copy that.

And probably can't filter for them as easily too.

Re: 1Password for SSH and Git (Beta)

#178

Earlier quoted context omitted.

I started using it back when because it just worked and I could keep my passwords synced between devices (windows, iOS and Mac) via Dropbox. Before that I used KeePass, but its Linux and Android clients were terrible. I still have 1password 4 on Windows PC and (apparently) version 7 on Mac; they still work together, but I'm afraid at some point they will decide to drop support for dropbox and force you to use their s…

Frankly I'd rather pay for 1Password sync that have Dropbox installed on my machines anymore with all the low-level hackery and product shenanigans they've pulled as the internal pressure to "innovate" and move up market has taken hold. I'm also worried about 1Password in the long-term with this recent VC investment which likely will create the same kind of pressures, but for now they still have the best product in t…

That's reasonable if you don't already pay for any cloud synchronized storage solution.

But many of us already pay for cloud file syncing across our devices and 1Password's previous solution worked just fine. Having it removed so they can charge their SaaS fees feels like a blatant worsening of the product.

Re: 1Password for SSH and Git (Beta)

#179

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.

Would a profile work here where you can define arbitrary fields?

Re: 1Password for SSH and Git (Beta)

#180

A huge problematic deficiency of 1Password is that it lacks literal multi-line text field types. The items in its database let you define custom fields for them, but there is no literal multi line text field. There's a "File" type, but you can't simply define fields with multi-line text values. However, every item has exactly one built-in "notes" field, but that's actually styled markdown text. And you only get one.…

Could you share a little bit about what you'd want to use this for? (I'm part of the 1Password design team)

If you're in here collecting feedback, I would second this request for the same reasons (keys, certs, other structured text I wish I could just copy/paste easily from the UI).

Been a happy paying customer since 1Password v4, but I agree this seems like an easy win.

Post reply on HN