Live data from Hacker News

1Password Secrets Automation

blog.1password.com

51–60 of 186 posts

Re: 1Password Secrets Automation

#51
post #38
post #30

Earlier quoted context omitted.

Bitwarden. One of the big reasons for doing so was because when I left my company, they took my Mac away from me, so I invested in a new laptop, for me there was no way I was going for Windows or Mac. So Linux it is. 1Password at the time had extremely poor support for Linux - no desktop client, their 1PasswordX was missing a lot of features and was super slow too. I switched to Bitwarden because it's open source, an…

Thanks for sharing. I’m sorry it took us so long to release a native Linux app. We have a great app for Linux now in beta and will move it to an official release shortly. https://blog.1password.com/1password-for-linux-beta-is-now-o... I hope you can give us another chance. —Dave 1Password Founder

Hi Dave. I understand that subscription is your future no matter what, but please don't cut off options for stand alone licenses and local syncing.

Re: 1Password Secrets Automation

#52
post #2

This looks interesting. We use 1Password, and I always thought it would be useful to programmatically pull values out and use in our cloud infrastructure. Currently we end up using the secret managers available in AWS or GCP, which seems pretty half baked. In GCP, for example, secrets are stored at a project level. It's not unusual to have certain secrets that are needed by more than one project, which means they get…

This is why we use Vault. Until recently, there was no good option to host it, so you had to manage it. It's good to have independent competition in this space.

They're not competing with Vault,they see this as an alternative for simpler use cases where Vault is overkill, or a complimentary product otherwise.

Re: 1Password Secrets Automation

#53
post #42

Earlier quoted context omitted.

Very much agree. My pet peeve at the moment is this[1], where they removed a feature I very much like (TouchID in the standalone browser extension) and still have yet to replace that functionality despite many promises that it is just around the corner. It was removed in August 2020. Definitely feel like they've lost sight of why people chose them in the first place, and stuff like this is certainly not helping assua…

It's a fundamental concern I've always had with subscriptions for non-entertainment services or trivially fungible goods. I've become a big believer in business incentives and feedback loops for sustainable commercial relationships. Individual leadership and culture can stand against them to some extent for a time, but individuals move on and it seems that near inevitably over enough years organizations tend to track…

[deleted]

Re: 1Password Secrets Automation

#55
post #26

Earlier quoted context omitted.

Because it works seamlessly on all of my devices and has done so for years. Never encountered any issues and syncing happens within seconds.

I've been quite happy with KeePassXC / KeePass2Android and syncing via Google Drive.

Not sure about Android but, for iOS users, it makes no sense trusting open source software. So, even if you choose strongbox or keepassium as they’re open source you’re still trusting some dude as you have no option to verify that the iOS build is the same as the build on github.

This is why I prefer to give my password to a company like Bitwarden and 1Password. At least, they have less incentive to be malicious than random dude on the store.

Re: 1Password Secrets Automation

#56
post #25
post #12

Earlier quoted context omitted.

What gimmicks, tricks, and dark patterns are you referring to? I've been using 1Password for my personal accounts for probably close to 10 years and have been happy with it. There are some things I feel are clunky, but I've never felt like I was being tricked or deceived by the company.

"It used to be free but now you have to pay" is really the only dark pattern they are guilty of.

I don't think it was ever free. It went from standalone licenses to SaaS, but it was always a paid product.

Re: 1Password Secrets Automation

#57
post #30

Earlier quoted context omitted.

What did you switch to if you stopped using 1Password?

Bitwarden. One of the big reasons for doing so was because when I left my company, they took my Mac away from me, so I invested in a new laptop, for me there was no way I was going for Windows or Mac. So Linux it is. 1Password at the time had extremely poor support for Linux - no desktop client, their 1PasswordX was missing a lot of features and was super slow too. I switched to Bitwarden because it's open source, an…

You can self-host this unofficial version https://github.com/dani-garcia/bitwarden_rs if you prefer. maybe not worth $10/month of your time amortized to set up, but it has been fire-and-forget for me.

My kids have started accumulating more passwords than they can memorize (and their memorized passwords were terrible), so I wanted a family password manager. I considered using "1password for familes" which I have access to for free from my day job, but if/when I leave the company then I'll have to go back to paying for it. So far I greatly prefer the experience of bitwarden over 1password. I use the web vault, the native mac app, and the linux command line app (through a janky homegrown dmenu/xclip shell script), and I have no complaints at all.

Re: 1Password Secrets Automation

#58
post #52

Earlier quoted context omitted.

This is why we use Vault. Until recently, there was no good option to host it, so you had to manage it. It's good to have independent competition in this space.

They're not competing with Vault,they see this as an alternative for simpler use cases where Vault is overkill, or a complimentary product otherwise.

Also it would be cool to unlock the vault via 1password.

Re: 1Password Secrets Automation

#60
Is anyone familiar with the secure introduction workflow using Hashicorp Vault? An orchestrator gets no more than a one-time use "cubbyhole" introduction token for a service that it is initializing. The initializing service uses the intro token to get actual credentials and secrets from the Vault. The orchestrator never touches any secrets: no secrets need to be passed as env variables anymore. With this setup, the person/service that seeds secrets into the Vault and the introduced system that uses the secrets are the only two that may ever touch them. Not sure how well this is actually documented but I gleamed enough from docs and a tech talk to figure the workflow out. It's pretty intuitive once you dig in.
Post reply on HN