I actually don't have a problem with this, but I do have a problem with press releases that are sprayed with emojis. It's incredibly unprofessional and gives a real amateur flavor to the whole thing, which for security software is really offputting.
It's too much fun for me too. Blushing faces and clapping hands look like kindergarden drawings, not consumer-oriented at all. I guess some people are more serious than others. :-*
To be pedantic, it looks like it's actually an official reply on a community forum, not a press release. Also, thinking that the use of emoji reflects the software quality is a mistake in our current culture.
I love normalizing emoji use. Its actually harmonizing the depictions because they can be wildly different across platforms, and until that occurs its part of an ongoing gag where its funny to imagine how messed up they render on someone's phone.
Like, imagine its only Gen X that complains about this, and they are the equally out of touch blackberry user whose device renders all the emojis in some messed up but hilarious way, then its a great way to make fun of them without saying anything and just keep bombarding them with an incommunicable internet, while the rest of us dont mind and some of us are also in on the joke.
Another problem with emojis is that it is not clear what it means to different people. Recently read in the WSJ that young people find smiley faces passive-aggressive or patronizing, not friendly or positive.
Admittedly, there is a similar problem with words, but there are at least dictionaries for them. :>
I haven't had a single bad experience with Bitwarden. I even pay for it now and still run it locally just to support them. Highly recommended if you don't want to be forced into 1Password's service.
I use Bitwarden for shared passwords with my family (using an Organisation).
For my personal passwords, I prefer keeping a local KeePass vault (I access over a local network drive, VPN in elsewhere).
I totally agree that primitives are some of the least important parts of choosing password managers, but what I like about KeePass is that you can use Argon2 as the password derivation function and specify your hardness factors. Because my laptop and desktop have a strong-enough CPU and I don't mind waiting 20-or-so seconds before the first unlock, I can set quite high values for this.
I love that KeePass works with pretty much whatever sync service you prefer. Personally, I use it with Google Drive and it even works with Android/iOS clients. However, would definitely recommend KeePassXC for desktop.
Dev here.. Thanks for the feedback. Please note that you're comparing a big product to a small open source software :) Of course would like to know how to make the extension better, so if you want to help us, make an issue to GitHub, thanks. Safari integration is coming eventually.
I'm in the same boat. Password sharing with my wife was a big plus for Bitwarden, and I got my kids in on it as well. I paid for the family plan and can share select items with my kids.
It's honestly fantastic to see how they have adapted to password managers.
Bitwarden's UX is so frustrating. The Firefox extension has no memory to it.
For example, if you're logging into your credit card provider from Mint.com, you have to search your card, copy the username. when you paste the result on Mint, you lose the window, and you have to re-search for your card to get the password. Very frustrating.
This is probably an edge case where the fields in the browser cannot be identified by their ids/classname. In this kinds of a scenario, you can set extra fields (and their corresponding values) in Bitwarden after inspecting the field elements in Dev tools.
No he means that Bitwarden's extension does not remember state. When you go back and forth between the form and opening the extension window, you always start at the default page. It does not remember you had an item open before. This happens with your credit card for instance which is typically not linked to a particular url.
This is one of my annoyances as well. Copy the credit card number... go to paste it. Come back and you have to find the credit card again and then copy the next bit... then go paste and when you come back you're once again presented with the full list so you have to go find the credit card again.
I've found just opening the main app to be a better solution in these cases, but it sure is annoying.
I moved to Bitwarden from Lastpass also, and I'm definitely happy for the most part.
The chrome extension leaves a tiny bit to be desired, but definitely still usable:
* Not as good about determining correct sign-in URL and lots of times will send me through the auth redirect from registration
* Launching sites without mouse isn't possible (shortcut exists to open extension but can't select site to launch it using arrow keys, for instance)
* Button locations aren't consistent between search view and opening it on a site you have a password on
Definitely still the best for me though. It's frustrating, though, that I don't feel like the paid plans really give me anything useful, so I'd be paying basically just to support the product (which I'm happy to do!). It's a weird spot for sure, I feel like table-stakes for a free password product is infinite devices + usable browser extension + phone apps + password generation. But figuring out what to add on top of that is always either directed at businesses or families, or things I don't care about like 2FA or an authenticator. I want to support you, damnit!
I don’t have issues with the URL, there’s lots of options for how the matching works. I found it to be superior to 1Password (tho I haven’t used that in a few years so I donno if they improved it)
The paid plan support OTP token and allow big file so you can embed stuff like google cloud json token file. The free has 1000character limit(per field) if I remember correctly.
Bitwarden run so much faster than 1password despite being a browser extension.
The CLI is great too. I pretty much use it like a cheap version of Vault to feed secret into K8S.
One other thing I do not like about BW (but not enough to switch) is that when you click out of the bitwarden window, it disappears and loses your place so you have to navigate to the secret again. Kind of annoying if you are on a website that resists autofill or want to copy something from custom fields.
Tip: Pop-out the extension as a window. Even if you close it, your browser’s Ctrl+Shift+N is going to restore that window with the same secret/state, even if the vault locks.
I use chrome shortcuts.
In extensions, look at the option to assign keyboard shortcuts. I have set it Alt+D combination. The 2FA codes are copied in the background, and when the screen comes, ctrl+v does the magic. Simple.
Multi-device access, browser integration, mobile platform integration, and sharing with spouse or team members. I know there are solutions to some of those based on some variant of KeePass, but using something like Bitwarden is very easy. Bitwarden is really nice in that you can host the server yourself (or use bitwarden-rs), so you're not having to mess around with WebDAV or some other storage sharing mechanism.
Though one more point that’s more than just "ease of use" is probably shared access. AFAIK Keepass has issues there while bitwarden (IIRC) supports it completely.
What caused me to not consider Bitwarden was the way it handled iframes. It could send the parent sites credentials to an iframe even if the iframe was on a different domain. This is a big no-no in my book.
This was a discovery in a security review they did and choose not to change.
This was some time ago so things may have changed. But, that red flag kept me away.
1Password fills iframes based on their domain rather than the parents. If you have an entry in 1Password it will use the value for the domain of the iframe.
yeah the interface is crap compared to 1password but i do find a bit of comfort that even though it's not the best interface it's fully opensource unlike 1password.
Bitwarden and KeePass here, bitwarden is very good. I do not use browser plug-ins so both are kind of the same but bitwarden just wins on the little things.
personally, i use bitwarden for passwords only, and i store backups of OTP seeds in a seperate keepass file.
I have my OTP codes on yubikey for daily use. (works great, and breaking a yubikey is a lot harder then destroying your phone and losing all your OTP).
I'm also happy with Bitwarden--I switched from 1Password a while ago when 1Password started the push toward subscription (which involved dropping support for features that I used, and dark UI patterns around pushing the subscription version as well as getting and using the non-subscription version).
I had bought several versions and both the Mac and Windows editions of 1Password over time, none of which were what I would consider inexpensive for a password manager. I consider their treatment of me as a customer to have been terrible.
I wouldn't be so pissed off about it if they had just dropped the product and started a new one, but slowly turning something paid for, used regularly, and liked into something different that I didn't want at all tells me that they are absolutely not worth doing business with again. They're not trustworthy.
+1 on Bitwarden. UX is perhaps not perfect. I've had some IOS sync issues but that seems to have gotten much better. Use it in Firefox every day and have no complaints.
I convinced my wife to pick it up and we now share a bunch of stuff and she loves it. And she's low tolerance for UX issues.
Is there a good command line client for bitwarden. I recently moved from keepass (using kpcli) to bitwarden (so I can share passwords with my spouse), but am so far, very unhappy with the command line tools.
The official command line tool is way too clumsy. I've tried rbw and rbw-fzf which are ok. rbw doesn't let me view all properties of an entry (attachments, notes), and rbw-fzf has issues if things have spaces in them and is limited to only passwords, not other info.
I'm a happy and paid user of bitwarden too.
On top of being open source, what made me choose it is that the desktop client downloads my vault locally in an open and secured format. So I can make an automated backup of this file wherever I want.
Mostly the same; but the only thing I miss in Bitwarden compared to Lastpass is, if the vault is logged out, it doesn't prompt me to log in (to the vault) when it finds a login prompt for a site I have saved in the vault.
Exactly—there are two major changes: the Electron change (which I'm 'meh' on, but could accept on its own), plus entirely dropping support for local vaults in version 8.
I've been using KeePass with Syncthing for some time. No problem if you only need to update the database from a single location and access as read-only from the rest, but there are also solutions for shared updating.
Unless they remove support for local vaults from their mobile apps, you can continue using the classic self-synced method. I sync my 1Password vault across Android and Windows using SyncThing, using 1Password 7 and the legacy browser extension in Firefox. I don't get the inline 1Password prompt in password inputs, but that's the only disadvantage (Ctrl+Alt+\ brings up the password selector anywhere in the OS, not just the browser).
In fact, if you're okay with only editing/creating password entries on your phone, you don't even need to pay for the desktop app, because you can use it in read-only mode. The Android app has no limitation to editing local vaults, and it's pretty rare for me to actually have to set up new accounts these days, so I'm fine doing it on my phone. I considered paying for 1Password X (their online offering), but it's simply not worth $45 per year for that minor convenience. I can't complain at all, because I use 1Password completely for free.
They have, as far as I can tell. Last month I tried to set up a new 1PW installation and exhaustively searched through the app menus - no sign of standalone vault support anywhere.
It's possible that it was hidden because I had previously signed in to my work's 1PW account, maybe, or that it's hidden too well for me to find. I don't know, and would be happy to learn either way.
iirc (it has been a while since I used it), this fits with what I saw. You could do it if you set it up as a local vault at the very beginning, and add a web account on top of it, but if you started with a web account it was not an option at all.
I fully expect that to happen. And it will catch many people unawares when their iOS app automatically updates and prompts them to "upgrade" to the sync service.
Yup, I'm out of here as well. Been using them since 2014, been frustrated since they heavily push you toward using their cloud, and now this shit happens.
1Password used to be native on the Mac, and now it's an Electron app. I'm not going to be using 1Password for this reason, and I encourage you to do the same.
Subscription business models and non-native apps are hallmarks of rot by VCs. Dump them!
Last I messed with it, Electron is structured such that the UI thread is decoupled from where you're supposed to run your "logic" (for performances reasons, I assume—similar patterns are really common in GUI systems, in general) and they already have to communicate at arm's length, so 1) it's not that big a stretch to wrap some native library on the "logic" side, and 2) if you're calling back-and-forth between logic and UI a lot, rather than sitting in your logic code for long periods of time, it'd expect it to do very little for performance.
Generally a massive bundle size, and/or inspecting the bundled frameworks themselves (right click on app -> show package -> browse folders for frameworks).
If you can’t tell the difference it doesn’t matter and I wouldn’t worry about it.
Electron apps typically don’t work for me because they don’t integrate with the rest of the system cleanly, and so once you stray off the designers’ happy path it becomes clumsy to use the app. This isn’t an esthetic or ideological argument; simply for my usage an electron app can rarely be as convenient as a native app on the Mac. Things like input integration, system service integration, selection, and responsiveness are much harder to do when you are fighting the electron abstraction, so no wonder devs leave those things out.
Just because a user can't tell the difference doesn't mean we shouldn't call out the fact that it is. Electron apps use way too many system resources. For lower powered devices, this becomes an issue.
Poke around the application bundle or its supporting files directories. On macOS, the Electron.framework folder will typically be somewhere inside of the .app bundle.
This is ridiculous. Electron works great, and if this leads to more frequent updates and a more consistent experience across platforms, that's a win for users. 1Password's Windows client, for example, has always felt behind the Mac edition, and if this brings parity and a higher feature and update velocity, that's a win. I have at least three Electron apps open right now and they are all great experiences that the vast majority of users of those products love.
This has nothing to do with VC and everything with trying to build a better product for users that is easier to work on for developers.
I haven't commented enough to report you so I will just comment. This response goes against nearly every guideline for the site. Please don't attack fellow users just because you disagree with their opinion of technology stack. I've used a wide range of Electron applications and the quality varies just like any other tech.
Electron is a pile of shit and _every_ Electron app I am forced to use should be a source of continuous shame for any dev who actually worked on it. This has nothing to do with improving features or service and is completely about increasing revenue and improving the sort of numbers investors like to see -- driven entirely by the fact that AgileBits has recently closed a B round and needs to show more revenue to justify that $2B valuation.
As a long-time 1password shill I have hit my limit and will slowly start migrating to BitWarden and iCloud Keychain.
Bitwarden and iCloud Keychain user here. I'm looking forward to the 2FA improvements in this year's macOS. It'll mean I could, in theory, mostly ditch Bitwarden as that's the big use case there for me.
You can create a shortcut in the iOS shortcuts app to open the Passwords area of Settings via an icon on your Home Screen. Just open the following URL in the shortcut:
prefs:root=PASSWORDS
Best tip I have for you around iCloud Keychain right there.
But even then I'd assume it was more due to the workflow than the original complaint, which was essentially "Electron = bad, you should be ashamed for using it".
No, I have plugins for roughly the same feature set/workflow in both editors. Open and edit a huge file in both editors and Sublime is more responsive.
that is a very low bar. VS code is still slow and eats up a ton of resources. not to mention I don't trust anything from microsoft. OP said electron = bad and you should be ashamed of using it because its helping propagate it's usage when its a cancer.
Electron is a tool. It can be used well. It can be used poorly. Any tool shares the same issues. I can write a shit native app and I can write a shit Electron app.
All Electron does is lower the barrier of entry to making an app and making it work cross-platform.
The problem is even the best examples of Electron apps aren't great and use far more resources than a native counterpart would.
VS Code is an example of Electron being "used well". I still find myself using other apps because they're more responsive. That tells me that Electron is inherently making the app experience worse, despite being used well
I understand the 'why' of electron, I am just not happy with the results at all.
Though maybe the world is better if that barrier of entry isn't lowered, I'm not sure what's better- a shitty app available everywhere or a good app available only on a couple of platforms...
I would argue that in general, having a lower barrier of entry to software engineering is a good thing, especially for attracting people that might not have otherwise considered it.
Someone wants to build a 5 minute app for themselves and Electron happens to be the easiest way to do it? Go for it, there's nothing stopping them. If that app happens to be useful enough for others to use it, even better, that person just solved what could have potentially been a big deal for that user.
If the people using the app are content with the features/quality and the resources it uses, why does it matter so much, especially to a third party like armchair engineers on HN, if it was built natively, on Electron, or CrappierFrameworkThatWillEventuallyReplaceElectron?
If the app isn't usable by you (and this is a general you, not specifically directed at you), then the answer is simple: don't use it. Nobody is forcing you to use Electron or any app built with it if you don't want to.
If as a user your needs are not met, whether that's due to sluggishness from Electron, incompatibility from having a native-only solution, whathaveyou, then all you really have to do is wait. A competitor will come and take its place eventually; that's what the market is there for.
So far, it seems like VS Code is more than meeting its users' needs, but like I said above, other alternatives exist and will continue to exist, and they're all great if VS Code doesn't work for your particular use.
> If the app isn't usable by you (and this is a general you, not specifically directed at you), then the answer is simple: don't use it. Nobody is forcing you to use Electron or any app built with it if you don't want to.
> If as a user your needs are not met, whether that's due to sluggishness from Electron, incompatibility from having a native-only solution, whathaveyou, then all you really have to do is wait. A competitor will come and take its place eventually; that's what the market is there for.
not the first time we've heard this argument used in different industries. I'm old enough to remember this argument about DLC's, DRMs and games being released before they are finished and get charged DLC packs to finish it. This argument falls apart when everyone starts doing it due to economic factors and complacent users/customers who blindly use what everyone else is using.
If truly everyone is doing it and you don't have any other option (which is just preposterous, there's an ever increasing number of choices out there) then maybe you're just not the target audience anymore.
Businesses aren't stupid, if a decision were to actively lose them more customers than it'd gain, they wouldn't do it. If every single business and OSS alternative suddenly switched to Electron and you had no other choice, then maybe it's you that is wrong about the value of Electron.
But, of course, that's a ridiculous hypothetical not really grounded in reality. In the real world, plenty of alternatives exist for practically every Electron app out there so if you don't want to use it, you don't have to.
And for every one of you, there's hundreds of people that think their Electron apps are fine and appreciate that they can use the exact same interface regardless of which computer they're using.
> then maybe you're just not the target audience anymore.
i see you're moving the goal post
once you have a monopoly you can do whatever you want, thus why everyone keeps talking about EEE. look at what apple is doing now with photoscanning. What they are doing is inherently bad but they are able ignore everyone and go ahead with it because their "target audience" doesn't care about this kinda stuff. Doesn't mean the rest of us shouldn't actively fight against it. your argument basically boils down to let the market and customers decide for itself. Over here there are some of us trying to tell people to not support electron because of the potential consequences, and the downward trend of the web as we see it.
> In the real world, plenty of alternatives exist for practically every Electron app out there so if you don't want to use it, you don't have to.
There's choice with password managers. But look at music. You have Deezer and Spotify. The only two free services that I'm aware of that only have Electron apps on desktop. (YT Music doesn't have an app on desktop). Spotify has exclusive content. You don't have choice when apps are the same as services. Hate the Hulu interface? You can't watch The Handmaid's Tale on Netflix. It's that kind of thing.
I'm with you on this one. During the end of the 90s there was a similar phenomenon for the exact same reasons, which was Java desktop apps, with their write once run anywhere motto. With the added insult that they had this awful non-standard UI most of the time. They eventually died down except for the corporate app world and things like JetBrains IDEs.
But now with Electron, which I don't like for the same reasons, as a friend once told me, allowed me to have some of my favorite apps running in Windows, Linux and Mac almost flawlessly with a good interface that finally the promise of Java was fully realized.
So while I would like people to follow more the Sublime Text approach, there is value in these Javascript based apps that lower the barrier of entry, provide widespread availability and are definitely easier to debug. Also sometimes I don't get to decide, since my org for instance makes it extremely convenient to stick with JetBrains stuff.
But hey, I'm the type of person that considered a Gentoo machine running Fluxbox far more useful than the very polished MacOS.
I'm a feature developer for 1Password, and I want to clarify a few things. I've posted this already in another thread, but there seems to be some misinformation being spread that our technical decisions are being driven by VC funding.
Our decision to built the macOS app in Electron was absolutely not driven by VC money. For the past few years, we've been working on consolidating 1Password's business logic into a single Rust-powered core that could be shared across all our apps. This has many advantages: feature consistency across platforms, faster development cycles, and better security. When building the front-end for the desktop platforms that would take advantage of this new core, Electron suited us perfectly, since we could write our UI code once and make it consistent across Linux, Windows, and Mac. We actually did build a native Mac app initially alongside the cross-platform Electron app, but we eventually decided that having two separate versions of the macOS app (one in Electron, one in SwiftUI) would cause a lot of needless development churn and hassle for both customers and our support team.
I can understand your frustration about Electron, but I hope you find my explanation reasonable. Please stop spreading misinformation.
That’s reasonable logic but for me with a company subscription and previously having been an individual purchaser with my backup in iCloud rather than on 1 pass servers, it doesn’t really tilt the balance - I also hate electron with a passion and will be looking to stay on 7 for as long as possible with a high likelihood of shifting to a different provider due to the forced shift to cloud storage after this.
With respect, I disagree with your conclusion about a SwiftUI version causing hassle for customers. Every time I use an Electron app, I get the distinct feeling that its developers are prioritizing their experience over my own. We the users subsidize faster development cycles with wasted CPU and memory, laggy interfaces, and strange, non-native UX.
> We the users subsidize faster development cycles with wasted CPU and memory, laggy interfaces, and strange, non-native UX.
I can absolutely attest to that with a relatively underpowered computer (4 gb of RAM). I can barely use 2 electron apps after which my computer grinds to a crawl (I’m running VSCode and Slack mostly). I have stopped using the discord desktop app and exclusively use the website now.
Thank you for letting me know your concerns. Just to clarify: when I said that a SwiftUI version would cause hassle for customers, I was referring to how releasing two separate versions of our app - one in Electron, and one in SwiftUI - would be confusing for non-technical users. I should have phrased that better, my bad.
Sorry for the confusion. With 1Password 8, we re-built the entire app from the ground up. We didn't have a working SwiftUI solution that we could just pick up and use - we had to re-architect the entire frontend from the ground up. So when we made the decision to stop working on the SwiftUI app, it was far from being complete.
That Electron is an unpleasant experience and is a resource pig that makes Java look svelte? No, that is not misinformation.
That AgileBits has been doing everything it can to force people to the subscription model and that this push to subscriptions very coincidentally lines up with two rounds of VC investment for over $300M over the past couple of years? No, that is not misinformation.
It may have been easier for the dev team to use Electron as their cross-platform toolkit, it is not easier for the users to put up with the attendant bloat and reduced performance.
The ones who should stop spreading misinformation regarding the forced subscription all seem to be working for AgileBits.
There's a reason people prefer one over the others. You can't have one front-end for all these different platforms. Well, you can, but then it's a compromise for at least 2 out of these 3 platforms.
So you had the beautifully engineered experience of macOS to draw native user experiences from, and then you just threw it out because you wanted parity?
That doesn't make the macOS experience better, it makes it worse.
I have to treat each Electron program as having ~5-20x the system resource footprint of an equivalent native program—because they do. So they're going to get cut, or I'm going to pick a competitor to begin with, more often than a native app. That goes especially for anything I open often, or for anything it'd be convenient or necessary to leave running most or all of the time. Rarely-used programs, I mostly don't care, and Electron's fine.
It may be a win for some users. I can’t see how switching my perfectly fine, frequently updated native app for a memory hogging web browser wrapper is a win for me. I’m actively looking for alternatives now.
I think it's reasonable to complain about the loss of the native app when one of the key selling points (imo) is the pleasant UI. I don't really understand the almost-automatic hatred of subscriptions.
if an app has ongoing development that you benefit from, it seems entirely fair to pay a subscription. the fair alternative is a one time payment for a lifetime license with few patches priced in. I would probably prefer the latter for something like a word processor, but would you really want to use the same version of a security-critical program like a password manager for the rest of your life? if not, how do you expect them to fund development/maintenance indefinitely?
The hatred comes from their proliferation. With what seems like damn near everything moving to a subscription model, it's more money out of my pocket for usually what amounts to rent-seeking (i.e, demanding more money, more often, whilst providing no additional value).
That last bit I don't believe applies to 1Password, because there are certain things you can't do without some kind of centralization, and the article makes that case.
...but look at something like Adobe CC, what exactly does moving from a purchase to a subscription benefit me? And let's not forget about the more subtle effects, like losing the right of first sale, silent T&C changes, mandatory updates, etc - things that are only to the vendor's benefit.
> what exactly does moving from a purchase to a subscription benefit me?
Trust that the company which provides something you need is far more likely to continue to be around. Suppose you tell your employer that you're taking a 1-week vacation. How does it benefit them for you to do that?
> what exactly does moving from a purchase to a subscription benefit me?
It keeps the vendor financially healthy, stable and willing to keep developing the stuff you use.
Would you want to dedicate your work into a product for meagre & sporadic standalone payments pressuring you to endlessly churn out marketable feature upgrades with little time for maintenance work just to barely make ends meet? No? Then why on earth do you expect other software vendors to do that?
Even Bitwarden pushes subscriptions.
I'd love to see how many developers who complain on HN about subscriptions actually make a living primarily from selling standalone software to consumers.
This is a lame justification; software companies were quite capable of sales rather than subscriptions and have been throughout most of their existence.
This model is simply more lucrative and strips customers of a number of their rights which are inconvenient for corporations.
> if an app has ongoing development that you benefit from, it seems entirely fair to pay a subscription.
Agreed. Though, this latest development – the move to Electron – is a negative for me, so it leaves a part of me wondering what kind of development I have been paying for. I imagine I am not alone with such a sense of disappointment.
For this use case, a subscription makes a lot of sense. I have no complaints, though I currently do not subscribe to this application. I would, if I felt the need.
My take on the hatred boils down to these things:
Utility type applications built as a service offer an inexpensive purchase of some kind, or are AD driven, etc... Then, features are changed, roadblocks added, user experience degraded to create problems that subscriptions pay to remedy, often poorly.
Noisy subscriptions. It's not enough to send a few bucks a month. ADS, various pitches, in app sales happening, all contribute to what might otherwise be a simple, worthy experience and solution.
It can be hard to cancel. -->if this happens to someone even once, the hate can be visceral afterword. Everyone else, no matter how well they do business is impacted to a degree.
Subscription apps / services going away on short notice. What were people paying for?
> I don't really understand the almost-automatic hatred of subscriptions. if an app has ongoing development that you benefit from, it seems entirely fair to pay a subscription.
I don't _want_ the ongoing development. Photoshop from 5 years ago is perfectly fine for me. Same with Lightroom, etc. I mean, I've only paid Apple _once_ for Logic Pro and have been getting upgrade after upgrade for no cost -- a nice bonus, but I'd be perfectly happy if logic's code had been set in stone at the moment of purchase, too.
The consumer-friendly option is to let the consumer decide if they want upgrades. Or for a security-focused app like 1password I'd have believed something like "we don't want to be responsible for security problems if you decide not to upgrade, thus you must buy a yearly license" but that wasn't the message at all.
They did. They offered standalone licenses and subscriptions for an entire version's lifecycle and 97% (or something crazy high like that) of the people who downloaded went for the subscription. I've been a standalone user since v3 and finally upgraded after realizing that buying a license for Windows, Mac, and Linux would cost me more over 3 years than just paying the subscription.
Let me tell you, as someone who used 1password since 3.x .. when I went to buy 7.x standalone it took me over an hour to find the page that let me buy standalone over three sessions.
Why did 97% buy the subscription? Because they hid the other version in a locked filing cabinet in a basement with a broken staircase.
No, they didn't. Subscriptions happened when version 6 came out and that's the time period they're referring to when they're talking about those stats. There was literally 2 giant boxes of equal size asking if you wanted to use an account or a standalone vault. 97% of people chose the subscription.
If every single utility and app start charging $3 or $5 per month then it becomes a problem. Software as a service is a good concept for something that is truly changing all the time, but I find it absurd that a Photoshop subscription or a huge IDE cost as much as these utilities thst used to be shareware in the past.
The old business model works but you have to keep innovating and diversify your product line. Microsoft was the best example with things like Encarta, Age of Empires and other tools like Project.
This new trend of doing these apps once, with far easier programming languages in a connected environment with plenty of docs, crash report data and things like stack overflow really makes it look that we are talking about cheap people trying to make a quick profit not unlike those free to play games.
This is kind of ridiculous. Photoshop doesn't benefit from being a subscription the way that 1Password does so it's only a problem if you decide to actually buy those for what they're asking for. Something like 1Password does truly change all the time to keep up with security practices, browser updates, and site updates so it fits with what you're describing.
I recently cancelled Evernote after 12 years of paying for it due to their new Electron client.
I've been using 1Password since 2008 and I'll be doing the same thing. I have tolerated the UI regressions and even subscription with version 7, but Electron is just unacceptable for what was once an amazing Mac app that put Apple's apps to shame.
I hate Electron as much as the next guy, but man have I been enjoying Obsidian. I mention this only because it has changed the way I write notes and manage them and I've been through the path of Evernote > Apple Notes > Bear > Obsidian.
Exactly the same here. I've had three software subscriptions until this year, mostly begrudgingly — CreativeCloud, Evernote and 1password.
I got rid of two of them — Evernote for exactly the same reason.
1pwd going the Electron route would have put me close, but not over the edge — but the fact that they seem to have willy-nilly removed local vaults does.
These days it sometimes feels like one has to write all essential software oneself. Or go back to DOS and plain text files.
> but the fact that they seem to have willy-nilly removed local vaults does.
They're a business, and 97% of their users were already on the subscription model. If you were running a business, and 97% of your users had abandoned a feature that was a headache for you to maintain, would you stubbornly keep wasting time and money on it?
Oh so THAT'S why the Evernote update sucks. The Android client is terrible, it dumps me to the useless Home whenever I scroll to the bottom. It's now unusable. I've begun transitioning to Notion because of it.
Similar here, I started using 1Password pretty early too. One of the main selling points for me: The nice, fast and native UI and the ability to keep my store local and sync it however I want.
The only wish I had over the years(and I would have gladly paid for an additional license): a linux client, even CLI would have been fine.
I'm not sure which year they started, but what they pushed instead was the announcement of online sync and other things I did not care about, at some point it became hard to even find the regular version on their website.
This was when I slowly started moving to alternatives. With the move to electron and this anouncement here I'm happy that I moved away a few years ago and their clear signal that I am not the kind of customer they have any interest in anymore.
> Subscription business models and non-native apps are hallmarks of rot by VCs. Dump them!
The costs of developing and maintaining software are recurring -- especially for security-critical software. Subscription business models align incentives towards ongoing maintenance.
Somewhere in the middle but towards the latter end of things. I believe that before the licenses, they did not have the recurring revenue to pay for a high-quality support team.
When I was 18, I wrote some shareware and asked for $10 from those who used and liked the program. Lots of nice people from all over the planet sent in some money, and sometimes with letters. Most often it was a thank you note. Sometimes people requested more features in return for paying the requested amount. And occasionally they'd tack on whatever extra they thought those features were worth to them. (That amount was less than minimum wage, if I took the time to implement those features for them and release the software.)
I recently visited my friend from our programming club who saved these letters and was reminded a couple people wrote additional angry letters years after paying for the shareware. They demanded support in return for their one payment. (Of course, not only had I moved on to other projects, but I had long sold the type of computer the shareware was created for!)
So I learned early on that people unreasonably expect support for no additional cost. Or they believe the amount they paid is for support in the future, not work done in the past. It doesn't work that way economically. A constant flow of additional money has to come in the door to pay a team to do the actual support.
AFAICT, the only feasible models for supported software seem to be subscription, microtransaction or advertising. Any one-time-up-front price means it's abandonware. Which is fine for some types of software, of course, but probably not as often as users expect support.
One could argue that their support team has handled this change unskilfully and that Agilebits should have hired a larger and more skilled support team before having a way to pay that team.
One could argue that.... but one would be silly to do so.
Subscription models make sense for something that needs to stay evergreen.
Why does a password manager need a subscription? My password should never touch a 3rd party’s server, I don’t need extra features, I don’t need a login, I don’t need long-term or even short-term support.
What ongoing development does a password manager have? Is it that buggy from the get-go to need constant updates?
> What ongoing development does a password manager have?
I shutter to think about just trying to keep the status quo across all those platforms, devices, browser extensions. How often do we have new versions of iOS or macOS? What about Windows, Android, Linux, Chrome OS?
I can think of a TON of work without adding a single feature.
Major releases of MacOS and iOS happen once a year. And most of the time they don’t break existing applications (iOS 12 notwithstanding). Almost everything from early iPhone OS to 12, and from 12 onwards worked ok, even with major resolution changes.
And the fact that we need to constantly change stuff just for the sake of change is the problem.
To add to this: I’m perfectly happy to pay a premium price for software when I need a new version. I did this with Photoshop for years, $399 per copy was perfectly fine for me because I spent that money every 3 or 4 years.
There are also what I think are reasonable models for providing people with ownership of an app but also being able to charge upgrade fees (for example, TablePlus, Dash, Sublime etc)
That's the point of this thread. YOU only need a new version every 3-4 years so you don't think there's any work any other time.
But you take all those platforms and all those extensions and the result is maintenance by itself is constant work. I'm not talking about change for the sake of change. I'm talking about the work just to keep the features that you have.
I have personal projects I'm working on where it feels like all I have time for is just keeping up with security updates, Ubuntu versions, DB version upgrades. Work projects are even worse with SOC2 requirements and the endless stream of CVEs.
There's no way a password manager can do nothing for 3-4 years ignoring security vulnerabilities in their dependencies that need to be patched.
You raise a valid point, and certainly then this product is not right for me due to their pricing and the features I’m paying for but never using (like Android and Ubuntu support).
It comes down to what value it provides to me for what I need it to do, which is store and retrieve passwords for me, and sync via wlan. That’s it. Why should I continually pay for Android, Ubuntu or Windows development when I don’t use their app on either of these platforms?
And additionally, as a consumer it’s not my responsibility to find a way for a company to fund its product. Saying “development goes on even without you upgrading, so you have to pay a subscription to support that” is kind of a weird argument, isn’t it. Imagine if you had to pay a subscription for using a car because next year a new model will require development and therefore you need to pay for it.
Most of the time the software doesn't even need to change, you just need to open up xcode and recompile the project against a new ios sdk and you're done.
Sure, a local-only password manager doesn't need a subscription, and solutions such as KeePassXC demonstrate this quite well (as a user of it myself!)
However, in the case of 1Password it's not just about being a password manager; it's also about syncing passwords between devices, staying on top of (sometimes rapidly!) changing standards between devices and browser extensions, and being aware of the evolving landscape of best security practices.
I don't know how subscription fixes your problem. Now people will still yell at you, even once you've moved on to other projects, and even more people will do so since they actually pay and assume that it is your obligation. You haven't fixed the "people are assholes" problem.
A better solution honestly is just to accept some percentage of people will be little assholes but hopefully, as you remembered before your friend brought it up, that most people are gracious and kind. Focus on those people.
The subscription fixes the problem because you can use the money from it to solve other problems in your life like having insufficient tacos in your stomach.
> So I learned early on that people unreasonably expect support for no additional cost. Or they believe the amount they paid is for support in the future, not work done in the past.
If I buy a piece of software, it's not unreasonable to expect it to work for some period of time after the purchase. This is especially true on the Windows side, where Microsoft has gone to great lengths to keep old APIs around and support most (but not all) old software within reason. I have engineering software programs that are a decade old that still run fine on my Windows 10 machine.
macOS has been less shy about deprecating old APIs and forcing software updates. I probably spend $500-1000 every year just upgrading a certain few software packages that charge for a new version every time a new macOS comes out, and I hate it. I don't mind paying for new versions of software, but it's becoming saddening to watch all of my macOS software rapidly decay away with each macOS upgrade unless I buy the newest version.
> it's not unreasonable to expect it to work for some period of time after the purchase.
"it works" and "the developer gives me support" are two different things. In this case, I'm sure the shareware he wrote still "worked," but clearly they thought they were entitled to perpetual updates or the ability to chat to the developer any time they like.
As far as I'm concerned, the SLA of $10 shareware I volunteered to pay for is "whatever the developer is willing and able to provide." It's $10. ¯\_(ツ)_/¯
Fwiw, 1Password isn't nuking 1P7 or existing local vaults. Those users are free to keep using v7 for as long as Apple or Microsoft allow the app to be installed on the OS. (And I do agree, macOS and iOS are both quite abrupt about cutting off support and I commend Windows for going to great lengths to avoid it)
Umm, the thousands of successful software companies before subscriptions, microtransactions and advertising were common in the software industry would like a word with you.
1Password on Linux is electron, and works wonderfully. Though, it's kind of sad for Mac users as they have been spoiled with native experiences for a long time.
This! Windows, Linux and macOS are OSes with very different aesthetics and concepts. Trying to emulate these (sometimes subtle) differences with a webpage won't work. And it will totally destroy the illusion if an OS update comes with a new theme.
And let's not forget that you're basically running a completely separate browser that can't re-use any memory from the other 5 separate browsers (=Electron apps) you need to run for work all day.
I think a subscription business model is the only honest way to sell software that will require ongoing support. If you're comfortable with a snapshot w/o updates, then by all means buy once, but I think coming to terms with the demands of ongoing support also means coming to terms with continuing to support the product in some way.
That said, I wish there were more variations in the way to pay - a long term license with a high upfront fee and a low monthly, an immediate access option with a high montly and no up-front fee, etc.
why does 1password need ongoing support? Take these strings, encrypt them. Let me decrypt them using a password i specify. Let me search for them and sort them.
I mean, I don't know - I don't work at the company. But it seems internally inconsistent to me to like the product, but have disdain for the professional judgement of the people who make it.
It seems like you'd be happier with a community product that has less support, but is available for free - and thankfully you have that option.
I don't quite see why free bug fixes/minor features + paid major upgrades model should be any different from subscription model for developers, except giving the users control over when to upgrade. Control that is essential for apps that contain critical data.
BTW, I think they do have an option that you pay for 3 years upfront. At least, that was one of the options they mentioned when I complained about the lack of the option to buy a license. To me that did not seem an acceptable solution because you pay upfront and still have all the drawbacks of the subscription model such as being dependent on the trustworthiness of a quite obviously untrustworthy company. Add to that the removal of local vault option, and it becomes even less acceptable.
The developer time it takes to do bug fixes and minor features is not free, so it seems appropriate to charge a fee for it.
I know that it's very common for subscription models to coincide with forced upgrades (as this one does), but that seems like a choice on the part of the company as opposed to something inherent to the revenue model. I'd be quite happy to pay a developer to continue to maintain an older version of their software.
Like you pointed out, I think a fee structure where you pay for major updates and otherwise pay a maintenance / hosting subscription fee makes the most sense.
I think that you see open source projects that struggle along all of the time because their developers cannot afford to work on them enough. Not every project, but enough of them. I try to support projects like that too.
Hi. I'm a feature developer for 1Password, and I want to clarify a few things. I've already posted this elsewhere, but I've seen multiple threads spreading misinformation that our technical decisions are being driven by VC funding. This could not be farther from the truth. We have been working on these changes long before we received any form of outside investments.
Over the past few years, we've been working on consolidating 1Password's business logic into a single Rust-powered core that could be shared across all our apps. This has many advantages: feature consistency across platforms, faster development cycles, and better security. When building the front-end for the desktop platforms that would take advantage of this new core, Electron suited us perfectly, since we could write our UI code once and make it consistent across Linux, Windows, and Mac. We actually did build a native Mac app initially alongside the cross-platform Electron app, but we eventually decided that having two separate versions of the macOS app (one in Electron, one in SwiftUI) would cause a lot of needless development churn and hassle for both customers and our support team.
I can understand your frustrations about Electron and our subscription-based model, but I hope you find my explanation reasonable. Please stop spreading misinformation.
> I've already posted this elsewhere, but I'm seeing some misinformation that our technical decisions are being driven by VC funding. This could not be farther from the truth. We have been working on these changes long before we received any form of outside investments.
That's worse, not better.
At least being forced to by investors makes sense. The current direction of travel being voluntary means you've just got a bad nose for building security.
Hi, long-time user, customer, and word-of-mouth recommender of 1Password for the nine years my Hacker News account has been active (give or take a few months). This is a big announcement that I'll have to chew on to understand what this means.
Can you quantify the "needless development churn and hassle for both customers and our support team" in some way? Presumably, 1Password 7 and its ancestors used native macOS APIs, which meant some degree of that given you had to do something different on Windows and/or Linux. I don't know what your support team has had to endure, but as a long-time sample size of 1, I've been incredibly satisfied with the way you've designed and engineered the macOS application (and the iOS app too!) to date; I'd be hopeful that whatever tradeoffs y'all will be making moving to Electron, the "native" feel of the macOS client wouldn't be sacrificed. Is there anything you can speak to there that I should prepare for with 1Password 8?
> Can you quantify the "needless development churn and hassle for both customers and our support team" in some way?
Sure, happy to elaborate on that! Since we were rebuilding our app from the ground up, it was a significant slow-down on development to create a user interface for both Electron and SwiftUI, requiring two separate teams of platform developers for every feature we needed to implement. There were also concerns by the documentation and support teams that we would need two separate sets of instructions for many common tasks, due to small differences in layout and look between the applications. Eventually, we had to make the tough decision to focus on a single common framework for desktop. This will allow us to ship features across every single platform far quicker than we could before.
> I'd be hopeful that whatever tradeoffs y'all will be making moving to Electron, the "native" feel of the macOS client wouldn't be sacrificed.
We've tried our very best to keep the experience the same so that the transition from 7 to 8 is smooth, and from my point of view 1Password 8 feels right at home on macOS - I especially love our new translucent sidebar. That being said, this is still in an early access stage, so there are bound to be hiccups and UI issues that need to be resolved. Please let us know if you run into any problems or have suggestions on how we can improve. And thank you for being a long-time user!
I mean looking at this I can see why people came to the conclusion that this was primarily a move that VC funding caused even though AgileBits seem to vehemently deny this.
The funny thing is, they were doing just fine for years with just their own money. Now that they have sooo much more money, they suddenly can't afford separate developers for different platforms... they should be able to hire 10x more people now.
The primary issue with having two separate teams for the same platform was not money, it was time. To be clear: we wanted to build a native app in parallel with our cross-platform Electron solution, and we had the developers to do it. But unfortunately, having an additional team that needed to implement the UI for every single new feature was a significant slow-down, and we collectively realized that we could not meet our deadlines nor maintain this long term.
I'm sorry for not being more clear earlier as to why we couldn't support two separate teams for the same platform. Hopefully this clears up any confusion.
I don’t understand why two teams means slower. Are you keeping the total number of engineers the same? If you are saying 2x engineers on electron complete tasks faster than 1x on electron and 1x on native, you are basically agreeing with OPs take.
You take money to provide software. But then you become lazy and greedy and want 1 size fits all. End result is your users having clunky, high latency experience.
I think he’s saying 1x on both Electron and Swift UI was making it too hard to ship either version to an acceptable standard because each was slowing the other down due to inconsistencies, difficulty staying in parity and double communication.
Unfortunately, it’s normal in software development for multiple platforms to increase development complexity when feature and UX parity is prioritized.
Maybe I'm missing something, but i pay for those teams with my client purchases. I have a mixed computing environment and have purchased versions 3, 4, 5, 6 & 7 for three platforms.
This is such nonsense that I can't let it go unremarked. I can count on the fingers of zero hands the number of times 1Password has shipped a "new feature" between major releases. There are no new features needed, it's a password manager. However, I would need to borrow some extra hands to count the number of features you've removed, features that loyal paying customers of many years depend on. 1P7 doesn't even let you keyboard navigate to the Generate Password button for goodness sake - something that I was able to do in every version up to that point.
Absolutely nothing about any decision AgileBits has made in the last 4 years has had anything to do with what customers (that's us, the people that used to give you money) want, and everything to do with nickle and diming the suckers dry.
UI consistency between different operating systems is NOT a user-focussed feature. When I'm on a Mac, I want my apps to behave like a Mac app. When I'm on Linux, I want my apps to behave like a Linux app. If you _actually_ believed that all apps should look and behave the same on any OS, why does the Android version look and behave nothing like the Mac app?
You've removed features with every major release, and this is just smashing the final nail into 1Password's coffin. You've ruined what used to be the best password manager on any platform.
I am very unhappy that 1P is moving to Electron for macOS for the reasons people here have reiterated a million times. I am actively looking for alternatives now.
You'd get rid of a working solution because of an implementation decision? I _love_ 1P, and I use it on Mac, Windows, Linux, and iOS, and it makes perfect sense that they standardize on Electron.
> You'd get rid of a working solution because of an implementation decision?
Yes, because the implementation decision has implications for both performance and UX. I’ve used 1Password since version 3 (2013!) and gotten friends and family to do the same, but I think I’m done when 7 stops working.
As much as I'm "meh" on Electron, I rarely use the actual 1Password App. On the other hand, I use the Firefox extension 30+ times a day, and that's about as far from a native app as you can get. So I think I'm fairly unlikely to notice a huge issue, and will instead be pleased that consolidating on Electron gives them greater feature velocity.
On the other side, I use the 1Password app extensively and make heavy use of all the different categories (secure notes, Windows MSDN licenses, etc). I’m extremely disappointed to see this turn into yet another sub-native browser-in-a-window experience.
I'd like to believe this isn't primarily profit motive. What gives me pause is how I write regularly asking for separate vaults for trivial passwords and passwords that could lead to financial ruin. The profit motive wants to keep 1Password simple to use, at the expense of security. I've been forced to buy a second password manager for sensitive passwords.
I'm sorry you feel that way. I'd love to know more about your issues with our current vault implementation in more detail, so I can pass along your feedback to the rest of the development team.
> What gives me pause is how I write regularly asking for separate vaults for trivial passwords and passwords that could lead to financial ruin.
Just to clarify, what solution are you asking for? Do you want a local vault option to store sensitive passwords? Or something else?
>would cause a lot of needless development churn and hassle
The hassle of doing what your users are paying you to do? Any child can hack a UI together in HTML but there's a reason no one (usually) pays for that.
This makes sense to me. Lots of other products have head in the same direction over time (e.g. YNAB) for similar reasons.
SaaS is familiar to consumers and ultimately a nicer business model for most products. If you support SaaS for new customers, maintaining the old product / pricing model indefinitely eventually stops making sense. At some point you have to make a move like this.
It is probably particularly timely to do this because Lastpass recently changed their pricing model (whether deliberately aligned or not). It's no longer possible to use the free plan of Lastpass and use it on both desktop and mobile: you have to pick one or the other. For many use cases this is effectively a requirement to use the paid plan. So now 1password has the opportunity to push legacy users to a paid monthly subscription knowing that some portion who may have switched to Lastpass to avoid a monthly fee now won't be able to do so, and will probably just pay the monthly fee to 1password instead.
I will run the installed version of YNAB as long as it runs on my computer, and after that I'll probably run in in a virtual machine until the end of time. I am not comfortable with my financial information being on the cloud in the hands of a third party, much less so when it is not the likes of Google and Apple with armies of security engineers and can be hacked much more easily.
Yeah I can totally understand that. I'm similar with the sync feature: the last thing I'm going to do is give them (or their 3rd party provider) my actual bank credentials. I would feel better if they supported some type of end-to-end encryption. I can also understand how, at least from a business perspective, most users probably don't care enough to not use it.
FWIW, YNAB never receives or touches your bank credentials — sign-in happens through MX and Plaid, which hands back a token to YNAB to use[1]. For banks that support it, the process goes through OAuth and you sign in directly with your bank, so even MX and Plaid never see your credentials. The whole process is end-to-end encrypted, with no credentials stored at rest (unless necessary on the MX/Plaid side, but they handle that).
Not trying to change your usage or habits, just wanted to clarify.
Thanks for clarifying! I understand the architecture but perhaps didn't explain it properly in my comment.
It does honestly strike me as the best approach given the constraints, but here in Canada almost none of my banks are supported with OAuth flow last time I checked so giving the 3rd party providers my credentials and having them log into the bank both violates the TOS of my bank and is also far less secure than I'm comfortable with. Storing my financial details in YNAB / their partners is one thing, storing credentials that can be used to actually move or spend my money is another.
It's honestly not a huge deal for me personally. Entering the transactions manually is a good habit as I can see the balances update and mobile app is easy to use right on the spot.
Totally fair and reasonable! Too many banks here in the US too that both make it against TOS to get external access to your data and also refuse to offer anything secure like OAuth — extremely frustrating :/ At best you can try to pressure your bank to support OAuth but... we're just small fries.
Yeah banking is stuck in decade old technology in north america. Heck I'd settle for TOTP (or any 2FA in some cases) or getting rid of those harmful security images.
A number of information sharing activities cannot be limited. This is typical of any bank or financial institution. Your bank has its own vendors, many of them are themselves SaaS and cloud hosted!
My point isn't to say "Why care at all? Just open the floodgates!" Instead, my point here is that trust and security in our society is only as good as the people and institutions that back them up. We don't use bank vault doors for our front doors just because we have the knowledge that anyone with simple tools can defeat a home lock.
Therefore, I think that the choice of more inconvenient solutions made just to avoid some nebulous what-if scenarios involving privacy is often (but not always) the wrong way to go.
A) They will have all of your financial information, as opposed to banks that will each get a slice. So the data they have is much more sensitive.
B) YNAB has around 100 employees in total. They do not have the resources to secure their data the way big banks do. We all have our doubts about security at big banks, but I am sure small startups are way worse.
C) It was all unnecessary for YNAB to go online. The decision, much like 1Password's was about money, not clients. I cannot live in this day and age without a bank account. I can live with an old version of YNAB. Heck, I can live even without YNAB. If banks are necessary evil, YNAB is an unnecessary one. Why increase your attack surface with unnecessary stuff, just because there is some necessary attack surface remaining?
Re. point C, I think everyone's use case is different but for an alternative perspective: it was absolutely necessary for YNAB to go online for me to buy it.
The mobile app is a really key use case for me, and even as a technical person I just can't be bothered to set up hacky sync via dropbox or expect my family to know how to do that. Even if I could be bothered, now I'm just kicking the responsibility to dropbox + myself with all the same problems. I'd rather have the app developers manage that responsibility.
I held off on the new YNAB for a very long time before switching about a year and a half ago. I absolutely love the new version and the syncing works so much better than before. And the new iOS client is loads better.
I was pretty stubborn at first, but honestly 7 has a lot of nice features, especially for families. You can also continue to use your old vault, though the announcement here seems kind of vague if this will continue to be true.
I've never tried 1Password but I've seen many here who endorse it. Does anyone have experience with both 1Password and KeepassXC? Especially with 1Password local vaults...
I've only briefly tried Keepass but the UI, the general clunky nature of the UX and such turned me off. To be completely fair, this was 3 years ago when Lastpass was becoming more and more useless and unreasonable. I tried out Dashlane and ended up using 1Password and have been a very happy customer since. I'm not particularly concerned with self hosting or syncing personally
I used KeePassXC as the Linux client for 1Password before there was one from AgileBits, and stopped short of implementing _write_ for the opvault format because that wasn't in my use case (and I also had some non-trivial concerns about KeePassXC accepting the PR, so I was trying to pitch it as a way to get more people to import 1Password opvaults)
I would be on-board with implementing the write side to opvault if they'd accept the PR, and would also implement the browser extension protocol server if 1Password would specify it, since as others have pointed out the KeePassXC browser extension is suboptimal
Then again, with all the massive outpouring of Bitwarden support in every single one of these threads ever, I am pretty sure the real solution is just to bite the bullet and jump ship to Bitwarden/vaultwarden like everyone else seems to be doing
I'm willing to stick around long enough to see if AgileBits makes good on their local vault something something, but given the past few years of activity, I'm going with "they're bluffing" or "it'll be a horribly hobbled implementation"
> Then again, with all the massive outpouring of Bitwarden support in every single one of these threads ever, I am pretty sure the real solution is just to bite the bullet and jump ship to Bitwarden/vaultwarden like everyone else seems to be doing
To follow myself up, I seem to have found another "those people don't know what they're missing" situation because I actually did try Bitwarden (Premium) this weekend and what a dumpster fire compared to 1P
I thought about writing up all the shitshow, but ultimately it just boils down to them not caring about their product or users
For some of the platforms, I would actually be on-board with jumping in to fix the innumerable bugs, but with them being a mixed setup (open and "premium" features), the fact that so much fundamental behavior has been broken for so long with no obvious mitigation strategy makes me question whether this is something I would want to invest in
Never had any reliability issues with iCloud Keychain since switching over 2-3 years ago, but obviously it's less featureful than 1Password. I liked how 1Password had a dedicated section for software licenses, but now just use a Notes note for that.
The most valuable parts of 1Password for me are storing non-password stuff like license keys, secure notes, random security question answers, and the like.
I’ve always used secure notes in the Keychain app for this. Not as smooth as 1Password, but it does the job when I need a licence number (when I get a new computer, so once every ~3 years) or an answer to a security question (can’t say how frequent that is; certainly not more than 1 every other year).
I’ve been doing that for more than a decade (more like 2 actually) without a hiccup.
I don't recommend Apple's keychain. It's smart enough to track usernames and passwords and feels very satisfying to use on an iPhone, but doesn't capture some other parts of authentication. This includes security questions, OTP, capturing notes around how sign-ins can be weird (HSAs and other portals rife with redirects), and non-iOS devices (as well as non-safari browsers).
Bitwarden is fantastic. I pay for the OTP features, though I feel keeping the codes alongside my passwords weakens my security posture. That's my choice, though.
I've used iCloud Keychain for all my personal stuff since it existed. It's pretty bare-bones, but the built-in integration into Apple's software makes it a no-brainer for me. It's worked great!
My daily drivers are a MacBook Pro and an iPhone, but I'd go with a 3rd party password manager every time for the ability to access passwords on a non-Apple device if I want.
There’s some nice “sanity checks” on all passwords, manual or generated, like reused password warnings and by default it checks your logins at haveibeenpwned, which is a nice to have.
It supports many more kinds of secure data than passwords and credit cards. It has specific entry types for bank accounts, passports, reward programs, software licenses, and so on.
It also has lots of built in analysis tools for determining:
- which of your passwords are reused, weak, or present in online password dumps
- what websites can have 2FA enabled on them
As well as the ability to store entire documents in vaults.
Been using 1Password since 2008 and it's the only software of its kind I recommend to anyone on any platform.
I like it for a number of reasons (other wallet apps can meet these bars, as well):
1) It is very cross-platform. It works on iOS, Android, MacOS, and Windows. I believe that it is also Linux-ready.
2) It has the ability to sequester groups of passwords into "vaults," that can then be assigned in different configurations, for different accounts. This way, the Treasurer gets the banking login, and whatnot, but the Webmaster never sees them, and Treasurer never sees the CP login.
3) It seems to support a whole bunch of TFA.
4) It syncs over everything, and helps to enforce password hygiene.
I'm glad I've been using Bitwarden anyway, I guess, but to me, this is totally unacceptable for security-critical software. You absolutely need to make it possible to self-host. If you're content to only ever be available to low-information, low-effort individual consumers, fine, I guess that's a market, but you've locked yourself out of ever being able to sell to high-security organizations that can't use public cloud services.
I highly recommend Enpass -- solid UI, single purchase, local vault, and a very handy option to sync via Dropbox (and probably through other services as well).
I am a big fan of 1password. I was very unhappy with the transition to subscription only, and tried bitwarden. After months of futzing around with it, I went back to 1password.
I did so after reviewing their audit results, awhat they documented about their architecture, and after they added great support for Linux. At the end of the day, not everything is a conspiracy - and their model appears to be incredibly secure.
I would like the self-hosting option (that like Bitwarden, will still require a subscription), but a big part of what I am doing is sharing credentials with family. 1Password does a great job there.
Honestly at the end of the day, everything else is about your value proposition. I didn't know or realize that 1Password had shifted to electron as asserted elsewhere. I guessed that there was a new version given that linux was supported but it made no difference for me. Great for them. Likewise, they are far more secure then me editing a password file. Eventually the market will decide here. If people really care about swift versus javascript, then it will penalize them eventually.
That said, people arguing that dashlane and others are better then 1password, given that dashlane has access to your passwords, I can't imagine that this is a choice that makes any sense given the basic requirement of a password manager (keep my passwords safe).
> That said, people arguing that lastpass is better then 1password, given that lastpass has access to your passwords
Don’t get me wrong, I hate Lastpass with an unprecedented rage for something that should be a simple utility (I’m forced to use it at work and it’s a time sink), but I don’t know where you get that and would like a source.
Are you sure that the passwords that were the object of the study came from the password manager itself? The paper that is referenced says this in the introduction:
> In this paper, we seek to fill in the gaps by gathering and analyzing a large collection of leaked password datasets across multiple years and various online services
> Virginia Tech researchers led by Dr. Wang have collected a number of publicly available password datasets from the Internet in January 2017. The datasets were obtained from various online forums and data archives.
It looks like they just used already leaked passwords.
Please, if you haven't already, fill out this 1Password survey. They are considering self-hosted vaults but want more data on who/how it would be used:
They’ve gone over and beyond to support old licences far longer than it could be expected, and a password manager is the kind of sensitive and ubiquitous product for which SaS actually makes sense.
Anyone remotely involved in anything similar knows it’s a PITA to keep up to date while keeping device compatibility, and the folks at 1P have been doing great work.
Actually a sensitive product is exactly where this does NOT make sense. No matter how good their security is with their cloud version it will still be less secure than having a vault locally on your disk. That is a fact.
Subscription services to me are only justified if they are providing a SERVICE which they are with the web version and ability to sync through their own servers, however, using a local version with your own vault can be done without any service at all.
So to me this looks like them intentionally crippling their own software in order to force people into paying a subscription fee that is not necessary. They already hide the ability to purchase a standalone license for 1Password 7 trying to get people to pay the subscriptions so this is the next logical step.
Hi, I work for 1Password. I can understand your frustration that we're phasing out local vaults. Luckily, I have some good news: we're currently running a survey to gauge user interest in self-hosting options. If you're interested, go to https://survey.1password.com/self-host/ and let us know your thoughts. Thanks!
> Actually a sensitive product is exactly where this does NOT make sense.
The idea that anyone except a tiny infinitesimal minority of all people should self host is ridiculous.
Even a lot of people with IT jobs have not enough time or knowledge to keep services like this working securely in a way that’s competitive with SaaS (i.e. these people are better served by paying others to do the job).
If you need any proof, just wander around any company that works in IT and do a simple check, see who has the latest OS version and who doesn’t.
But it was never about self-hosting: a local vault can be synced between devices on the same network - all you have to do is to open 1PW on both of them. Everyone can manage it.
I got started with 1Password SaaS based on a work account and added it for my family, so I am not losing anything with this change. I've generally been pleased with the service and its definitely been an upgrade from LastPass in terms of usability and security (no random autofills into hidden forms, no breaches etc...)- that said I'm sad to see this direction. I can't see how this could have been costly to maintain, nor that it would bring them incremental revenue given the backlash and ample competition. Maybe predictable cashflows are worth it, but in principle self-hosting should always be an option.
I guess I’m the outlier in being very happy with 1Password and fine with paying for the subscription service. Not only is 1Password the best password manager I’ve used, but it makes it seamless to share stuff with my wife. I don’t care if 8 is an Electron app either, considering I usually interact with it via the browser anyway with their extension. (Also I know that the majority of what they wrote for it is Rust and fast, and I generally trust the engineers to do a good job since they’ve done a good job with it in the past) Also they make a CLI tool for accessing passwords allowing you to integrate password management there: https://1password.com/downloads/command-line/
What I have zero interest in is increasing my attack surface solely for their bottom line.
I'm also increasingly uncomfortable with the company handling my passwords engaging in the sort of spin and dark patters we've seen from AgileBits in the past few years.
I'm curious about how you see the attack surface increasing when using 1Password. My knowledge of how it works is that it always stores your passwords in an encrypted blob that can only be decrypted with a combination of username, "master password", and vault password. So no matter if it's in Dropbox, 1Password's servers, or your own hard drive, if anyone obtains a copy of the password file they still have to crack it before they gain access to anything.
Also I see your reply has been downvoted enough to become grey. (EDIT: Looks like between starting writing this and submitting it, you're no longer in the gray from downvotes!) I imagine it's because you made a blanket claim about spin and dark patterns without any supporting evidence. I'd be curious to know what you're referring to since I don't really keep an eagle eye on this stuff, I just use their product.
The one thing I do remember in the vein of "dark patterns" is how they effectively hid the method of doing a one-time payment for 1Password where you have to manage syncing and backing up the password file yourself. Seeing as I have no reason currently to do anything but make a charitable read of that situation which has been decried more than once on HN, I'd be willing to bet they did so for the following reason: They have had many problems in the past where a customer has lost a password file because they were not a power user and did something such as keep it on one hard drive in their only computer. (reinstalled windows, hard drive died, etc.) So they wanted to make something that would prevent that from happening for the vast majority of their customers that don't really understand stuff like backups, or don't have Dropbox, or who aren't part of Apple's ecosystem and have iCloud, etc. so that their passwords will remain safe and secure. So they made their own sync service and hid the version that would do local-only files so that only the dedicated users who really want to do that would find it and use it.
OR alternatively they're a bunch of greedy people that just want to hoover up dollars from our wallets, as people love to accuse them of here. Maybe a little of column A and column B, honestly. Something something needing to ensure they have a company that stays in the black without wanting to absolutely bloat up their own software so it becomes another useless Enterprise(TM) application with each passing paid version.
Also the only affiliation I have with 1Password is I have a friend I recently learned works for them, otherwise I'm just a customer. I just got into one of my little ADHD focuses where I really wanted to reply with something long and detailed, so please don't assume I work for them or something and am defending them because of that :)
> So no matter if it's in Dropbox, 1Password's servers, or your own hard drive, if anyone obtains a copy of the password file they still have to crack it before they gain access to anything.
When I keep it on an airgapped machine that's a lot harder than when it sits on 1password's internet facing servers.
> So no matter if it's in Dropbox, 1Password's servers, or your own hard drive, if anyone obtains a copy of the password file they still have to crack it before they gain access to anything.
Except that they control the client that I'm entering the master password into. So either the password is sent to their servers anyway or a malicious actor could simply update the client to do so.
But you can take your device off the network when running the password manager to ensure it isn't able to do that, for example. (Or more realistically, you can watch with something like Little Snitch or WireShark to ensure it isn't happening.) That's something you can't do when the password manager requires the network to do its main function.
It's absolutely incredible to me that people ignore one of the biggest sides of the argument for pre-baked, user friendly products like 1Password: usability for as many people as possible.
You're trusting the client whether or not it can talk on the network. A malicious update that starts generating predictable passwords for websites doesn't need a network connection.
You're of course free to use whatever software you want or do whatever you want. But I think assuming that you're going to see a malicious actor updating your password manager to steal all your data shouldn't be too high on your list of things that you think will realistically happen. I'm not saying it's impossible, just one of the least likely things to happen.
> I'm curious about how you see the attack surface increasing when using 1Password.
Someone above outlined it nicely: If you let 1Password take care of encrypting the vault, and iCloud (for example) of storing the vault securely, then a malicious actor would have to compromise both products to get your secrets.
> I'm curious about how you see the attack surface increasing when using 1Password. My knowledge of how it works is that it always stores your passwords in an encrypted blob that can only be decrypted with a combination of username, "master password", and vault password. So no matter if it's in Dropbox, 1Password's servers, or your own hard drive, if anyone obtains a copy of the password file they still have to crack it before they gain access to anything.
_If_ they obtain a copy of my password file.
"My email is nucleardog@nucleardog.example, my password is abcdef12345."
If I'm using 1Password's cloud service I'm... screwed? You now have literally my entire digital life.
If I'm syncing anywhere else, you've got a much bigger task ahead of you. First you have to _find_ where my vault is stored, then you need to gain access to it.
There's an extra layer of security to the way I want to do this. An extra factor of authentication. I don't want the only thing between you and my entire life to be one set of credentials.
I think bitwarden is much less cringey as a corporation if you're looking for an alternative. I use it and pay an annual subscription and have no issues. You can even self host if you get fed up with pay for a suscription or their free service.
Agreed. In the end 1Password has always been a subscription, just you paid "one-time" upgrades every two years to stay up-to-date with the latest version.
However the differential factor of 1Password, which was that it _didn't_ provide the storage if you didn't want it, has now gone away. Precisely why I chose 1Password when I started using it. I don't see the difference between this and any other password manager now.
There might be security or technical reasons for removing this option, but looking at how hard they've been trying to get me into a subscription during the last couple of years I just think we're on a bad case of subscription-all-the-things here.
100% same. I've been a happy subscriber for years now, and recently switched to the Family plan to try and get my parents to start taking security a bit more seriously.
I've been using 1Password for 3 years now. Been paying $35/year and I'm with you on this one. I really like their service. The integrations are great. I rarely use their Mac app. I use my Apple Watch to unlock 1Password in my browser. That for me, is a game changer. It's such a seamless experience. I'm a happy customer and I love the service.
1. Open 1Password Mac app
2. Go to Preferences > Security > Apple Watch (there's also option to enable Touch ID) and enable it
Make sure you have your browser 1Password plugin updated to the latest version.
When you click on the locked 1Password icon in the browser, you get the "Double click to approve" alert on your Apple Watch. You double click the side button on your watch and 1Password in your browser is now unlocked. This also works the same way with Touch ID. Hope that helps. Cheers.
I come at it from a slightly different angle. I got in when it was syncing via Dropbox and iCloud, and it worked perfectly fine.
The switch to a subscription service is a forced downgrade for me; it's putting functionality I already have behind a subscription.
This is particularly an issue since the old versions (versions I paid for, mind you) are slowly going away (typically as a recompilation and submission is required to keep them available on iOS devices).
I'm somewhere in between. I also paid for a non subscription version and I also feel like I was forced to upgrade to the subscription. Sadly switching password managers, especially if you share with a family, is really painful.
We now pay the subscription, a tad begrudgingly, but I have to admit 1Password overall does a great job.
It’s not a complete import, you’ll get usernames and passwords but if you’ve done anything else with it (like say attaching software license files, scans of important documents, etc) they’ll be silently dropped.
Most record types (software license, wireless router, documents, drivers licenses, email accounts, membership, passports, maybe more) don’t exist in Bitwarden. I’m not sure what happens with all of those, maybe transformed into secure note, but again with all of the attachments removed. The lack of categories is also a nuisance for organization, you can create folders but have to manage it manually.
I’m still glad I switched, having bought 1Password on a bunch of platforms and a bunch of paid upgrades before it turned into a subscription. It probably would have been less money if it had been a subscription from the start with all the times I bought it. Maybe it’s irrational, I just don’t like being so dependent on a subscription service, and having a local network sync between my devices was just fine. Same reason Lightroom can pound sand with their $120/year licensing, I’m not going to keep my photo library in something that I just have to keep paying for the rest of my life.
Bitwarden is good enough for me, with 1Password as a subscription you can look at it and realize “this is going to be $36/year forever.” If I spent any time in it, might be worth the expense. I’ve bought a lot of software and I don’t mind paying for good software. But I’ve moved the things that were attachments to an encrypted disk image, and 99% of my password manager interaction is via auto fill so I don’t actually care how polished the UI is.
Family sharing would be a more compelling reason to stick with it if you’re using that.
Before I started using 1Password I did use the secure disk image method for storing what I now store in 1Password. But it's only a few things, really, and in every case it's just to have quicker access to something normally stored in a file cabinet so I don't have to dig into the files.
> It’s not a complete import, you’ll get usernames and passwords but if you’ve done anything else with it (like say attaching software license files, scans of important documents, etc) they’ll be silently dropped.
It's not quite a silent dropping -- 1Password warns you with a popup during the export that it doesn't include them in the export file. BitWarden won't warn you, but in its defense the files aren't even present for it to skip...
I have done this, and it was horrible… for example I was missing all attachments (no notification or error messages). Also the fields are not properly converted 1:1.
All in all, it was a big mess. This was about a year ago.
Funny story: I migrated from lastpass to bitwarden a couple years back. I expected a big mess. Instead, the import was better than perfect: a bunch of accounts that wouldn't autofill in lastpass magically started to autofill after being imported into bitwarden.
I think it might be the only "better than perfect" import story I've ever experienced, and I can't rightly expect it to happen again, but it happened once and that's something.
Bitwarden's model is consumer friendly. I really appreciate being able to self-host a fully functional vault, even if I don't exercise that option. I feel confident that they won't hold my data hostage. $10/year is a great deal. +1 for bitwarden.
This is the exact experience I had. I was moving from Lastpass after they sold out. I used the migration as a point in time to clean up my vault and have enjoyed a completely clean password manager ever since. Bitwarden has slowly been adding the features I wanted when I had left Lastpass - and at this point it just works for my workflow.
While I understand subscriptions can add value, I don't understand the forced model. Clearly 1Password has a subset of customers that don't want what they're forcing on customers. Maybe it's that they're positioning to sell the company and moving to 100% subscription boosts the bottom line valuation. But in the majority of cases the customer is not always delighted by this move. Sales organizations love to claim "it's what the customer wants", "it's more affordable", among other half-truths - when the reality is it's a much more consistent revenue stream that disconnects customers voting with dollars from continual enhancement of the product such that the customer is incented to upgrade.
You... just saved me many hours. My 2021 goal is to migrate from 1Password to Bitwarden. I’ve been putting it off as I still have half a year of my subscription. But that does make it easier.
I got Windows going on a throwaway VM and installed the 1P client. Took 30 mins to an hour but surely a better option than recreating your vault by hand
It's not going away any time soon, the app is still available for MacOS and the browser extensions work just fine. Eventually they will stop supporting them but that'll just mean at some point in the future a MacOS/firefox/chrome update will break the existing app and they won't fix it. That might be 2 months from now or it might be 2+ years.
Sure, if you longer have a way to use an older version of MacOS. Not a good idea to leave your sole copy on a machine you don't have full control over.
This is the reason I bought my first license of 1Password many years ago. I thought the trust model of one vendor supplying the password manager but not the storage (I was using DropBox sync too at the time) was a great way to ensure that my data is safe.
Same story for me. I switched to the KeePassXC ecosystem eventually as a result — it's open source, has compatible clients for just about everything, and has one-click import for 1Password vaults.
I've been using KeePass (KeePassXC and similar) for years. macOS, Windows and Android. I've also had 1Password for a shared business vault for years as well.
I much prefer KeePassXC. I find KeepassXC substantially easier to use than 1Password on macOS. I strongly dislike 1Password's UX. It feels very cumbersome to use.
I have a shared family KeePass database as well. Works great.
I'm perfectly happy with paying a subscription, and think $4.99/month for 5 people is affordable.
What I'm not happy with is the possibility of password access being limited or sync breaking if 1Password servers go down. At least with Dropbox (iCloud, wifi) sync, I have full control over the local vault file.
Ultimately, it might be mostly about ownership and choice for me.
If the servers go down you'll never lose access to anything. You would lose sync while the servers were down but you would be able to access everything you already had on every device.
This makes losing local vault support an even bigger cause for alarm:
> After you remove a family member’s account, they can’t sign in to 1Password, which means:
> They lose all the items in their Private vault. Because the items weren’t shared with any other family members, no one will be able to access them.
Imagine: the access credentials of the administrator gets compromised, and the entire's family's digital life, stored on 1Password, gets wiped by the malicious actor.
The attack surface would be limited if instead, the removed user's license turns into a read-only one, like how 1Password currently deals with people using local vaults, and are not on a subscription.
I’m glad you find it affordable but these nickle and dime things add up. Especially when the product fits into $0 software so $4.99 is infinitely higher than $0.
I feel like these small, “affordable,” services are just whittling away the Unix philosophy of do one small thing well. Layering on unnecessary crap just to charge a fee eventually comes home to roost.
Also, passwords is a lifetime need. So 80 years x 12 months = $4,790.4 and that seems like a cost that should be reduced out of one’s lifetime.
Do I want to go to Tahiti once in my life, or pay for password convenience?
Again, glad you’re happy but I don’t want to live in a world where I pay $5/month for commercials versions that crowd out what should be community, OSS tools. I love curl and it’s awesome, but don’t want to pay $5/month/forever.
We forget that taxes are inefficient and should be minimized where possible. A login tax for all eternity sucks.
I think about sustainability quite a bit and if everyone who needs password management spends what you’re comfortable spending, that’s a waste I think. And when tech stops making things cheaper and faster it’s a bit sad.
> We forget that taxes are inefficient and should be minimized where possible. A login tax for all eternity sucks.
Yes, but like in many other cases, an efficient market would mean that they will always need to be better in most aspects than whatever free, open source, or simply lower cost competitor pops up.
Unless they decide to prevent people from exporting their passwords, of course — and that's a big enough dealbreaker for me that I'd move away anyway, not caring how fancy or advanced the rest of their UX is.
That comparison would be $2.99 for 1Password. It is the family plan that costs $4.99, and Bitwarden's family plan is not $0. It also assumes you don't want the features in the paid version of Bitwarden, so it's not an apples-to-apples comparison. 1Password doesn't offer a free reduced-feature version, true.
Why not? I had this setup for years before switching to bitwarden_rs.
You have apps on every device to access your password database and do autofill. I stored everything in KeePass, recovery keys, TOTP seeds, sensitive documents and notes. I get the password sharing thing for families but for a single user they have the same featureset. The only thing missing is browser access but even though I now have browser access to Bitwarden I think I’ve used it like twice. I think I used Keyweb maybe once.
It's not the same thing because the whole argument being made is in the context of 1Password and its target audience: normal users. That's your mum and dad and other very likely non-techie people.
Let's Encrypt SSL/TLS certificates are free, as is Apache/Nginx/Caddy to reverse proxy Nextcloud or any other solution (if a web based interface is needed). You might also need something like ngrok ( https://ngrok.com/ ) for publically accessing the instance if you're behind NAT and are hosting it on a homelab, or alternatively just put it on one of the VPSes that you're using, if you have any.
Personally i'm using a similar setup (a WireGuard VPN tunnel or two in there as well) on my pre-existing VPSes, so the effective costs are 0$ for me. And the file based approach is actually superior to any (possibly) dubious browser plugins in my eyes.
Recently set up something similar. DNS entry that resolves to a local ip, swag + letsencrypt reverse proxying to Nextcloud, all setup as containers and accessible anywhere over WireGuard. I'm pretty happy with it.
It does seem like an interesting and useful project, though there are also other more popular alternatives like Caddy: https://caddyserver.com/ (even though their V2 not being backwards compatible was a tad annoying)
Apart from that, just wanted to say that WireGuard is absolutely lovely! Pretty simple to set up, works well and uses way less resources than something like OpenVPN.
This reads like that notorious HN comment about it being trivially easy to roll your own Dropbox. Our time has value. Good UI has value. How much time is saved by just using a service like 1Password versus the design, setup, maintenance, and ongoing use of a system like you suggest with all those individual pieces?
I know exactly how to do it, I've tried out what has been described above.
I've got a lab for stuff I want to tinker with, but a password manager is seen as an "essential service" to me like e-mail and music. I'd much prefer to pay a bit per month and have a team of professionals deal with it if the servers go down.
If at the end of the day my home server breaks and I want to get on and watch Amazon Prime/Netflix/whatever I still can with a hosted password manager. I value my time and sanity a lot more than £2 a month.
That's a fair point! But depending on your setup, it's also possible to replicate the password database file to every single device of yours on the network.
Currently doing just that, if any of my servers go down, i can still access all of my passwords on my desktop, on my laptop, on my tablet, on my phone or on my backup servers. Of course, provided that i have KeePass or a mobile app installed and know the master password.
Oh and I do manual backups to SD cards just to be sure every month. I'm not sure how I'd do that with a cloud service where in a sense their entire company (and my network connection to it) is a single point of failure. If my internet connection goes down, how would I log in to my selfhosted software in my homelab over LAN, without being able to access the passwords?
> so getting to know how to do things by yourself is a waste of time?
Potentially. Are you looking to make a prototype, or are you trying to go to prod with mission critical data?
Most people here could trivially roll a prototype grade password manager in pretty limited time. Getting something hardened and reliable is a different story.
I was just thinking the exact same thing. For technical and especially non-technical folk, getting a full nextcloud host set up and working is going to take significantly more time than a simple login into 1Password, where it just works.
Box.net supports webdav if that's what you want. I'm not aware of any other big name cloud storage providers that offer support for standard protocols. It's available for free accounts, too. This does mean the files aren't encrypted, however if your vault is encrypted that may not matter to you.
For a moment I felt that perhaps I should add clarification about how I'm not trying to dismiss the cloud solutions (as in the notorious Dropbox comment), but instead am attempting to provide one of the many libre setups to answer the parent question, but in the end didn't get around to it.
My time probably isn't as valuable as that of the many people here (about 5x less earnings on average in Latvia when compared to places like US), therefore it definitely makes sense for me to upskill myself in any way possible, especially if I get usable software out of it.
But if you take the container based approach, there is almost no administration to be done:
First, install Docker: https://docs.docker.com/engine/install/ubuntu/#installation-methods (about 10 minutes, varies by distro)
Personally, i use Docker Swarm, but that's just a few more init commands and Docker Compose works as well: https://docs.docker.com/compose/install/ (about 5 minutes)
Then, set up something like Caddy for a reverse proxy: https://hub.docker.com/_/caddy (probably 20 minutes)
And then, set up Nextcloud: https://hub.docker.com/_/nextcloud (probably 20 minutes)
Lastly, install KeePass from the previously mentioned links and put the password DB in the synced folder (probably 10 minutes)
Ngrok, DNS challenges etc. might be necessary depending on the setup, but are not usually required for most regular VPSes.
Backups and updates should also be taken care of, but full VPS backups are mostly standard and you can just bump the container tag every month.
As for the UI, i agree in principle, but not in this case. KeePass has good UI and I'd argue that you don't need a team of UI and UX developers to keep track of some usernames and passwords (and maybe certificate files).
Furthermore, I'd argue that most of the cloud offerings are actually problematic because not all of them let you download the data as files. In contrast, KeePass works with files (much like SQLite) and therefore, if you'd prefer to use SD cards or Samba or NFS or whatever instead of VPSes to somewhat decrease the attack surface, or simply use tools that you know, then you can do that. Want Syncthing instead of Nextcloud? Go ahead!
I'm putting emphasis on this because the line of thinking that we need web SaaS platforms for everything is dangerous - it makes you think that the problem is more complicated than it actually is. Whereas in reality some people probably get away with using password protected spreadsheets (don't do this). The problem is complicated only from a security perspective. That's it.
The cloud solutions excel at convenience and things like browser plugins and it's good that they're offering options for the less technically inclined folk, but they're far from the only option.
Except, you didn't need to roll your own. 1PW used to support Dropbox - it's how I still use it.
And specifically you only need the DB free tier to store a 1PW vault, so the only cost was paying for the 1PW client (which I am more than happy to pay for on major version updates, as long as it is not a subscription).
1PW removed functionality that existed, with goal (or at the very least the effect) of locking users into their own cloud platform with a new monthly bill.
The real question here is how much time it takes to setup this experience and how much time it takes to maintain. You could argue that the true cost is the labor cost of implementation and maintenance at your current pay rate.
I'd vastly prefer to be able to do 'bring your own storage' but for that price I don't really see a problem with that being a "you can do that, but you pay the same subscription price anyway" feature.
Affordability is a mirage- $5 per month and $60 per year wont break a bank but its a huge amount to justify other geographies where money transactions are NOT in $$
When you have a 1Password.com subscription, you are not "working in the cloud" like with Google Docs or something.
Your vault is local, and synced to/from the cloud.
Basically just like Dropbox. If your internet is down and you cannot reach Dropbox, all files synced to your computer are still there, on your computer. It's just that any changes you make locally or changes made on dropbox.com cannot be synced until your connection is back.
I agree, I switched about a year or two ago to subscription and I'm quite happy with it. There are some apps/platforms that I believe /should/ be subscriptions and my password manager is absolutely one of those. 1Password has continually added new/better features year after year and the price is tiny compared to the value I get (and then subsequently provide to people in my 'family'). The UI is the best I've seen in a password manager and while design doesn't necessarily affect the ability for a PW manager to do it's core job, I prefer looking at pretty apps. Almost every time I use 1Password I leave with a smile/good-feeling.
I think the issue people have is YetAnotherCompany:tm: forcing you into their subscription walled garden.
And also from a user security standpoint, i don't think we can keep going on making enhancements to user security good practice habits if we gate keep good password habits behind paywalls.
I'll be an outlier with you. I install the app where every I am, authenticate, and BAM, I have my passwords. So easy even a caveman could do it. I've been a happy subscriber for years.
Same. I share my passwords with my wife and sync them across devices. I also have a license for an older standalone app. I don’t feel cheated. I wanted to be able to share some passwords with other people.
I saw something mentioned about self-hosted vaults. That is something I might consider for my family.
I advocated for the use of 1pass at work precisely because we can share strong passwords with the team. Otherwise, people would just use the same, well-known weak passwords for everything, including business critical ones like domain registrar or Gsuite admin or the root AWS account.
I am not as happy about having another Electron app running on my local box. I hope they spent time locking things down. On the other hand, if it means my wife (on Windows) gets feature parity with my macOS client, that would be good. Even better if the Linux desktop gets feature parity and no longer have to rely on the web or browser plugin.
It saves me so much time compared to how I used to have to do it — pull out phone, unlock, open Authy, wait forever for it to load, type in code, put phone away…
It’s the little things that all add up. I’m very happy with 1Password — been using it for 10 years, and happy to subscribe, considering it’s probably my most-used utility app.
I am cognizant of this risk, and assume it, because security is always a spectrum between Secure and Convenient. If I had to pull out my phone every time I wanted to use 2FA, I for sure would not be so liberal to turn it on for all the "low value" properties the way I do now
I have never even _heard_ of someone having their 1P master password compromised and the vault(s) exfiltrated (although I grant you it could be just because the NSA doesn't write blog posts about their pwn2own victories)
It's my recollection AgileBits is also running (that is: currently) a CTF with a publicly exposed vault, so folks can test the resilience against attack for themselves
> I am cognizant of this risk, and assume it, because security is always a spectrum between Secure and Convenient.
Absolutely. But also, in such setup, the security benefit of 2FA/OTP codes are negligible at best since there are no conditions under which only one factor could be compromised without also having the other factor leaked (assuming you're using unique passwords for each identity, which is the entire point of a password manager).
However, I suppose it could be used for bypassing the inconvenience of mandated 2FA scenarios (to the dismay of your company's security team).
> But also, in such setup, the security benefit of 2FA/OTP codes are negligible at best since there are no conditions under which only one factor could be compromised without also having the other factor leaked (assuming you're using unique passwords for each identity, which is the entire point of a password manager).
Phishing and good ole fashioned human error are two methods by which a password can be leaked without exposing the 2FA token.
I previously thought that we were just having a difference of risk tolerance, but if you think some rando can _phish_ a TOTP secret, we are not even in the same universe of risk mitigation
> Hello, dear sir, this is the USA IRS and we are going to send the FBI because your TOTP code is expired and are going to put you in jail if you don... hello? hello?!
For passive phishing (e.g. setting up an identical website to the real one) stealing a valid TOTP token is trivial and such campaigns have already been spotted in the wild [1]
> if you think some rando can _phish_ a TOTP secret
Given the context this discussion is about (someone with a 1Password vault, storing unique passwords and TOTP secrets for each account they have) do you see any scenario in which a user gets his password stolen but not the token (or the OTP secret seed altogether)?
> Hello, dear sir, this is the USA IRS
If an attacker via a phone call is able to get the victim to (a) unlock their 1Password vault, (b) spell out their password for account X, what makes you think they couldn't get them to also (c) open their 2FA app and spell out their TOTP token?
> I previously thought that we were just having a difference of risk tolerance
The point I was making is that there are no security advantages to setting up a time-based OTP as a second factor for authentication if the secret seed is going to be stored in the same vault where the passwords are: might as well just forego this TOTP setup altogether and save the extra hassle. Or get a hardware second-factor (TPM, Google Titan, Yubikey, ...)
> there are no conditions under which only one factor could be compromised without also having the other factor leaked
Man in the middle attack,
Phishing attack,
Over the shoulder attack,
Brute force attack,
Keylogger,
Http (not https) traffic sniffing,
'Breech' of the site and realisation they host their passwords in clear text on an unsecured db online.
Then there is human error; typing password into wrong site, giving your password to the tech support cold caller, telling someone your supersecret password ...
> Man in the middle attack
> Http (not https) traffic sniffing
If you can see the password, you can also see the time-based OTP, and you can use those to gain access.
> Phishing attack
> Over the shoulder attack
If you can convince someone to provide you their password, it's highly likely you'll also be able to convince them to also provide you their time-based OTP.
> Brute force attack
A successful brute-force attack on the vault (unlikely) means you've lost both your password and your OTP secret. A sucessful brute-force attack against a remote account using a safe password (re: password managers) is very unlikely!
> 'Breech' of the site and realisation they host their passwords in clear text on an unsecured db online
The password and the OTP secret themselves have no value (given that you're using unique passwords for each account). If the attacker has breached the service back-end then it's gameover anyways, regardless of 2FA for user accounts.
If my password vault is compromised it's game over anyway. There's enough access in there to remove the 2FA on all of my accounts even if you didn't have the codes. There's no way I'm giving up breakglass access and risking locking myself out of my accounts permanently or while I'm on road if I lose my phone.
The point of using 2FA for me is to protect me against my password being compromised since it's a long_lived access key.
I believe there's barely no benefit to setting up a TOTP 2FA for those accounts if you're going to store the backup codes/token seed along with the password in the same vault.
> If my password vault is compromised it's game over anyway.
There are ways you could make a vault compromise not mean a complete/irreversible takeover, but that would either give up breakglass access as you say or add complexity and reduce availability.
> The point of using 2FA for me is to protect me against my password being compromised since it's a long_lived access key.
In which situations on your setup would a unique password compromise not imply there's also been a TOTP token/seed compromise?
I agree with all of your points - I'm okay with their sub model, I'm okay with Electron and it's the first time I was able to convince family members to use a password manager (because it works so well)
I think removing the self-managed data store feature makes sense even if not everyone likes it. It removes a source of architectural complexity, and most users aren't looking for local storage anyway.
Personally, the problem of managing reliable persistence of my password database just isn't something I want to spend time on, and the incremental difference in security posture is uninteresting to me given that it's encrypted at rest anyway. In terms of waking hours spent worrying about the security of my household IT, the security and persistence of sensitive documents (mainly vs. ransomware) is a bigger problem and I like that my passwords aren't tied up in that mess.
I'm with you. It's seemless, it works (on everyplatform) and it's easy to use.
At the end of the day if you want a password vault that is sync'd across devices, you're trusting someone...somewhere. Be that 1password, dropbox, or even that Linode you manually rsync your data to. You've got to decide what is the biggest risk for your own personal use cases.
For me, I'd rather store my sensitive data with a company that has demonstrated a repeated push to keep my data as secure as possible, even from itself. It's their core business, all they focus on.
Agreed - software like this doesn't exist in a vacuum of frozen dependencies (at least not until Urbit takes over). Subscription models make sense for stuff that requires updates over time to keep it working. Their stuff is reasonably priced and the product has been really good for years (imo).
I suppose they could do something like JetBrains where you get updates while subscribed, but realistically login breaks for users would be a mess to support and a standalone text editor is a different service.
This move makes sense to me given their market. Those that want to run a vault can use an alternative that's more of a hassle to deal with.
I'd only recommend LastPass if you're a fan of LogMeIn, Ltd. and only being able to see your passwords either on Desktop or Mobile (on the free version).
I mean you can only view your passwords on mobile, OR you can only view your passwords on desktop. On the free version, you can't be signed into both desktop and mobile at the same time, and you can only switch 3 times.
They've had security bugs in their browser extension before, but it is almost required to use it - the webapp works horribly without it. My least-used browser gets that extension, so it isn't running most of the time, at least. And with it, the UI is still terrible. The app is just awkward and poorly done.
The one good thing I can say is the user/group model is reasonably implemented.
I just went through all the trouble of setting up Bitwarden, the built-in 2fa from 1P doesn't seem to transfer over, or doesn't work with the chrome extension at least.
Hi. I'm a feature developer for 1Password, and I want to clarify a few things. First of all, our decision to built the macOS app in Electron was absolutely not driven by VC money. For the past few years, we've been working on consolidating 1Password's business logic into a single Rust-powered core that could be shared across all our apps. This has many advantages: feature consistency across platforms, faster development cycles, and better security. When building the front-end for the desktop platforms that would take advantage of this new core, Electron suited us perfectly, since we could write our UI code once and make it consistent across Linux, Windows, and Mac. We actually did build a native Mac app initially alongside the cross-platform Electron app, but we eventually decided that having two separate versions of the macOS app (one in Electron, one in SwiftUI) would cause a lot of needless development churn and hassle for both customers and our support team.
I can understand your frustration about Electron, but I hope you find my explanation reasonable. Please stop spreading misinformation.
>Electron suited us perfectly, since we could write our UI code once and make it consistent across Linux, Windows, and Mac.
This is the source of your mistake. Users don't desire to have the same UI across different OS environments, it's only an app's developers that care about that. Cross-platform UIs are inarguably a worse user experience than UIs tailored to the conventions and designs of each OS.
A Mac app that doesn't actually feel or behave like a Mac app is not a good Mac app. The same is true with tvOS apps like YouTube and Prime Video that don't actually feel or act like good tvOS apps.
> Users don't desire to have the same UI across different OS environments
Um, speak for yourself. I personally don't like having the docs showcase completely different UIs to the one I'm using. I also like having an app i can run on Linux, which has been happening a lot more since Electron became a thing (no sane company wants to write apps in GTK, and much as Qt is a great toolkit it requires expertise most SaaS vendors don't have).
You're speaking as if it's fait accompli that 1password made a mistake picking electron. It is not, and I am fairly certain they did not.
Anecdote, but, my workstation is Linux, my work laptop is macOS, my personal computer is Windows where I run Linux VMs. I run 1Password across all these operating systems. Having a consistent interface is nice and it means I don't have to relearn the UI three times.
There's an argument to be made the other way around:
Maybe if you choose to use multiple platforms you should just deal with the multiple approaches to UI? Why should the single platform citizens suffer from a UI that's inconsistent with the rest of the platform?
To stretch it to an absurd case:
Imagine Slack decided that the shortcut to copy text will be Ctrl+C on all platforms. And Windows users who occasionaly use a mac would rejoice because it would save them from having to think which button to press.
> Users don't desire to have the same UI across different OS environments, it's only an app's developers that care about that.
I guess we'll have to agree to disagree on that. I personally enjoy having consistent user interfaces across the apps that I use, and there are many other people that would say the same, so I would avoid making broad assumptions. From our perspective, consistent user interfaces are a win-win for both the development team and the majority of end users. That being said, I'll take your feedback into account.
This is a curious response. I would have used the same reasoning as an argument against Electron (or similar unified development systems): they are not consistent with all of the other native apps that people use.
I don't know if your reasoning is that looking like a web app means it is consistent with those apps, or that the apps look the same across platforms, but neither of those arguments are compelling to me. I chose the platform I am on because I think the interface is a good one that makes me more productive.
And I have never found an Electron app (or web app in general) that is as high quality as good native apps (on any platform). There are just so many compromises, and I am not even considering resource usage here. Everything just feels a little slip-shod.
Thank you for that well-written explanation of your concerns. Your frustrations are shared by many users in this thread, and I'll do my best to pass them forward to the rest of the dev team.
> I guess we'll have to agree to disagree on that.
This is such a bizarre claim. I know Agilebits understands Mac users.
To be brutally honest, I've heard this line from a lot of software shops after they decide tailoring their apps to the native platform is too expensive or inconvenient for them. Suddenly they all find that their users don't care about their native platform - I suspect if I went looking for the discussion from back when Adobe did this, I'd see the same phrasing.
> I guess we'll have to agree to disagree on that.
Let's be clear about this: you are the seller, we are the customer. You can't `agree to disagree` with your customers.
If you don't agree to what some your customers are telling you, then they won't be your customers, and you won't lose just these customers but also all the others who observe your behavior. It is a modified case of repeated prisoner's dilemma. If I observe that you tend to defect on other instances, I will less inclination to cooperate. In other words, your reputation will suffer.
On the consistent user interfaces, the consistency of an app with other apps on the same platform is much more important than the consistency of that app across platforms. Even if you use multiple platforms, you switch much more frequently between apps on the same platform than between different instances of one app across platforms.
I don't have super strong feelings about native v.s. cross-platform UIs, but I think I (and maybe others) think about this question from the "reverse" direction. I expect a given service / app / functionality to work the same everywhere, no matter the platform. This is true of tools I use through my terminal or tools I use in GUIs. Other approaches feel to me like they make using the product more difficult - I may not be able to help someone else on another OS use it, it may mean that an obscure platform has more bugs than a unified approach, etc. I understand why native may make sense, but I do not think it is a given.
I wholly agree with this, I choose Macs and use basically exclusively "good" Mac apps since I want everything I use to just feel right. On the occasion I use Windows or Linux, I want the UX to feel akin to what other applications on those platforms use.
Kinda a random thought, but is it at all possible to build a native 1Password app using their API [1]? I haven't read Agile Bits' ToS, but I would be interested in working on / following a Mac-centric client.
Thank you for pointing me to that thread. I'll make sure to respond there as well.
I did (incorrectly) assume that the parent was talking about Electron, so that's my bad. That being said, our decision to move away from licensing is absolutely not being driven by VC funding, so the parent comment is also spreading misinformation. We were building a subscription-based model all the way back in 2014, and we're phasing out licenses for the host of reasons that were mentioned in the original article.
In my experience the impact of VC money isn't directly seen by engineers but is rather a subtle top down shift in direction. Growth matters more, revenue matters more, existing users matter a bit less versus future users, features that impede this are removed, etc. Feature direction shifts slowly but surely.
The goal of a VC company is to either grow big or die. That's it. Risky bets at the expense of existing users are expected if current growth does not meet expectations. Worst case everyone quits the app and you go bankrupt. VCs expect that 9 time out of 10 so no big deal as long as the 10th makes it big.
But how can you justify removing the ability to have a local vault?
Why would anyone think for a second that it would be a good idea to force people to store every password for everything in their life in your cloud without an opt out?
That, even more than Electron and the subscription model (both which do bother me), is an absolutely deal breaker. I've paid for every version of 1Password since v3 in 2009, but I'm done with it now.
The original article goes into great detail as to why we're moving away from local vaults.
That being said, we are looking into gauging user interest in self-hosting. Please take a look at our survey [1] if you want to share your thoughts. Hope that helps!
I don't want self-hosted, and I definitely don't want subscription based. I, 1Password user for many years, want the local vaults!
1Password 6 is great, and I'll keep using it until it quits working on my devices, but no more after that! I used to recommend 1Password so much to people it was borderline evangelizing, but I quit recommending it once the subscription was pushed over the other options, and now that local vaults are going away I'm actively recommending against it to anyone that asks.
Guess I'll be moving to Bitwarden or Keepass myself; time to research!
The short answer is no. People often have misconceptions about Electron apps based on their experiences with a poorly written one. I've had my own fair share of bad experiences with Electron-driven apps. But the way we've utilized Electron is far different than most applications.
Our Electron app is really only a thin client over a Rust-driven backend that handles all our business logic. We only invoke Typescript when we need to render the UI; everything else goes through Rust. We even run some Swift code too, for deep integration with the operating system.
Memory is still an issue with Electron, but we're getting better at reducing the footprint. We've put a lot of work into optimizing this app, so I recommend you give it a shot; I think you'll be pleasantly surprised by how performant and responsive it is.
Hi, I didn't mention Electron in my comment, it was purely about the move to remove single time purchase and local vaults. I don't like the direction where the product is heading, therefore I want out.
Strong "do not want" for lastpass. Run far, far away.
I switched to KeePassXC a while ago due to the increasing hostility over local stores. Looks like I was right on the money.
KeePass has served me pretty well - it's not as polished, but it works absolutely everywhere due to the numerous client apps on many OSes, and it syncs normally. Toss on something like Dropsync for mobile, and it's pretty streamlined: https://play.google.com/store/apps/details?id=com.ttxapps.dr...
Damn. This is a huge mistake. I've used 1password for over a decade. I will happily buy an upgrade license. I just don't want another subscription to my credit card. This is rent seeking!
>People are said to seek rents when they try to obtain benefits for themselves through the political arena. They typically do so by getting a subsidy for a good they produce or for being in a particular class of people, by getting a tariff on a good they produce, or by getting a special regulation that hampers their competitors.
You may not like the subscription business model, but it isn't rent seeking. Monthly payment != rent seeking.
> Rent-seeking implies extraction of uncompensated value from others without making any contribution to productivity.
I think the rent seeking comment was about removing the option for (free) Dropbox sync and only supporting the subscription-based plan. They are asking for more money for less product.
I use 1Password, and migrated over to their subscription service some time ago. A password manager seems like the best overall option at this time.
However, given they have all the password for many people, how are they not one of the biggest targets in the world? In their old Dropbox model, I understood the security model. In the service model it's moved to "Just Trust Us".
Is there anyone who can help me understand how this model is secure?
It's basically E2EE (where the encryption key is your master password + secret key, which looks similar to a guid), with the caveat being that 1password is still accessible via the browser so you do have to trust they're not compromising you by saving your secret key + master password separately (that is, unless you're auditing the login page every time you open it).
684 comments
[ 2.7 ms ] story [ 588 ms ] threadThis is also a consumer product, not enterprise.
Imagine emojis in IETF RFCs. No thanks.
They have an established reputation.
Like, imagine its only Gen X that complains about this, and they are the equally out of touch blackberry user whose device renders all the emojis in some messed up but hilarious way, then its a great way to make fun of them without saying anything and just keep bombarding them with an incommunicable internet, while the rest of us dont mind and some of us are also in on the joke.
Admittedly, there is a similar problem with words, but there are at least dictionaries for them. :>
For my personal passwords, I prefer keeping a local KeePass vault (I access over a local network drive, VPN in elsewhere).
I totally agree that primitives are some of the least important parts of choosing password managers, but what I like about KeePass is that you can use Argon2 as the password derivation function and specify your hardness factors. Because my laptop and desktop have a strong-enough CPU and I don't mind waiting 20-or-so seconds before the first unlock, I can set quite high values for this.
I used to use Enpass and never had an issue but it's not open-source and you have to pay for Mobile client.
It's honestly fantastic to see how they have adapted to password managers.
For example, if you're logging into your credit card provider from Mint.com, you have to search your card, copy the username. when you paste the result on Mint, you lose the window, and you have to re-search for your card to get the password. Very frustrating.
I've found just opening the main app to be a better solution in these cases, but it sure is annoying.
The chrome extension leaves a tiny bit to be desired, but definitely still usable:
* Not as good about determining correct sign-in URL and lots of times will send me through the auth redirect from registration
* Launching sites without mouse isn't possible (shortcut exists to open extension but can't select site to launch it using arrow keys, for instance)
* Button locations aren't consistent between search view and opening it on a site you have a password on
Definitely still the best for me though. It's frustrating, though, that I don't feel like the paid plans really give me anything useful, so I'd be paying basically just to support the product (which I'm happy to do!). It's a weird spot for sure, I feel like table-stakes for a free password product is infinite devices + usable browser extension + phone apps + password generation. But figuring out what to add on top of that is always either directed at businesses or families, or things I don't care about like 2FA or an authenticator. I want to support you, damnit!
Bitwarden run so much faster than 1password despite being a browser extension.
The CLI is great too. I pretty much use it like a cheap version of Vault to feed secret into K8S.
Though one more point that’s more than just "ease of use" is probably shared access. AFAIK Keepass has issues there while bitwarden (IIRC) supports it completely.
- conflict-less sync; with KeepassXC, I learned to live with keepass-diff, once the inevitable sync conflict happens
- no need to have entire app running, or even installed; in browser, the extension is enough. KeepassXC was a kind of annoying to launch.
- password sharing
Advantages of KeepassXC:
- can autofill http auth dialogs; bitwarden still cannot do this
- can serve as ssh agent, so synced database takes care of your ssh keys too
This was a discovery in a security review they did and choose not to change.
This was some time ago so things may have changed. But, that red flag kept me away.
I’ve gone so far as to test this.
In my opinion this is the right security model
Lastpass frequently messed up the autologin and injected a lot of ugly css/html in the forms which Bitwarden doesn't.
Also it works really well as a chrome extension with Kiwi browser on Android.
I have my OTP codes on yubikey for daily use. (works great, and breaking a yubikey is a lot harder then destroying your phone and losing all your OTP).
I had bought several versions and both the Mac and Windows editions of 1Password over time, none of which were what I would consider inexpensive for a password manager. I consider their treatment of me as a customer to have been terrible.
I wouldn't be so pissed off about it if they had just dropped the product and started a new one, but slowly turning something paid for, used regularly, and liked into something different that I didn't want at all tells me that they are absolutely not worth doing business with again. They're not trustworthy.
I convinced my wife to pick it up and we now share a bunch of stuff and she loves it. And she's low tolerance for UX issues.
The official command line tool is way too clumsy. I've tried rbw and rbw-fzf which are ok. rbw doesn't let me view all properties of an entry (attachments, notes), and rbw-fzf has issues if things have spaces in them and is limited to only passwords, not other info.
i would be still using it myself but i also wanted to login to desktop applications so ive been using keepassXC since.
keepass's auto-type feature is also a great way of autofilling passwords without having to give your browser access to your password vault
Last github update 657 days ago.
Maybe it's done.
I use it to securely store notes and important files.
In fact, if you're okay with only editing/creating password entries on your phone, you don't even need to pay for the desktop app, because you can use it in read-only mode. The Android app has no limitation to editing local vaults, and it's pretty rare for me to actually have to set up new accounts these days, so I'm fine doing it on my phone. I considered paying for 1Password X (their online offering), but it's simply not worth $45 per year for that minor convenience. I can't complain at all, because I use 1Password completely for free.
It's possible that it was hidden because I had previously signed in to my work's 1PW account, maybe, or that it's hidden too well for me to find. I don't know, and would be happy to learn either way.
https://pwsafe.info/ for Mac and iOS https://pwsafe.org/ for Windows
The underlying file format is opensource and developed by Bruce Schneier.
Subscription business models and non-native apps are hallmarks of rot by VCs. Dump them!
They just like to say that they use Rust for the backend code. Rust for the backend of the client apps, React for the UI, wrapped in Electron.
Electron apps typically don’t work for me because they don’t integrate with the rest of the system cleanly, and so once you stray off the designers’ happy path it becomes clumsy to use the app. This isn’t an esthetic or ideological argument; simply for my usage an electron app can rarely be as convenient as a native app on the Mac. Things like input integration, system service integration, selection, and responsiveness are much harder to do when you are fighting the electron abstraction, so no wonder devs leave those things out.
edit: apparently 8 will be electron-based. So... no standalone subscriptions AND they've moved from native to electron :/
This has nothing to do with VC and everything with trying to build a better product for users that is easier to work on for developers.
As a long-time 1password shill I have hit my limit and will slowly start migrating to BitWarden and iCloud Keychain.
You can create a shortcut in the iOS shortcuts app to open the Passwords area of Settings via an icon on your Home Screen. Just open the following URL in the shortcut:
prefs:root=PASSWORDS
Best tip I have for you around iCloud Keychain right there.
For anyone who doesnt use shortcuts often, what you need to do in Shortcuts is:
1. Make a ‘URL’ action to prefs:root=PASSWORDS 2. Hit the ‘+’ and make a ‘Open URL’ action from safari.
Save, add to Home Screen, and you’re done.
But that doesn’t make VS Code “shit”. It’s pretty much the shining star of Electron done right.
that is a very low bar. VS code is still slow and eats up a ton of resources. not to mention I don't trust anything from microsoft. OP said electron = bad and you should be ashamed of using it because its helping propagate it's usage when its a cancer.
Electron is a tool. It can be used well. It can be used poorly. Any tool shares the same issues. I can write a shit native app and I can write a shit Electron app.
All Electron does is lower the barrier of entry to making an app and making it work cross-platform.
VS Code is an example of Electron being "used well". I still find myself using other apps because they're more responsive. That tells me that Electron is inherently making the app experience worse, despite being used well
I understand the 'why' of electron, I am just not happy with the results at all.
Though maybe the world is better if that barrier of entry isn't lowered, I'm not sure what's better- a shitty app available everywhere or a good app available only on a couple of platforms...
Someone wants to build a 5 minute app for themselves and Electron happens to be the easiest way to do it? Go for it, there's nothing stopping them. If that app happens to be useful enough for others to use it, even better, that person just solved what could have potentially been a big deal for that user.
If the people using the app are content with the features/quality and the resources it uses, why does it matter so much, especially to a third party like armchair engineers on HN, if it was built natively, on Electron, or CrappierFrameworkThatWillEventuallyReplaceElectron?
If the app isn't usable by you (and this is a general you, not specifically directed at you), then the answer is simple: don't use it. Nobody is forcing you to use Electron or any app built with it if you don't want to.
If as a user your needs are not met, whether that's due to sluggishness from Electron, incompatibility from having a native-only solution, whathaveyou, then all you really have to do is wait. A competitor will come and take its place eventually; that's what the market is there for.
So far, it seems like VS Code is more than meeting its users' needs, but like I said above, other alternatives exist and will continue to exist, and they're all great if VS Code doesn't work for your particular use.
> If as a user your needs are not met, whether that's due to sluggishness from Electron, incompatibility from having a native-only solution, whathaveyou, then all you really have to do is wait. A competitor will come and take its place eventually; that's what the market is there for.
not the first time we've heard this argument used in different industries. I'm old enough to remember this argument about DLC's, DRMs and games being released before they are finished and get charged DLC packs to finish it. This argument falls apart when everyone starts doing it due to economic factors and complacent users/customers who blindly use what everyone else is using.
Businesses aren't stupid, if a decision were to actively lose them more customers than it'd gain, they wouldn't do it. If every single business and OSS alternative suddenly switched to Electron and you had no other choice, then maybe it's you that is wrong about the value of Electron.
But, of course, that's a ridiculous hypothetical not really grounded in reality. In the real world, plenty of alternatives exist for practically every Electron app out there so if you don't want to use it, you don't have to.
And for every one of you, there's hundreds of people that think their Electron apps are fine and appreciate that they can use the exact same interface regardless of which computer they're using.
i see you're moving the goal post
once you have a monopoly you can do whatever you want, thus why everyone keeps talking about EEE. look at what apple is doing now with photoscanning. What they are doing is inherently bad but they are able ignore everyone and go ahead with it because their "target audience" doesn't care about this kinda stuff. Doesn't mean the rest of us shouldn't actively fight against it. your argument basically boils down to let the market and customers decide for itself. Over here there are some of us trying to tell people to not support electron because of the potential consequences, and the downward trend of the web as we see it.
There's choice with password managers. But look at music. You have Deezer and Spotify. The only two free services that I'm aware of that only have Electron apps on desktop. (YT Music doesn't have an app on desktop). Spotify has exclusive content. You don't have choice when apps are the same as services. Hate the Hulu interface? You can't watch The Handmaid's Tale on Netflix. It's that kind of thing.
But now with Electron, which I don't like for the same reasons, as a friend once told me, allowed me to have some of my favorite apps running in Windows, Linux and Mac almost flawlessly with a good interface that finally the promise of Java was fully realized.
So while I would like people to follow more the Sublime Text approach, there is value in these Javascript based apps that lower the barrier of entry, provide widespread availability and are definitely easier to debug. Also sometimes I don't get to decide, since my org for instance makes it extremely convenient to stick with JetBrains stuff.
But hey, I'm the type of person that considered a Gentoo machine running Fluxbox far more useful than the very polished MacOS.
Bitwarden's desktop app is built on Electron..
Our decision to built the macOS app in Electron was absolutely not driven by VC money. For the past few years, we've been working on consolidating 1Password's business logic into a single Rust-powered core that could be shared across all our apps. This has many advantages: feature consistency across platforms, faster development cycles, and better security. When building the front-end for the desktop platforms that would take advantage of this new core, Electron suited us perfectly, since we could write our UI code once and make it consistent across Linux, Windows, and Mac. We actually did build a native Mac app initially alongside the cross-platform Electron app, but we eventually decided that having two separate versions of the macOS app (one in Electron, one in SwiftUI) would cause a lot of needless development churn and hassle for both customers and our support team.
I can understand your frustration about Electron, but I hope you find my explanation reasonable. Please stop spreading misinformation.
I can absolutely attest to that with a relatively underpowered computer (4 gb of RAM). I can barely use 2 electron apps after which my computer grinds to a crawl (I’m running VSCode and Slack mostly). I have stopped using the discord desktop app and exclusively use the website now.
That AgileBits has been doing everything it can to force people to the subscription model and that this push to subscriptions very coincidentally lines up with two rounds of VC investment for over $300M over the past couple of years? No, that is not misinformation.
It may have been easier for the dev team to use Electron as their cross-platform toolkit, it is not easier for the users to put up with the attendant bloat and reduced performance.
The ones who should stop spreading misinformation regarding the forced subscription all seem to be working for AgileBits.
There's a reason people prefer one over the others. You can't have one front-end for all these different platforms. Well, you can, but then it's a compromise for at least 2 out of these 3 platforms.
Even Microsoft has "Office 365 for Mac".
That doesn't make the macOS experience better, it makes it worse.
if an app has ongoing development that you benefit from, it seems entirely fair to pay a subscription. the fair alternative is a one time payment for a lifetime license with few patches priced in. I would probably prefer the latter for something like a word processor, but would you really want to use the same version of a security-critical program like a password manager for the rest of your life? if not, how do you expect them to fund development/maintenance indefinitely?
That last bit I don't believe applies to 1Password, because there are certain things you can't do without some kind of centralization, and the article makes that case.
...but look at something like Adobe CC, what exactly does moving from a purchase to a subscription benefit me? And let's not forget about the more subtle effects, like losing the right of first sale, silent T&C changes, mandatory updates, etc - things that are only to the vendor's benefit.
Trust that the company which provides something you need is far more likely to continue to be around. Suppose you tell your employer that you're taking a 1-week vacation. How does it benefit them for you to do that?
It keeps the vendor financially healthy, stable and willing to keep developing the stuff you use.
Would you want to dedicate your work into a product for meagre & sporadic standalone payments pressuring you to endlessly churn out marketable feature upgrades with little time for maintenance work just to barely make ends meet? No? Then why on earth do you expect other software vendors to do that?
Even Bitwarden pushes subscriptions.
I'd love to see how many developers who complain on HN about subscriptions actually make a living primarily from selling standalone software to consumers.
This model is simply more lucrative and strips customers of a number of their rights which are inconvenient for corporations.
Agreed. Though, this latest development – the move to Electron – is a negative for me, so it leaves a part of me wondering what kind of development I have been paying for. I imagine I am not alone with such a sense of disappointment.
My take on the hatred boils down to these things:
Utility type applications built as a service offer an inexpensive purchase of some kind, or are AD driven, etc... Then, features are changed, roadblocks added, user experience degraded to create problems that subscriptions pay to remedy, often poorly.
Noisy subscriptions. It's not enough to send a few bucks a month. ADS, various pitches, in app sales happening, all contribute to what might otherwise be a simple, worthy experience and solution.
It can be hard to cancel. -->if this happens to someone even once, the hate can be visceral afterword. Everyone else, no matter how well they do business is impacted to a degree.
Subscription apps / services going away on short notice. What were people paying for?
I don't _want_ the ongoing development. Photoshop from 5 years ago is perfectly fine for me. Same with Lightroom, etc. I mean, I've only paid Apple _once_ for Logic Pro and have been getting upgrade after upgrade for no cost -- a nice bonus, but I'd be perfectly happy if logic's code had been set in stone at the moment of purchase, too.
The consumer-friendly option is to let the consumer decide if they want upgrades. Or for a security-focused app like 1password I'd have believed something like "we don't want to be responsible for security problems if you decide not to upgrade, thus you must buy a yearly license" but that wasn't the message at all.
Why did 97% buy the subscription? Because they hid the other version in a locked filing cabinet in a basement with a broken staircase.
The old business model works but you have to keep innovating and diversify your product line. Microsoft was the best example with things like Encarta, Age of Empires and other tools like Project.
This new trend of doing these apps once, with far easier programming languages in a connected environment with plenty of docs, crash report data and things like stack overflow really makes it look that we are talking about cheap people trying to make a quick profit not unlike those free to play games.
I've been using 1Password since 2008 and I'll be doing the same thing. I have tolerated the UI regressions and even subscription with version 7, but Electron is just unacceptable for what was once an amazing Mac app that put Apple's apps to shame.
I got rid of two of them — Evernote for exactly the same reason.
1pwd going the Electron route would have put me close, but not over the edge — but the fact that they seem to have willy-nilly removed local vaults does.
These days it sometimes feels like one has to write all essential software oneself. Or go back to DOS and plain text files.
They have been talking about this for years. It was not done willy-nilly. There are limits to local vaults.
They're a business, and 97% of their users were already on the subscription model. If you were running a business, and 97% of your users had abandoned a feature that was a headache for you to maintain, would you stubbornly keep wasting time and money on it?
Bitwarden is right there waiting for you.
The only wish I had over the years(and I would have gladly paid for an additional license): a linux client, even CLI would have been fine. I'm not sure which year they started, but what they pushed instead was the announcement of online sync and other things I did not care about, at some point it became hard to even find the regular version on their website.
This was when I slowly started moving to alternatives. With the move to electron and this anouncement here I'm happy that I moved away a few years ago and their clear signal that I am not the kind of customer they have any interest in anymore.
Can you go more into how non-native apps are a "hallmarks of rot by VCs"?
I hate them too, but my impulse is to blame MBA thinking (build once, less investment, who cares if it sucks) than VCs specifically.
The costs of developing and maintaining software are recurring -- especially for security-critical software. Subscription business models align incentives towards ongoing maintenance.
Whom would you rely on to handle something that matters to you:
A. Someone who refuses to eat until they start collapsing from hunger?
B. Someone who eats regular meals?
I recently visited my friend from our programming club who saved these letters and was reminded a couple people wrote additional angry letters years after paying for the shareware. They demanded support in return for their one payment. (Of course, not only had I moved on to other projects, but I had long sold the type of computer the shareware was created for!)
So I learned early on that people unreasonably expect support for no additional cost. Or they believe the amount they paid is for support in the future, not work done in the past. It doesn't work that way economically. A constant flow of additional money has to come in the door to pay a team to do the actual support.
AFAICT, the only feasible models for supported software seem to be subscription, microtransaction or advertising. Any one-time-up-front price means it's abandonware. Which is fine for some types of software, of course, but probably not as often as users expect support.
One could argue that.... but one would be silly to do so.
Why does a password manager need a subscription? My password should never touch a 3rd party’s server, I don’t need extra features, I don’t need a login, I don’t need long-term or even short-term support.
What ongoing development does a password manager have? Is it that buggy from the get-go to need constant updates?
It does not, that is why there is KeePassXC and other alternatives.
I shutter to think about just trying to keep the status quo across all those platforms, devices, browser extensions. How often do we have new versions of iOS or macOS? What about Windows, Android, Linux, Chrome OS?
I can think of a TON of work without adding a single feature.
And the fact that we need to constantly change stuff just for the sake of change is the problem.
To add to this: I’m perfectly happy to pay a premium price for software when I need a new version. I did this with Photoshop for years, $399 per copy was perfectly fine for me because I spent that money every 3 or 4 years.
But you take all those platforms and all those extensions and the result is maintenance by itself is constant work. I'm not talking about change for the sake of change. I'm talking about the work just to keep the features that you have.
I have personal projects I'm working on where it feels like all I have time for is just keeping up with security updates, Ubuntu versions, DB version upgrades. Work projects are even worse with SOC2 requirements and the endless stream of CVEs.
There's no way a password manager can do nothing for 3-4 years ignoring security vulnerabilities in their dependencies that need to be patched.
It comes down to what value it provides to me for what I need it to do, which is store and retrieve passwords for me, and sync via wlan. That’s it. Why should I continually pay for Android, Ubuntu or Windows development when I don’t use their app on either of these platforms?
And additionally, as a consumer it’s not my responsibility to find a way for a company to fund its product. Saying “development goes on even without you upgrading, so you have to pay a subscription to support that” is kind of a weird argument, isn’t it. Imagine if you had to pay a subscription for using a car because next year a new model will require development and therefore you need to pay for it.
However, in the case of 1Password it's not just about being a password manager; it's also about syncing passwords between devices, staying on top of (sometimes rapidly!) changing standards between devices and browser extensions, and being aware of the evolving landscape of best security practices.
Way too often, automatic upgrades silently break my existing software, take away functionality or introduce new bugs.
Anyway thanks for showing me KeePassXC, looks like something I’ll be very interested in
This worked perfectly fine until they “fixed” it by removing Dropbox support, and now are apparently removing iCloud sync too
A better solution honestly is just to accept some percentage of people will be little assholes but hopefully, as you remembered before your friend brought it up, that most people are gracious and kind. Focus on those people.
If I buy a piece of software, it's not unreasonable to expect it to work for some period of time after the purchase. This is especially true on the Windows side, where Microsoft has gone to great lengths to keep old APIs around and support most (but not all) old software within reason. I have engineering software programs that are a decade old that still run fine on my Windows 10 machine.
macOS has been less shy about deprecating old APIs and forcing software updates. I probably spend $500-1000 every year just upgrading a certain few software packages that charge for a new version every time a new macOS comes out, and I hate it. I don't mind paying for new versions of software, but it's becoming saddening to watch all of my macOS software rapidly decay away with each macOS upgrade unless I buy the newest version.
"it works" and "the developer gives me support" are two different things. In this case, I'm sure the shareware he wrote still "worked," but clearly they thought they were entitled to perpetual updates or the ability to chat to the developer any time they like.
As far as I'm concerned, the SLA of $10 shareware I volunteered to pay for is "whatever the developer is willing and able to provide." It's $10. ¯\_(ツ)_/¯
Fwiw, 1Password isn't nuking 1P7 or existing local vaults. Those users are free to keep using v7 for as long as Apple or Microsoft allow the app to be installed on the OS. (And I do agree, macOS and iOS are both quite abrupt about cutting off support and I commend Windows for going to great lengths to avoid it)
And let's not forget that you're basically running a completely separate browser that can't re-use any memory from the other 5 separate browsers (=Electron apps) you need to run for work all day.
I think a subscription business model is the only honest way to sell software that will require ongoing support. If you're comfortable with a snapshot w/o updates, then by all means buy once, but I think coming to terms with the demands of ongoing support also means coming to terms with continuing to support the product in some way.
That said, I wish there were more variations in the way to pay - a long term license with a high upfront fee and a low monthly, an immediate access option with a high montly and no up-front fee, etc.
Done.
It seems like you'd be happier with a community product that has less support, but is available for free - and thankfully you have that option.
BTW, I think they do have an option that you pay for 3 years upfront. At least, that was one of the options they mentioned when I complained about the lack of the option to buy a license. To me that did not seem an acceptable solution because you pay upfront and still have all the drawbacks of the subscription model such as being dependent on the trustworthiness of a quite obviously untrustworthy company. Add to that the removal of local vault option, and it becomes even less acceptable.
I know that it's very common for subscription models to coincide with forced upgrades (as this one does), but that seems like a choice on the part of the company as opposed to something inherent to the revenue model. I'd be quite happy to pay a developer to continue to maintain an older version of their software.
Like you pointed out, I think a fee structure where you pay for major updates and otherwise pay a maintenance / hosting subscription fee makes the most sense.
I think that you see open source projects that struggle along all of the time because their developers cannot afford to work on them enough. Not every project, but enough of them. I try to support projects like that too.
Over the past few years, we've been working on consolidating 1Password's business logic into a single Rust-powered core that could be shared across all our apps. This has many advantages: feature consistency across platforms, faster development cycles, and better security. When building the front-end for the desktop platforms that would take advantage of this new core, Electron suited us perfectly, since we could write our UI code once and make it consistent across Linux, Windows, and Mac. We actually did build a native Mac app initially alongside the cross-platform Electron app, but we eventually decided that having two separate versions of the macOS app (one in Electron, one in SwiftUI) would cause a lot of needless development churn and hassle for both customers and our support team.
I can understand your frustrations about Electron and our subscription-based model, but I hope you find my explanation reasonable. Please stop spreading misinformation.
That's worse, not better.
At least being forced to by investors makes sense. The current direction of travel being voluntary means you've just got a bad nose for building security.
Could you elaborate on this?
What's your experience building security systems? Do you have a LinkedIn profile or a CV we could review?
Can you quantify the "needless development churn and hassle for both customers and our support team" in some way? Presumably, 1Password 7 and its ancestors used native macOS APIs, which meant some degree of that given you had to do something different on Windows and/or Linux. I don't know what your support team has had to endure, but as a long-time sample size of 1, I've been incredibly satisfied with the way you've designed and engineered the macOS application (and the iOS app too!) to date; I'd be hopeful that whatever tradeoffs y'all will be making moving to Electron, the "native" feel of the macOS client wouldn't be sacrificed. Is there anything you can speak to there that I should prepare for with 1Password 8?
Sure, happy to elaborate on that! Since we were rebuilding our app from the ground up, it was a significant slow-down on development to create a user interface for both Electron and SwiftUI, requiring two separate teams of platform developers for every feature we needed to implement. There were also concerns by the documentation and support teams that we would need two separate sets of instructions for many common tasks, due to small differences in layout and look between the applications. Eventually, we had to make the tough decision to focus on a single common framework for desktop. This will allow us to ship features across every single platform far quicker than we could before.
> I'd be hopeful that whatever tradeoffs y'all will be making moving to Electron, the "native" feel of the macOS client wouldn't be sacrificed.
We've tried our very best to keep the experience the same so that the transition from 7 to 8 is smooth, and from my point of view 1Password 8 feels right at home on macOS - I especially love our new translucent sidebar. That being said, this is still in an early access stage, so there are bound to be hiccups and UI issues that need to be resolved. Please let us know if you run into any problems or have suggestions on how we can improve. And thank you for being a long-time user!
So your margins are more important than your users’ native experiences. Got it.
I'm sorry for not being more clear earlier as to why we couldn't support two separate teams for the same platform. Hopefully this clears up any confusion.
You take money to provide software. But then you become lazy and greedy and want 1 size fits all. End result is your users having clunky, high latency experience.
Unfortunately, it’s normal in software development for multiple platforms to increase development complexity when feature and UX parity is prioritized.
Absolutely nothing about any decision AgileBits has made in the last 4 years has had anything to do with what customers (that's us, the people that used to give you money) want, and everything to do with nickle and diming the suckers dry.
UI consistency between different operating systems is NOT a user-focussed feature. When I'm on a Mac, I want my apps to behave like a Mac app. When I'm on Linux, I want my apps to behave like a Linux app. If you _actually_ believed that all apps should look and behave the same on any OS, why does the Android version look and behave nothing like the Mac app?
You've removed features with every major release, and this is just smashing the final nail into 1Password's coffin. You've ruined what used to be the best password manager on any platform.
Okay, I have a suggestion: drop Electron and keep supporting the native app you have.
Yes, because the implementation decision has implications for both performance and UX. I’ve used 1Password since version 3 (2013!) and gotten friends and family to do the same, but I think I’m done when 7 stops working.
> What gives me pause is how I write regularly asking for separate vaults for trivial passwords and passwords that could lead to financial ruin.
Just to clarify, what solution are you asking for? Do you want a local vault option to store sensitive passwords? Or something else?
The hassle of doing what your users are paying you to do? Any child can hack a UI together in HTML but there's a reason no one (usually) pays for that.
SaaS is familiar to consumers and ultimately a nicer business model for most products. If you support SaaS for new customers, maintaining the old product / pricing model indefinitely eventually stops making sense. At some point you have to make a move like this.
It is probably particularly timely to do this because Lastpass recently changed their pricing model (whether deliberately aligned or not). It's no longer possible to use the free plan of Lastpass and use it on both desktop and mobile: you have to pick one or the other. For many use cases this is effectively a requirement to use the paid plan. So now 1password has the opportunity to push legacy users to a paid monthly subscription knowing that some portion who may have switched to Lastpass to avoid a monthly fee now won't be able to do so, and will probably just pay the monthly fee to 1password instead.
Not trying to change your usage or habits, just wanted to clarify.
[1]: https://www.youneedabudget.com/security/#direct-import
It does honestly strike me as the best approach given the constraints, but here in Canada almost none of my banks are supported with OAuth flow last time I checked so giving the 3rd party providers my credentials and having them log into the bank both violates the TOS of my bank and is also far less secure than I'm comfortable with. Storing my financial details in YNAB / their partners is one thing, storing credentials that can be used to actually move or spend my money is another.
It's honestly not a huge deal for me personally. Entering the transactions manually is a good habit as I can see the balances update and mobile app is easy to use right on the spot.
Check out Chase's privacy policy as an example:
https://www.chase.com/digital/resources/privacy-security/pri...
A number of information sharing activities cannot be limited. This is typical of any bank or financial institution. Your bank has its own vendors, many of them are themselves SaaS and cloud hosted!
Even large, sophisticated banks can be hacked:
https://www.nytimes.com/2019/07/30/business/bank-hacks-capit...
My point isn't to say "Why care at all? Just open the floodgates!" Instead, my point here is that trust and security in our society is only as good as the people and institutions that back them up. We don't use bank vault doors for our front doors just because we have the knowledge that anyone with simple tools can defeat a home lock.
Therefore, I think that the choice of more inconvenient solutions made just to avoid some nebulous what-if scenarios involving privacy is often (but not always) the wrong way to go.
A) They will have all of your financial information, as opposed to banks that will each get a slice. So the data they have is much more sensitive.
B) YNAB has around 100 employees in total. They do not have the resources to secure their data the way big banks do. We all have our doubts about security at big banks, but I am sure small startups are way worse.
C) It was all unnecessary for YNAB to go online. The decision, much like 1Password's was about money, not clients. I cannot live in this day and age without a bank account. I can live with an old version of YNAB. Heck, I can live even without YNAB. If banks are necessary evil, YNAB is an unnecessary one. Why increase your attack surface with unnecessary stuff, just because there is some necessary attack surface remaining?
The mobile app is a really key use case for me, and even as a technical person I just can't be bothered to set up hacky sync via dropbox or expect my family to know how to do that. Even if I could be bothered, now I'm just kicking the responsibility to dropbox + myself with all the same problems. I'd rather have the app developers manage that responsibility.
I was just disappointed that I would have to buy the app again in order to upgrade.. because I just couldn’t see why it wasn’t free update.
I would be on-board with implementing the write side to opvault if they'd accept the PR, and would also implement the browser extension protocol server if 1Password would specify it, since as others have pointed out the KeePassXC browser extension is suboptimal
Then again, with all the massive outpouring of Bitwarden support in every single one of these threads ever, I am pretty sure the real solution is just to bite the bullet and jump ship to Bitwarden/vaultwarden like everyone else seems to be doing
I'm willing to stick around long enough to see if AgileBits makes good on their local vault something something, but given the past few years of activity, I'm going with "they're bluffing" or "it'll be a horribly hobbled implementation"
To follow myself up, I seem to have found another "those people don't know what they're missing" situation because I actually did try Bitwarden (Premium) this weekend and what a dumpster fire compared to 1P
I thought about writing up all the shitshow, but ultimately it just boils down to them not caring about their product or users
For some of the platforms, I would actually be on-board with jumping in to fix the innumerable bugs, but with them being a mixed setup (open and "premium" features), the fact that so much fundamental behavior has been broken for so long with no obvious mitigation strategy makes me question whether this is something I would want to invest in
I've recently been using keychain for new accounts, but not sure I wanna bite the bullet and go all in - just need a nudge.
I’ve been doing that for more than a decade (more like 2 actually) without a hiccup.
Bitwarden is fantastic. I pay for the OTP features, though I feel keeping the codes alongside my passwords weakens my security posture. That's my choice, though.
Are there advantages of using it over Apple's built in keychain?
Would appreciate if someone who has used/uses 1Password could comment on this.
I don't think Keychain (up to but not including iOS 15 beta) supports OTP.
On macOS, not much other than Safari seems to use it, I think?
-Password sharing
There’s some nice “sanity checks” on all passwords, manual or generated, like reused password warnings and by default it checks your logins at haveibeenpwned, which is a nice to have.
It supports many more kinds of secure data than passwords and credit cards. It has specific entry types for bank accounts, passports, reward programs, software licenses, and so on.
It also has lots of built in analysis tools for determining: - which of your passwords are reused, weak, or present in online password dumps - what websites can have 2FA enabled on them
As well as the ability to store entire documents in vaults.
Been using 1Password since 2008 and it's the only software of its kind I recommend to anyone on any platform.
1) It is very cross-platform. It works on iOS, Android, MacOS, and Windows. I believe that it is also Linux-ready.
2) It has the ability to sequester groups of passwords into "vaults," that can then be assigned in different configurations, for different accounts. This way, the Treasurer gets the banking login, and whatnot, but the Webmaster never sees them, and Treasurer never sees the CP login.
3) It seems to support a whole bunch of TFA.
4) It syncs over everything, and helps to enforce password hygiene.
It has a field for user name and password, both mandatory.
A password manager offers a lot more, including a field for notes or credit card numbers.
If it were just me, the iCloud stuff would probably be enough.
I did so after reviewing their audit results, awhat they documented about their architecture, and after they added great support for Linux. At the end of the day, not everything is a conspiracy - and their model appears to be incredibly secure.
I would like the self-hosting option (that like Bitwarden, will still require a subscription), but a big part of what I am doing is sharing credentials with family. 1Password does a great job there.
Honestly at the end of the day, everything else is about your value proposition. I didn't know or realize that 1Password had shifted to electron as asserted elsewhere. I guessed that there was a new version given that linux was supported but it made no difference for me. Great for them. Likewise, they are far more secure then me editing a password file. Eventually the market will decide here. If people really care about swift versus javascript, then it will penalize them eventually.
That said, people arguing that dashlane and others are better then 1password, given that dashlane has access to your passwords, I can't imagine that this is a choice that makes any sense given the basic requirement of a password manager (keep my passwords safe).
-- edited correction - dashlane, not lastpass.
Don’t get me wrong, I hate Lastpass with an unprecedented rage for something that should be a simple utility (I’m forced to use it at work and it’s a time sink), but I don’t know where you get that and would like a source.
> In this paper, we seek to fill in the gaps by gathering and analyzing a large collection of leaked password datasets across multiple years and various online services
It looks like they just used already leaked passwords.
https://survey.1password.com/self-host/
Source: I work there :)
They’ve gone over and beyond to support old licences far longer than it could be expected, and a password manager is the kind of sensitive and ubiquitous product for which SaS actually makes sense.
Anyone remotely involved in anything similar knows it’s a PITA to keep up to date while keeping device compatibility, and the folks at 1P have been doing great work.
Subscription services to me are only justified if they are providing a SERVICE which they are with the web version and ability to sync through their own servers, however, using a local version with your own vault can be done without any service at all.
So to me this looks like them intentionally crippling their own software in order to force people into paying a subscription fee that is not necessary. They already hide the ability to purchase a standalone license for 1Password 7 trying to get people to pay the subscriptions so this is the next logical step.
The idea that anyone except a tiny infinitesimal minority of all people should self host is ridiculous.
Even a lot of people with IT jobs have not enough time or knowledge to keep services like this working securely in a way that’s competitive with SaaS (i.e. these people are better served by paying others to do the job).
If you need any proof, just wander around any company that works in IT and do a simple check, see who has the latest OS version and who doesn’t.
edit: I misread and was looking at the business page. $4.99/month for family and $2.99/month for user is entirely reasonable!
We have me, my wife, my eldest, and my mum on it - and it is indeed super simple to be able to share things around.
I used to have keepas/lastpass/dashlane - but 1password is the only one I've managed to convince family members to use as well
Not sure where the signup link is, sorry.
What I have zero interest in is increasing my attack surface solely for their bottom line.
I'm also increasingly uncomfortable with the company handling my passwords engaging in the sort of spin and dark patters we've seen from AgileBits in the past few years.
Also I see your reply has been downvoted enough to become grey. (EDIT: Looks like between starting writing this and submitting it, you're no longer in the gray from downvotes!) I imagine it's because you made a blanket claim about spin and dark patterns without any supporting evidence. I'd be curious to know what you're referring to since I don't really keep an eagle eye on this stuff, I just use their product.
The one thing I do remember in the vein of "dark patterns" is how they effectively hid the method of doing a one-time payment for 1Password where you have to manage syncing and backing up the password file yourself. Seeing as I have no reason currently to do anything but make a charitable read of that situation which has been decried more than once on HN, I'd be willing to bet they did so for the following reason: They have had many problems in the past where a customer has lost a password file because they were not a power user and did something such as keep it on one hard drive in their only computer. (reinstalled windows, hard drive died, etc.) So they wanted to make something that would prevent that from happening for the vast majority of their customers that don't really understand stuff like backups, or don't have Dropbox, or who aren't part of Apple's ecosystem and have iCloud, etc. so that their passwords will remain safe and secure. So they made their own sync service and hid the version that would do local-only files so that only the dedicated users who really want to do that would find it and use it.
OR alternatively they're a bunch of greedy people that just want to hoover up dollars from our wallets, as people love to accuse them of here. Maybe a little of column A and column B, honestly. Something something needing to ensure they have a company that stays in the black without wanting to absolutely bloat up their own software so it becomes another useless Enterprise(TM) application with each passing paid version.
Also the only affiliation I have with 1Password is I have a friend I recently learned works for them, otherwise I'm just a customer. I just got into one of my little ADHD focuses where I really wanted to reply with something long and detailed, so please don't assume I work for them or something and am defending them because of that :)
When I keep it on an airgapped machine that's a lot harder than when it sits on 1password's internet facing servers.
Except that they control the client that I'm entering the master password into. So either the password is sent to their servers anyway or a malicious actor could simply update the client to do so.
It's absolutely incredible to me that people ignore one of the biggest sides of the argument for pre-baked, user friendly products like 1Password: usability for as many people as possible.
Someone above outlined it nicely: If you let 1Password take care of encrypting the vault, and iCloud (for example) of storing the vault securely, then a malicious actor would have to compromise both products to get your secrets.
It's why we have a pilot and copilot on planes.
_If_ they obtain a copy of my password file.
"My email is nucleardog@nucleardog.example, my password is abcdef12345."
If I'm using 1Password's cloud service I'm... screwed? You now have literally my entire digital life.
If I'm syncing anywhere else, you've got a much bigger task ahead of you. First you have to _find_ where my vault is stored, then you need to gain access to it.
There's an extra layer of security to the way I want to do this. An extra factor of authentication. I don't want the only thing between you and my entire life to be one set of credentials.
However the differential factor of 1Password, which was that it _didn't_ provide the storage if you didn't want it, has now gone away. Precisely why I chose 1Password when I started using it. I don't see the difference between this and any other password manager now.
There might be security or technical reasons for removing this option, but looking at how hard they've been trying to get me into a subscription during the last couple of years I just think we're on a bad case of subscription-all-the-things here.
Can you point me to where this gets set up? I'd love to do this.
Make sure you have your browser 1Password plugin updated to the latest version.
When you click on the locked 1Password icon in the browser, you get the "Double click to approve" alert on your Apple Watch. You double click the side button on your watch and 1Password in your browser is now unlocked. This also works the same way with Touch ID. Hope that helps. Cheers.
edit: Provided clarity regarding the Mac App
The switch to a subscription service is a forced downgrade for me; it's putting functionality I already have behind a subscription.
This is particularly an issue since the old versions (versions I paid for, mind you) are slowly going away (typically as a recompilation and submission is required to keep them available on iOS devices).
We now pay the subscription, a tad begrudgingly, but I have to admit 1Password overall does a great job.
Most record types (software license, wireless router, documents, drivers licenses, email accounts, membership, passports, maybe more) don’t exist in Bitwarden. I’m not sure what happens with all of those, maybe transformed into secure note, but again with all of the attachments removed. The lack of categories is also a nuisance for organization, you can create folders but have to manage it manually.
I’m still glad I switched, having bought 1Password on a bunch of platforms and a bunch of paid upgrades before it turned into a subscription. It probably would have been less money if it had been a subscription from the start with all the times I bought it. Maybe it’s irrational, I just don’t like being so dependent on a subscription service, and having a local network sync between my devices was just fine. Same reason Lightroom can pound sand with their $120/year licensing, I’m not going to keep my photo library in something that I just have to keep paying for the rest of my life.
Bitwarden is good enough for me, with 1Password as a subscription you can look at it and realize “this is going to be $36/year forever.” If I spent any time in it, might be worth the expense. I’ve bought a lot of software and I don’t mind paying for good software. But I’ve moved the things that were attachments to an encrypted disk image, and 99% of my password manager interaction is via auto fill so I don’t actually care how polished the UI is.
Family sharing would be a more compelling reason to stick with it if you’re using that.
It's not quite a silent dropping -- 1Password warns you with a popup during the export that it doesn't include them in the export file. BitWarden won't warn you, but in its defense the files aren't even present for it to skip...
https://imgur.com/a/cjMbWZT
I think it might be the only "better than perfect" import story I've ever experienced, and I can't rightly expect it to happen again, but it happened once and that's something.
I previously used LastPass but heard about Bw on HN. Saw it had Yubikey support for just $10 per year. Tried Bw. Have never regretted that decision.
While I understand subscriptions can add value, I don't understand the forced model. Clearly 1Password has a subset of customers that don't want what they're forcing on customers. Maybe it's that they're positioning to sell the company and moving to 100% subscription boosts the bottom line valuation. But in the majority of cases the customer is not always delighted by this move. Sales organizations love to claim "it's what the customer wants", "it's more affordable", among other half-truths - when the reality is it's a much more consistent revenue stream that disconnects customers voting with dollars from continual enhancement of the product such that the customer is incented to upgrade.
Thank you!
I just tried to do this after comparing the features that I use and what I'm paying 1p vs. the bw rate.
There seems to be no export mechanism from web access.
I tried installing the (Linux) desktop client, which exports to a different file format from the one, single 1p format listed as supported by bw.
Bw did not like it.
I also could not get it to digest the json-like data in the alternative paste import box.
If anyone knows how I can migrate without manually entering hundreds of logins by hand, that'd be super swell.
It allows me to use the vault on all of my iOS devices and that’s sufficient.
I much prefer KeePassXC. I find KeepassXC substantially easier to use than 1Password on macOS. I strongly dislike 1Password's UX. It feels very cumbersome to use.
I have a shared family KeePass database as well. Works great.
What I'm not happy with is the possibility of password access being limited or sync breaking if 1Password servers go down. At least with Dropbox (iCloud, wifi) sync, I have full control over the local vault file.
Ultimately, it might be mostly about ownership and choice for me.
Ps. They can delete accounts too: https://support.1password.com/add-remove-family-members/
This makes losing local vault support an even bigger cause for alarm:
> After you remove a family member’s account, they can’t sign in to 1Password, which means:
> They lose all the items in their Private vault. Because the items weren’t shared with any other family members, no one will be able to access them.
Imagine: the access credentials of the administrator gets compromised, and the entire's family's digital life, stored on 1Password, gets wiped by the malicious actor.
The attack surface would be limited if instead, the removed user's license turns into a read-only one, like how 1Password currently deals with people using local vaults, and are not on a subscription.
Big, big nope right there, thanks.
I’m glad you find it affordable but these nickle and dime things add up. Especially when the product fits into $0 software so $4.99 is infinitely higher than $0.
I feel like these small, “affordable,” services are just whittling away the Unix philosophy of do one small thing well. Layering on unnecessary crap just to charge a fee eventually comes home to roost.
Also, passwords is a lifetime need. So 80 years x 12 months = $4,790.4 and that seems like a cost that should be reduced out of one’s lifetime.
Do I want to go to Tahiti once in my life, or pay for password convenience?
Again, glad you’re happy but I don’t want to live in a world where I pay $5/month for commercials versions that crowd out what should be community, OSS tools. I love curl and it’s awesome, but don’t want to pay $5/month/forever.
We forget that taxes are inefficient and should be minimized where possible. A login tax for all eternity sucks.
I think about sustainability quite a bit and if everyone who needs password management spends what you’re comfortable spending, that’s a waste I think. And when tech stops making things cheaper and faster it’s a bit sad.
Yes, but like in many other cases, an efficient market would mean that they will always need to be better in most aspects than whatever free, open source, or simply lower cost competitor pops up.
Unless they decide to prevent people from exporting their passwords, of course — and that's a big enough dealbreaker for me that I'd move away anyway, not caring how fancy or advanced the rest of their UX is.
What is the competition that costs $0? Bitwarden is $3.33/mo for equivalent functionality to the $4.99/mo plan from 1Password.
The $0 competition for hackers is https://github.com/dani-garcia/vaultwarden
You have apps on every device to access your password database and do autofill. I stored everything in KeePass, recovery keys, TOTP seeds, sensitive documents and notes. I get the password sharing thing for families but for a single user they have the same featureset. The only thing missing is browser access but even though I now have browser access to Bitwarden I think I’ve used it like twice. I think I used Keyweb maybe once.
Your choice of solution isn't the same thing.
Let's Encrypt SSL/TLS certificates are free, as is Apache/Nginx/Caddy to reverse proxy Nextcloud or any other solution (if a web based interface is needed). You might also need something like ngrok ( https://ngrok.com/ ) for publically accessing the instance if you're behind NAT and are hosting it on a homelab, or alternatively just put it on one of the VPSes that you're using, if you have any.
Personally i'm using a similar setup (a WireGuard VPN tunnel or two in there as well) on my pre-existing VPSes, so the effective costs are 0$ for me. And the file based approach is actually superior to any (possibly) dubious browser plugins in my eyes.
It does seem like an interesting and useful project, though there are also other more popular alternatives like Caddy: https://caddyserver.com/ (even though their V2 not being backwards compatible was a tad annoying)
Oh, and some people also have pretty good luck with software like Traefik: https://traefik.io/traefik/
Apart from that, just wanted to say that WireGuard is absolutely lovely! Pretty simple to set up, works well and uses way less resources than something like OpenVPN.
I've got a lab for stuff I want to tinker with, but a password manager is seen as an "essential service" to me like e-mail and music. I'd much prefer to pay a bit per month and have a team of professionals deal with it if the servers go down.
If at the end of the day my home server breaks and I want to get on and watch Amazon Prime/Netflix/whatever I still can with a hosted password manager. I value my time and sanity a lot more than £2 a month.
Currently doing just that, if any of my servers go down, i can still access all of my passwords on my desktop, on my laptop, on my tablet, on my phone or on my backup servers. Of course, provided that i have KeePass or a mobile app installed and know the master password.
Oh and I do manual backups to SD cards just to be sure every month. I'm not sure how I'd do that with a cloud service where in a sense their entire company (and my network connection to it) is a single point of failure. If my internet connection goes down, how would I log in to my selfhosted software in my homelab over LAN, without being able to access the passwords?
Potentially. Are you looking to make a prototype, or are you trying to go to prod with mission critical data?
Most people here could trivially roll a prototype grade password manager in pretty limited time. Getting something hardened and reliable is a different story.
Their client used to support this and they stopped. Because their current way makes them more money.
Their old client was super easy for non-technical users and groups (just enter Dropbox credentials, etc).
My time probably isn't as valuable as that of the many people here (about 5x less earnings on average in Latvia when compared to places like US), therefore it definitely makes sense for me to upskill myself in any way possible, especially if I get usable software out of it.
But if you take the container based approach, there is almost no administration to be done:
As for the UI, i agree in principle, but not in this case. KeePass has good UI and I'd argue that you don't need a team of UI and UX developers to keep track of some usernames and passwords (and maybe certificate files).Furthermore, I'd argue that most of the cloud offerings are actually problematic because not all of them let you download the data as files. In contrast, KeePass works with files (much like SQLite) and therefore, if you'd prefer to use SD cards or Samba or NFS or whatever instead of VPSes to somewhat decrease the attack surface, or simply use tools that you know, then you can do that. Want Syncthing instead of Nextcloud? Go ahead!
I'm putting emphasis on this because the line of thinking that we need web SaaS platforms for everything is dangerous - it makes you think that the problem is more complicated than it actually is. Whereas in reality some people probably get away with using password protected spreadsheets (don't do this). The problem is complicated only from a security perspective. That's it.
The cloud solutions excel at convenience and things like browser plugins and it's good that they're offering options for the less technically inclined folk, but they're far from the only option.
And specifically you only need the DB free tier to store a 1PW vault, so the only cost was paying for the 1PW client (which I am more than happy to pay for on major version updates, as long as it is not a subscription).
1PW removed functionality that existed, with goal (or at the very least the effect) of locking users into their own cloud platform with a new monthly bill.
After setup I rarely have to think about it, maybe manually synch a conflict between the dB's every 3 months or so.
Overall, _very_ happy with the setup.
We're not the primary target audience for 1Password, we just happen to fit under the umbrella anyway.
I have no particular qualms with paying for software whether as a one-time purchase or a subscription.
I just don't want all my stuff syncing to and reliant on 1Password's infra.
I'll pay them $5/mo to self-host my own passwords. But they won't let me. So I switched to KeepassXC.
Your vault is local, and synced to/from the cloud.
Basically just like Dropbox. If your internet is down and you cannot reach Dropbox, all files synced to your computer are still there, on your computer. It's just that any changes you make locally or changes made on dropbox.com cannot be synced until your connection is back.
And also from a user security standpoint, i don't think we can keep going on making enhancements to user security good practice habits if we gate keep good password habits behind paywalls.
I saw something mentioned about self-hosted vaults. That is something I might consider for my family.
I advocated for the use of 1pass at work precisely because we can share strong passwords with the team. Otherwise, people would just use the same, well-known weak passwords for everything, including business critical ones like domain registrar or Gsuite admin or the root AWS account.
I am not as happy about having another Electron app running on my local box. I hope they spent time locking things down. On the other hand, if it means my wife (on Windows) gets feature parity with my macOS client, that would be good. Even better if the Linux desktop gets feature parity and no longer have to rely on the web or browser plugin.
It saves me so much time compared to how I used to have to do it — pull out phone, unlock, open Authy, wait forever for it to load, type in code, put phone away…
It’s the little things that all add up. I’m very happy with 1Password — been using it for 10 years, and happy to subscribe, considering it’s probably my most-used utility app.
Until your vault is somehow compromised and your second factor is no longer distinct from the first one...
I have never even _heard_ of someone having their 1P master password compromised and the vault(s) exfiltrated (although I grant you it could be just because the NSA doesn't write blog posts about their pwn2own victories)
It's my recollection AgileBits is also running (that is: currently) a CTF with a publicly exposed vault, so folks can test the resilience against attack for themselves
Absolutely. But also, in such setup, the security benefit of 2FA/OTP codes are negligible at best since there are no conditions under which only one factor could be compromised without also having the other factor leaked (assuming you're using unique passwords for each identity, which is the entire point of a password manager).
However, I suppose it could be used for bypassing the inconvenience of mandated 2FA scenarios (to the dismay of your company's security team).
Phishing and good ole fashioned human error are two methods by which a password can be leaked without exposing the 2FA token.
> Hello, dear sir, this is the USA IRS and we are going to send the FBI because your TOTP code is expired and are going to put you in jail if you don... hello? hello?!
> Click this link and paste in your TOTP secret because we need to verify your identity: https://1passsword.com/2fa-verify/
> if you think some rando can _phish_ a TOTP secret
Given the context this discussion is about (someone with a 1Password vault, storing unique passwords and TOTP secrets for each account they have) do you see any scenario in which a user gets his password stolen but not the token (or the OTP secret seed altogether)?
> Hello, dear sir, this is the USA IRS
If an attacker via a phone call is able to get the victim to (a) unlock their 1Password vault, (b) spell out their password for account X, what makes you think they couldn't get them to also (c) open their 2FA app and spell out their TOTP token?
> I previously thought that we were just having a difference of risk tolerance
The point I was making is that there are no security advantages to setting up a time-based OTP as a second factor for authentication if the secret seed is going to be stored in the same vault where the passwords are: might as well just forego this TOTP setup altogether and save the extra hassle. Or get a hardware second-factor (TPM, Google Titan, Yubikey, ...)
[1]: https://www.zdnet.com/article/new-tool-automates-phishing-at...
Man in the middle attack, Phishing attack, Over the shoulder attack, Brute force attack, Keylogger, Http (not https) traffic sniffing, 'Breech' of the site and realisation they host their passwords in clear text on an unsecured db online.
Then there is human error; typing password into wrong site, giving your password to the tech support cold caller, telling someone your supersecret password ...
If you can see the password, you can also see the time-based OTP, and you can use those to gain access.
> Phishing attack > Over the shoulder attack
If you can convince someone to provide you their password, it's highly likely you'll also be able to convince them to also provide you their time-based OTP.
> Brute force attack
A successful brute-force attack on the vault (unlikely) means you've lost both your password and your OTP secret. A sucessful brute-force attack against a remote account using a safe password (re: password managers) is very unlikely!
> 'Breech' of the site and realisation they host their passwords in clear text on an unsecured db online
The password and the OTP secret themselves have no value (given that you're using unique passwords for each account). If the attacker has breached the service back-end then it's gameover anyways, regardless of 2FA for user accounts.
If you're doing this there's a very limited benefit to TOTP anyways.
The point of using 2FA for me is to protect me against my password being compromised since it's a long_lived access key.
> If my password vault is compromised it's game over anyway.
There are ways you could make a vault compromise not mean a complete/irreversible takeover, but that would either give up breakglass access as you say or add complexity and reduce availability.
> The point of using 2FA for me is to protect me against my password being compromised since it's a long_lived access key.
In which situations on your setup would a unique password compromise not imply there's also been a TOTP token/seed compromise?
Personally, the problem of managing reliable persistence of my password database just isn't something I want to spend time on, and the incremental difference in security posture is uninteresting to me given that it's encrypted at rest anyway. In terms of waking hours spent worrying about the security of my household IT, the security and persistence of sensitive documents (mainly vs. ransomware) is a bigger problem and I like that my passwords aren't tied up in that mess.
And that's why I only use community maintained software with no telemetry or "data driven decisions."
At the end of the day if you want a password vault that is sync'd across devices, you're trusting someone...somewhere. Be that 1password, dropbox, or even that Linode you manually rsync your data to. You've got to decide what is the biggest risk for your own personal use cases.
For me, I'd rather store my sensitive data with a company that has demonstrated a repeated push to keep my data as secure as possible, even from itself. It's their core business, all they focus on.
I suppose they could do something like JetBrains where you get updates while subscribed, but realistically login breaks for users would be a mess to support and a standalone text editor is a different service.
This move makes sense to me given their market. Those that want to run a vault can use an alternative that's more of a hassle to deal with.
[1] https://techcrunch.com/2019/11/14/fourteen-years-after-launc...
I'd only recommend LastPass if you're a fan of LogMeIn, Ltd. and only being able to see your passwords either on Desktop or Mobile (on the free version).
https://support.logmeininc.com/lastpass/help/what-can-i-expe...
Lastpass is a bucket of ass.
They've had security bugs in their browser extension before, but it is almost required to use it - the webapp works horribly without it. My least-used browser gets that extension, so it isn't running most of the time, at least. And with it, the UI is still terrible. The app is just awkward and poorly done.
The one good thing I can say is the user/group model is reasonably implemented.
I can understand your frustration about Electron, but I hope you find my explanation reasonable. Please stop spreading misinformation.
This is the source of your mistake. Users don't desire to have the same UI across different OS environments, it's only an app's developers that care about that. Cross-platform UIs are inarguably a worse user experience than UIs tailored to the conventions and designs of each OS.
A Mac app that doesn't actually feel or behave like a Mac app is not a good Mac app. The same is true with tvOS apps like YouTube and Prime Video that don't actually feel or act like good tvOS apps.
Um, speak for yourself. I personally don't like having the docs showcase completely different UIs to the one I'm using. I also like having an app i can run on Linux, which has been happening a lot more since Electron became a thing (no sane company wants to write apps in GTK, and much as Qt is a great toolkit it requires expertise most SaaS vendors don't have).
You're speaking as if it's fait accompli that 1password made a mistake picking electron. It is not, and I am fairly certain they did not.
Maybe if you choose to use multiple platforms you should just deal with the multiple approaches to UI? Why should the single platform citizens suffer from a UI that's inconsistent with the rest of the platform?
To stretch it to an absurd case:
Imagine Slack decided that the shortcut to copy text will be Ctrl+C on all platforms. And Windows users who occasionaly use a mac would rejoice because it would save them from having to think which button to press.
I guess we'll have to agree to disagree on that. I personally enjoy having consistent user interfaces across the apps that I use, and there are many other people that would say the same, so I would avoid making broad assumptions. From our perspective, consistent user interfaces are a win-win for both the development team and the majority of end users. That being said, I'll take your feedback into account.
I don't know if your reasoning is that looking like a web app means it is consistent with those apps, or that the apps look the same across platforms, but neither of those arguments are compelling to me. I chose the platform I am on because I think the interface is a good one that makes me more productive.
And I have never found an Electron app (or web app in general) that is as high quality as good native apps (on any platform). There are just so many compromises, and I am not even considering resource usage here. Everything just feels a little slip-shod.
https://daringfireball.net/2018/12/electron_and_the_decline_...
This is such a bizarre claim. I know Agilebits understands Mac users.
To be brutally honest, I've heard this line from a lot of software shops after they decide tailoring their apps to the native platform is too expensive or inconvenient for them. Suddenly they all find that their users don't care about their native platform - I suspect if I went looking for the discussion from back when Adobe did this, I'd see the same phrasing.
I canceled my subscription today.
Let's be clear about this: you are the seller, we are the customer. You can't `agree to disagree` with your customers.
If you don't agree to what some your customers are telling you, then they won't be your customers, and you won't lose just these customers but also all the others who observe your behavior. It is a modified case of repeated prisoner's dilemma. If I observe that you tend to defect on other instances, I will less inclination to cooperate. In other words, your reputation will suffer.
On the consistent user interfaces, the consistency of an app with other apps on the same platform is much more important than the consistency of that app across platforms. Even if you use multiple platforms, you switch much more frequently between apps on the same platform than between different instances of one app across platforms.
Kinda a random thought, but is it at all possible to build a native 1Password app using their API [1]? I haven't read Agile Bits' ToS, but I would be interested in working on / following a Mac-centric client.
[1]: https://support.1password.com/connect-api-reference/
Parent makes a lot of sense, actually, in context of the submission headline. There was no misinformation here at all.
[1] https://news.ycombinator.com/item?id=28145755
I did (incorrectly) assume that the parent was talking about Electron, so that's my bad. That being said, our decision to move away from licensing is absolutely not being driven by VC funding, so the parent comment is also spreading misinformation. We were building a subscription-based model all the way back in 2014, and we're phasing out licenses for the host of reasons that were mentioned in the original article.
The goal of a VC company is to either grow big or die. That's it. Risky bets at the expense of existing users are expected if current growth does not meet expectations. Worst case everyone quits the app and you go bankrupt. VCs expect that 9 time out of 10 so no big deal as long as the 10th makes it big.
Why would anyone think for a second that it would be a good idea to force people to store every password for everything in their life in your cloud without an opt out?
That, even more than Electron and the subscription model (both which do bother me), is an absolutely deal breaker. I've paid for every version of 1Password since v3 in 2009, but I'm done with it now.
That being said, we are looking into gauging user interest in self-hosting. Please take a look at our survey [1] if you want to share your thoughts. Hope that helps!
[1] https://survey.1password.com/self-host/
1Password 6 is great, and I'll keep using it until it quits working on my devices, but no more after that! I used to recommend 1Password so much to people it was borderline evangelizing, but I quit recommending it once the subscription was pushed over the other options, and now that local vaults are going away I'm actively recommending against it to anyone that asks.
Guess I'll be moving to Bitwarden or Keepass myself; time to research!
Our Electron app is really only a thin client over a Rust-driven backend that handles all our business logic. We only invoke Typescript when we need to render the UI; everything else goes through Rust. We even run some Swift code too, for deep integration with the operating system.
Memory is still an issue with Electron, but we're getting better at reducing the footprint. We've put a lot of work into optimizing this app, so I recommend you give it a shot; I think you'll be pleasantly surprised by how performant and responsive it is.
> Memory is still an issue with Electron
Sounds like their conceptions are correct.
My work Slack dies at least once every day, and makes my laptop scream if I have VS Code on. I don't want to know what adding 1Pw will do.
I switched to KeePassXC a while ago due to the increasing hostility over local stores. Looks like I was right on the money.
KeePass has served me pretty well - it's not as polished, but it works absolutely everywhere due to the numerous client apps on many OSes, and it syncs normally. Toss on something like Dropsync for mobile, and it's pretty streamlined: https://play.google.com/store/apps/details?id=com.ttxapps.dr...
Maybe I'll try bitwarden.
You may not like the subscription business model, but it isn't rent seeking. Monthly payment != rent seeking.
> Rent-seeking implies extraction of uncompensated value from others without making any contribution to productivity.
I think the rent seeking comment was about removing the option for (free) Dropbox sync and only supporting the subscription-based plan. They are asking for more money for less product.
>by manipulating the social or political environment in which economic activities occur, rather than by creating new wealth.
Otherwise simply raising the price on something would be rent seeking.
Raising the price of something certainly can be considered rent seeking.
For example: https://pnhp.org/news/rent-seeking-by-drug-barons/
However, given they have all the password for many people, how are they not one of the biggest targets in the world? In their old Dropbox model, I understood the security model. In the service model it's moved to "Just Trust Us".
Is there anyone who can help me understand how this model is secure?
It's basically E2EE (where the encryption key is your master password + secret key, which looks similar to a guid), with the caveat being that 1password is still accessible via the browser so you do have to trust they're not compromising you by saving your secret key + master password separately (that is, unless you're auditing the login page every time you open it).
https://support.1password.com/security-assessments/
They've gone pretty far above and beyond what we're used to seeing wrt sharing security details, audit results, and architecture information.
Self hosting would be nice to keep though. Been thinking about setting up a server to hold all that stuff
This is both upsetting and disturbing.