>Set up the 1Password 8 desktop app That will be the Electron version. No thanks.
I wish 1Password used Tauri instead of Electron.
1Password for SSH and Git (Beta)
361–370 of 406 posts
Re: 1Password for SSH and Git (Beta)
#362Re: 1Password for SSH and Git (Beta)
#363Earlier quoted context omitted.
> you're just one "npm install" away from the key being exfiltrated It's not as easy as that if your private key is protected with a passphrase, which IMO ought to be the default option. I am amused by the rationalization going on here, though... taking extra steps to secure your SSH private key because you might "npm install" something bad. There's nothing wrong with enhancing the security of your private keys throu…
> just don't run "npm install" (or similar untrusted code) in an environment that you don't want to get pwned. So it is unreasonable to want to develop a JS app on the same machine I use for SSH? Docker works I guess, but adds a lot of mental (and in the case of Docker for Mac, performance) overhead.
Just because I happened to be dealing with this today (on Windows with WSL2 but same rules apply) I'll make a comment.
The issue I ran into was due to Docker for Desktop binding the local filesystem into the devcontainer running in a WSL2 VM.
The solution to this is to instead use a named volume in your docker-compose.yml and in your Dockerfile copy the files from your working directory into your devcontainer.
This provided an incredible improvement in the performance of using devcontainers in vscode. The one big drawback to this approach that I've run into is needing to make sure I commit and push my code to a git repo when I'm done working as there's not a copy stored on my local machine.
Re: 1Password for SSH and Git (Beta)
#364Question: if I have this on Windows (1Password for Windows), is it possible to do this via WSL?
Re: 1Password for SSH and Git (Beta)
#365Earlier quoted context omitted.
> I don't think SSH keys are things you should share across machines in a password manager. While I agree with the first half of your statement (don't share SSH keys), I cannot agree with the second (don't put SSH keys in a password manager). For my home use of 1Password, I absolutely want to keep backups of my SSH keys in 1Password. Because, in general, there's exactly 1 SSH key which can get into my cloud instances…
I'll concede that it's not nearly as crazy to share keys across devices for home use or low-risk things. I must admit I was speaking mostly from an enterprise perspective.
I could see this eventually being built into 1Password's Secrets Automation product which can sync to each user's 1Password client. It allows the use of Vault for a backend so now that SSH Keys in 1Password are a thing it wouldn't be out of the realm of possibility to have Vault generate short-lived per-user SSH certificates that are automatically rotated into the user's 1Password vault.
Re: 1Password for SSH and Git (Beta)
#366Earlier 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…
Thank you, I really appreciate that, and it will save me and others a lot of time and effort! Spectacular turn-around. I'm looking forward to upgrading to 1Password 8. Please also put some love into the 1Password CLI utility "op" too, so it's safe and useful for unattended scripts.
Re: 1Password for SSH and Git (Beta)
#367>Set up the 1Password 8 desktop app That will be the Electron version. No thanks.
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…
It doesn't integrate with OS. Like events happen differently, stuff like this. Especially for macOS.
But again, if one uses some crap from IntelliJ and Slack, this fits right in.
Re: 1Password for SSH and Git (Beta)
#368Re: 1Password for SSH and Git (Beta)
#369Ahh, this is such a nice improvement over literally anything i've used for agent key management on Windows or Linux, and easily competes with using the Keychain integration available on OSX; It sucks that I can't really use the functionality due to the v8 requirement, and am once again in the position of paying for something where I don't get to actually use new and useful features due to really aggressive ( if not outright anti-user ) product direction.
For some context on my bitterness: v6 stopped working with chrome based browsers a few years ago due to an issue with browser signatures, and the official guidance was to ( pay to ) upgrade to v7 rather than fixing the app, and so the software I had paid for was no longer usable in the way that it was when I purchased a license for it, effectively being downgraded through no fault of the end user ; Similarly, the Windows variant of 1pw has... kind of always just been a bad experience compared to the mac version, and while the controversial Electron-based unification for v8 promised to bring the experience in line with the Mac app ( not requiring purchase of another license type this time because I'd since bitten the bullet and paid for a subscription so I could actually use v7 ), it also required migration to the hosted vault system, as support for local vaults was completely dropped in the same version.
I would feel a lot more comfortable using this otherwise legitimately fantastic functionality if it didn't also require me to migrate from a local vault to the hosted version. I already didn't want my passwords hosted online; I definitely don't want my ssh agent and its private keys to be bound to said hosted service, and nothing has yet come out of 1Password's survey for self hosting the vault server in order to maintain a vault that works with 1PW 8 locally.
It's an unfortunate hill to die on, I realize; I just want to maintain control of my own stuff, using a tool that is actually nice to use ( 1Password is and has always been miles ahead of everything else in terms of the day to day user experience, otherwise I'd be able to justify looking at alternatives )
Re: 1Password for SSH and Git (Beta)
#370Earlier quoted context omitted.
I wish 1Password used Tauri instead of Electron.
On twitter they said they are closely looking at tauri‘s progress. Tauri is not even 1.0 - i guess they will later on switch to it.
Oh nice! Tauri is super close to 1.0 so it'll be interesting to read the resulting blog post about the switch.