- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
You must log in or register to comment.
If we didn’t already have the perfect option that is bitwarden I would probably go for this. But there’s really no reason to switch away from bitwarden to this. It’s open source, gets regularly publicly audited, and nothing ever leaves your device unencrypted. So even if they had their data center broken into and all machines stolen physically I wouldn’t have to worry about my passwords
Bitwarden is too functional and too affordable for me to really consider moving.
I use both. Proton pass is good because you can create, free of charge, up to 10 aliases for your proton mail account.
Does the creative commons licence at the end of every comment really do anything? Are you going to do anything about it if someone doesn’t respect the permissions you’ve laid out?
Are you going to do anything about it if someone doesn’t respect the permissions you’ve laid out?
No, but I hope that someday an IA spell the license for me to have a good laugh.
I would appreciate it if you’d stop adding it.
Why?
On mobile it is the most visible object on the screen, and very annoying:
To add onto what Andromxda said, SimpleLogin is included with your Proton account (might be paid accounts only).
Use it with a custom domain - it’s amazing and if Proton Mail ever shuts down you won’t have to migrate any of your logins because they’re already on your own domain.
Nice, I will try that
I’ll stick with KeePassXC but I’m still very happy to see them remembering about Linux. I hope Drive will be next, this is something I’m really waiting for.
As scientists, we know that transparency and peer review lead to better security.
What? App developers are scientists now?
I know this originally came from CERN, but I find it hard to believe those same folks are working on this now.
While I don’t particularly agree with the sentiment, those in the field of Computer Science could be argued to be “scientists”, though often not in the classical sense. As a Computer Science major myself, I would never consider myself a “scientist” in the classical definition of the term. Those involved in actual research, yes, though that does not describe me despite the title of my Bachelor’s. I would consider those involved in the theoretical side of Computer Science to be more akin to mathematicians, as most of the theory is based in mathematical proofs and models (take for instance the field describing formal computational models as a means to defining how computers operate, and how effective specific algorithms are in that context). Though I could understand the argument that those involved heavily in the theoretical side of Computer Science may be considered scientists, given their similarity to theoretical physicists. In that sense, there is also active experimentation to test hypotheses about algorithmic runtime. It’s a fascinating niche of Computer Science that I studied briefly in university, but likely will not be pursuing in the future.
Generally those involved with active development of commercial software don’t fit into that category, though. It’s very much a question of semantics.
I’d never admit it irl or to anyone I know because it’s petty. But it bothers me when cs people refer to themselves as engineers.
Referring to themselves as scientists would seriously be a step past that.
Damn, I thought for some unknown ungodly reason Valve implemented something like game pass for Proton.
Shhhhh, don’t give them ideas!
I’m very skeptical about online cloud-based password managers. I don’t trust that at all. I still prefer to use a local off-line password manager like KeePassXC.
Since the vault is end-to-end encrypted, it shouldn’t matter where it is hosted, even if it is in the cloud. Here is what a security researcher and a password cracker Jeremy M. Gosney has said about this after the LastPass incident.
”Is the cloud the problem? No. The vast majority of issues LastPass has had have nothing to do with the fact that it is a cloud-based solution. Further, consider the fact that the threat model for a cloud-based password management solution should *start* with the vault being compromised. In fact, if password management is done correctly, I should be able to host my vault anywhere, even openly downloadable (open S3 bucket, unauthenticated HTTPS, etc.) without concern. I wouldn’t do that, of course, but the point is the vault should be just that – a vault, not a lockbox.”
What is your threatmodel here?
The problem for me with completely self hosting it is that it’ll be relatively hard to get my backup, availability and sync requirements satisfied without a lot of effort.
Whereas I trust encryption in theory enough to hand my encrypted data to anyone. If the implementation is properly audited then I also trust that.
Most of my passwords are for accounts with 2fa anyway so even if both the storage leak and the encryption turn out to be subpar my threatmodel is still not violated.
Electron?
This is all I want to know. If yes, I’ll pass.
