was onboard until i found its a gui
There is already a command line tool available.
1Password for Linux development preview
271–280 of 352 posts
Re: 1Password for Linux development preview
#272Earlier quoted context omitted.
I tested Bitwarden for a while and found it was lacking features compared to 1Password. Until a few weeks back they didn't even have a "Trash", delete an item and it was gone forever. Exporting 1Password to Bitwarden was a complete mess, attachments in items were not imported at all/deleted (you don't get a warning of this.) Bitwarden is okay, but compared to 1Password they have a long way to go in my opinion.
It depends. 1Password lacks some things I'd really want (like configurable matching, having everything on a subdomain that's not on the public prefix list match is cumbersome). The Windows client is also extremely laggy and doesn't use Windows Hello half the time. 1Password X, which is almost a must-use on Windows, also has desyncing issues. So I guess if you don't mind the above and are on macOS, it's better.
Would agree with this. I went from Mac to Windows and the 1Password client on macOS is much, much better. It's slowly improving on Windows though.
Re: 1Password for Linux development preview
#273Earlier quoted context omitted.
They were also pretty dismissive of Linux for a long time, so it's kind of funny to hear it as one of their biggest requests. 1Password X narrowly prevented me from switching for a while, but I've come to see alternatives as generally better options. Yeah, they're not as flashy, but I think Bitwarden and Keepass XC do a great job. Keepass XC may even be doing a better job at security . At least in some dimensions. ht…
FWIW cache side channel attacks are primarily a threat on (shared) cloud platforms, but not as much [1] on personal devices. Considering that 1password runs in its own process and that most personal devices should have Meltdown mitigations in place, it would be prohibitively difficult to successfully launch a cache side channel attack to extract the password from outside of your device, especially at scale. Attackers…
Oops, I somehow managed to respond to the wrong comment. I meant to respond to https://news.ycombinator.com/item?id=24057416
Re: 1Password for Linux development preview
#274Earlier quoted context omitted.
That’s where Agilebits has me; the UI on Mac and iOS is so much better than the alternatives. I do keep looking, Keepass XC looks really good since the last time I checked around.
KeepassXC is quite good if you mainly use it on your computer. I've been using Keepass(XC) for about 10 years, it's secure and reliable. But I'm looking to switch to 1password or Bitwarden as I'm increasingly using portable devices (phone, tablet…).
Keepass2Android works pretty well for me. You can sync your password database via google drive or other file sharing services.
Re: 1Password for Linux development preview
#275Use pass: https://www.passwordstore.org
Re: 1Password for Linux development preview
#276Earlier quoted context omitted.
> Why shouldn't it be Electron? Because every Electron app is inconsistent with the rest of the desktop. I use a dark theme system-wide but Electron won't care [edit: 1Password has custom integration for GTK theme]. Honestly, this isn't something the developer of the app have to put years of research in (Slack for example). The toolkit is supposed to do the integration (GTK, Qt, [Cocoa?]) and clearly Electron doesn't…
There are also advantages for the user. For example, new features arrive for all platforms at the same time; there is no prioritization of platforms or such. Same for bugs - apart from issues stemming from Electron itself, they're likely to appear on all platforms and therefore likelier to get fixed. In essence, the old "only X% of our users use platform Y, it's not worth it to make this feature/fix this bug for them…
> For example, new features arrive for all platforms at the same time
That (and everything else you said) is true for any cross-platform framework, not just Electron.
Re: 1Password for Linux development preview
#277Earlier quoted context omitted.
> Why shouldn't it be Electron? Because every Electron app is inconsistent with the rest of the desktop. I use a dark theme system-wide but Electron won't care [edit: 1Password has custom integration for GTK theme]. Honestly, this isn't something the developer of the app have to put years of research in (Slack for example). The toolkit is supposed to do the integration (GTK, Qt, [Cocoa?]) and clearly Electron doesn't…
There are also advantages for the user. For example, new features arrive for all platforms at the same time; there is no prioritization of platforms or such. Same for bugs - apart from issues stemming from Electron itself, they're likely to appear on all platforms and therefore likelier to get fixed. In essence, the old "only X% of our users use platform Y, it's not worth it to make this feature/fix this bug for them…
None of these are advantages over other, better cross-platform toolkits.
Re: 1Password for Linux development preview
#278I was a 1Password user from when it was fully self-hosted until they started pulling bait and switch tactics to move people to subscriptions and online vaults[1]. I also had Windows licences, and Windows was certainly a 2nd class citizen while I used 1Password. And of course, it doesn't look like the 1Password Linux client is open source. The back-end certainly isn't. I switched to Keepass[2] initially, synchronised…
This comment is like a canonical example of why a company would choose not to develop for Linux. 1Password puts real resources and risk into supporting a platform that may not pay off, but it’s Not Good Enough for much of the community because:
-The client is not open source
-the backend is not open source
-it’s not “a first class citizen” right away (the Windows port is by all accounts improving)
I’m not trying to put down your comment but to point out that when you have a fragmented platform that is difficult to develop for plus a community that is often hostile to closed source or less than perfect feature parity you are going to be relatively deprived of commercial offerings. This is why we see less Linux support broadly. Not that you personally should change your opinions.
Re: 1Password for Linux development preview
#279I was a 1Password user from when it was fully self-hosted until they started pulling bait and switch tactics to move people to subscriptions and online vaults[1]. I also had Windows licences, and Windows was certainly a 2nd class citizen while I used 1Password. And of course, it doesn't look like the 1Password Linux client is open source. The back-end certainly isn't. I switched to Keepass[2] initially, synchronised…
You should consider LastPass. They've had considerably fewer security breaches than KeePass and is accessible either using a local app or from any modern browser regardless of OS. It even has a smart phone app, although the phone app requires a subscription.
Re: 1Password for Linux development preview
#280Earlier quoted context omitted.
Same issue for me, having online vaults was the killer for me. Also the subscription made me really think if the service was worth it after all, specially after buying the apps they are asking me more money. I moved to Keepass (and opensource apps) and im fairly happy with it. I dont think i will go back to 1Password.
A program worth using is worth buying
Woah! I think a lot of people in the free / open source community might have a problem with such a statement.
However, I do pay for a password manager because I recognise their importance and view them in a slightly different, almost unique way. I'm not averse to paying for software and services online, too.