74
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 11 Sep 2023
74 points (97.4% liked)
Privacy
31601 readers
344 users here now
A place to discuss privacy and freedom in the digital world.
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
Some Rules
- Posting a link to a website containing tracking isn't great, if contents of the website are behind a paywall maybe copy them into the post
- Don't promote proprietary software
- Try to keep things on topic
- If you have a question, please try searching for previous discussions, maybe it has already been answered
- Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
- Be nice :)
Related communities
Chat rooms
-
[Matrix/Element]Dead
much thanks to @gary_host_laptop for the logo design :)
founded 5 years ago
MODERATORS
For the 2nd point:
Mixing it doesn't reduce it to 1fa - it still makes your accounts immune to Passwort leaks and common attacks
You are only at a 1FA level if someone hacked your PW-Manager but in that instance you're most likely fucked anyway
Sure for the most important accounts having 2FA in another app is good so you can at least secure those if the PW-Safe leaked but I have 2FA on every single website I use(d) that offers it - even if I'm only on there once a year so using a special app is less important than just having the additional security in the first place
I usually call it 1,5FA since it is reduced to one factor, namely the password manager, but that password manager is protected by 2FA.
It's still 2FA. They're separate secrets. But I agree that hosting your passwords on someone else's computer is asking for trouble.
At this point, it really depends on implementation, and the exploit.
It the exploit can get both in one go, I'd argue that it's technically 1FA. Else, no matter how trivial it to do both steps, it's 2FA. But then it pushes the question back to "what is a go at it"? A script? A remote file copy? Etc.
Kinda important technicality in my view, as separating them in the password management process is the first requirement to actually have two factors.
However, using two apps instead of two parts of the same app isn't much of an improvement. If the device is compromised, it doesn't matter much how many apps you split the data into. You can always use different passphrases, no biometrics, etc, but at that point, it's so inconvenient that you're just better off carrying two devices...
The point I'm making here is: 2FA were originally supposed to be actually separated (other, offline device). However, for various reasons (cost, adoption, convenience, etc), apps were pushed instead. Now we have a regression where, in most cases, 2FA or MFA are often just a "single factor authentication with extra steps". As a matter of fact, true MFA was the main criteria when I selected my bank. And the day they force an app on me is the day I change banks.
As long as you at least have actual, separate 2FA for access to your recovery email(s) you should be more or less fine.
Unless you mean that if your password manager is compromised it probably means that your device is compromised, which also means that you're probably also a victim to a session hijack for the recovery email(s), in which case you are truly fucked.
You can also have a multi-level approach where for "higher value" accounts you have a separate password database so the more valuable accounts aren't exposed as much as everything else... There are definitely options.