Re:Flaws in deterministic password managers
by tprynn on Tuesday November 22, 2016 @02:47PM
(#13016971)
Not to be too pointed, but would you consider adding this disclaimer to your blog post and github repo? Hopefully that will inform potential users before using a system that could leave them less secure.
Re:Flaws in deterministic password managers
by ogrisel on Tuesday November 22, 2016 @03:29PM
(#13017380)
Funny, I also implemented mine a while ago (mostly un-maintained but I still use it): https://pypi.python.org/pypi/virtualkeyring/
I also thought I was clever and the first to do it ;)
I have been thinking about adding support to keep some state info in a yaml file to deal with revocation and specific varying password policies (e.g. in a dropbox synced folder) but I was too lazy to implement it. If someone wants to do it please feel free to send a PR.
The compromised master password issue is a real issue though.
Re:Flaws in deterministic password managers
by Nomentatus on Tuesday November 22, 2016 @06:22PM
(#13018573)
Use a photo as the master password. It can't be confused with text.
Re:Flaws in deterministic password managers
by minitech on Tuesday November 22, 2016 @06:47PM
(#13018709)
This change seems kind of worrying: https://github.com/libeclipse/visionary/pull/40/files#r79336...
The distribution of characters in “complex passwords” isn’t even?
Re:Flaws in deterministic password managers
by libeclipse on Thursday November 24, 2016 @02:21AM
(#13028806)
That doesn't matter. I could just put a full stop at the end of the string and call it a complex password. The point of it was for sites that require symbols. The complex password doesn't add a meaningful amount of entropy to a sufficiently long normal password; a 32 character normal password already has log2(16^32) = 128 bits of entropy.
We rely on the seed for security, the seed being the hash that scrypt spits out
Re:Flaws in deterministic password managers
by minitech on Thursday November 24, 2016 @03:18PM
(#13032512)
So it’s way too complicated for that purpose, then.
Re:Flaws in deterministic password managers
by libeclipse on Monday November 28, 2016 @03:21AM
(#13054128)
That's not an argument. Keep in mind that entropy is a property of password generation, not the result of the generation.
Re:Flaws in deterministic password managers
by minitech on Tuesday November 29, 2016 @05:02AM
(#13062058)
I mean, what do you want me to say? It is way too complicated. Why are you using a pre-shuffled character set and getting a permutation of it by index when the index is always extremely low compared to the number of permutations just to get some symbols in your password? Just base64-encode with a custom alphabet or something.
I never said anything about entropy, either.
The points that the article makes are right, and people should use conventional passwords over deterministic ones.
But I guess it appeals to a certain small subset of people. For some servers and things that I own I find myself using it sometimes: it turns a relatively strong password into a monster of a password.
Another useful use is that it's good at sharing passwords for things with friends, and for that, it's surprisingly handy.
For the average person however, the disadvantages and the things that could go wrong outweigh the advantages. Keepass is what you should be using.
[0] https://libeclipse.me/visionary/