Maybe suggest that to them?
I mean, I dunno. Knowing how to press an icon or copy-paste content from one app to another is sort of computer table stakes in 2018. These are problems on the user end, not the product end. It would be terribly insecure if their passwords were just automatically input every time someone on their computer opened a login screen.
I find this to be quite an under-represented opinion whenever I encounter password security discussions. How many people's threat models need consider physical security of their house? Surely most people's number one - if not only - threat is using a compromised service, so a password manager is just another vector; albeit one whose raison d'etre is security.
If your machine with the password manager gets pwned then it's probably game over, and you can do that remotely for a networked device. So at the very least it's reasonable to compare the physical security of a paper notebook and a computer.
Yes you might have encrypted the device but as everyone is so fond of saying 'once you have physical access it's game over anyway', so by that logic the notebook and computer are as secure as one another as they both rely on physical security. Maybe the computer is even less secure as you can attack it over the network!
It's important to plan for disaster recovery though. That's probably a more reasonable fear - something like fire or accidentally spilling coffee over the book would be pretty bad. Maybe a backup copy in a waterproof fire safe would be a 'good enough' solution for priority accounts like email from where you can probably reset/recover all other accounts.
Of course, the ideal for security is that the best options are so convenient that you might as well do them. But there sure is a lot of circlejerking that happens when someone is exposed as "doing it wrong."
I use keepassXC (actually MacPass, which is brilliant and has an HTTPConnecter plugin that can talk to the Firefox addon keepasshttp) and it works great. Maybe not as fancy as 1P etc but free and open source. On iOS I use MiniKeePass which also works well.
This is the setup that I was going to suggest to him. Personally I find it not that complicated, just needs some time to get used to the routines.
Some implementations do and it has been patched in the main repo but didn't make it out to all users. Communication from KeePass/MacPass to the browser is just over http as the name suggests so passwords are sent in plain text and can be sniffed over the network.
If it's confined to localhost then you're fine as it's as secure as not having a compromised device in the first place.
Can you explain this issue a bit more?
I use 1password, and I would be very angry if it randomly did not record my input data correctly. Yet, it's been flawless. Whether it's a username, a custom data field, an email, a site, a custom password, etc - it has never not recorded a piece of data I gave it. I'm on OSX, Windows and iPhone.
Is there an issue here I should be aware of? Because not recording data is a big, big deal..
****
My best guess is they used JavaScript to replace the contents of the text field before submission. Thankfully I've apparently never needed to use this password.That said, out of 1000+ saved passwords, this is the only case like that I've seen.
When you revisit that entry in the future. Like possibly the far future when your one-year-long session finally expires, you'll find out you only have a password.
Pretty bad UX. The popup that has [Cancel] [Save] should just show you the username and blotted out password for you to confirm.
I have a few entries where I was so paranoid that I said fuck it and copied my password right into the name of the website entry. So I'm wondering if there's a case where it only saves the username and not the password because it doesn't detect it? I just haven't registered for a website in a long time so I only remember the one case.
If you haven't encountered it, you're just lucky or, more likely, haven't yet noticed. ;)
3rd option, I don't use that feature :)
I create all my passwords before registration when I need them. So that's the weak point it seems. Hell, I don't even have the browser plugin installed.
Also, the 25% failure you speak of is why I don't trust it at all. All it takes is one time where it doesn't save your username and it becomes useless.
So I just open it up and create entries manually. Which is fine for me but exactly something I wouldn't expect everyone to do since the app trains you to depend on its autosave.
I think a few UI changes would go a long way. I have a mental list and wish it would be worthwhile to build my own, as every developer likes to think. But in reality it just feels like a list of minor features/tweaks they can add eventually.
I tried migrating my entire family to a 1Password family account. Honestly for people with limited tech-knowledge even 1PW is still too complicated.
- In 25% of the cases it does not save e.g. the username correct. Explaining my parents how to open the app, edit the login, etc. is just not gonna work.
- they don't prefill logins (like e.g. Dashlane) so you either have to press the icon or do the keyboard shortcut. Again not suitable for someone who is not very technical.
- On some sites (even big ones) the user/password inserting simply does not work. Explaining them how to open the app, copy user/pass, switch to browser... not gonna work.
- generating random passwords and filling them on registration page does not work 100% either
- using it on mobile is just horrible.
Only thing I could come up with would be (on a Mac) the built in password „manager“. Any ideas? Hate people using their birthday as pw just because there is no easy solution to this problem.