Live data from Hacker News

KeeWeb: Unofficial KeePass web and desktop client

github.com

41–50 of 125 posts

Re: KeeWeb: Unofficial KeePass web and desktop client

#41
post #29

Do not generate passwords with it, it uses insecure Math.random: https://github.com/antelle/kdbxweb/blob/906e927d3e3384db4dd3... https://github.com/antelle/keeweb/blob/master/app/scripts/ut... (in meme form: https://imgur.com/FcZNflQ ) Filed issue: https://github.com/antelle/kdbxweb/issues/5 (embarrassing/funny: it was me who wrote Salsa20 "user-space" generator used here ( https://github.com/antelle/kdbxweb/blob/906…

Just so we're clear: your assertion is that because the password generator uses a non-cryptographically secure PRNG, generating unique 20+ character alphanumeric passwords for every login is worse than people's default behavior? I mean, I get that it's worse than other keepass implementations - that's obviously a problem - but if this gets people to stop using "hunter2" or "p4$$w0rd" that's got to be worth something,…

No, it's not worse for your scenario. (That wasn't my assertion)

However, this is an alternative to KeePass/KeePassX, so the typical behavior of KeePass users is to generate passwords with it, not reuse bad passwords.

For example, I use KeePassX to generate strong passwords for long-term encrypted archives, and if I switched to this app, I wouldn't get the same security.

I'm confused, though, should I say: "All right, people, fuck it, generate your passwords with Math.random! YOLO!"

Re: KeeWeb: Unofficial KeePass web and desktop client

#42
post #36
post #29

Do not generate passwords with it, it uses insecure Math.random: https://github.com/antelle/kdbxweb/blob/906e927d3e3384db4dd3... https://github.com/antelle/keeweb/blob/master/app/scripts/ut... (in meme form: https://imgur.com/FcZNflQ ) Filed issue: https://github.com/antelle/kdbxweb/issues/5 (embarrassing/funny: it was me who wrote Salsa20 "user-space" generator used here ( https://github.com/antelle/kdbxweb/blob/906…

Is there a practical attack for this usage? The attacker would need to have a bunch of your passwords already? EDIT: Not that I'm justifying using Math.random, I just don't see why you so strongly recommend against using this tool.

>> Is there a practical attack for this usage?

This is the question I ask every single time I read about anything in security. It feels like there's just SO MANY THINGS wrong about every damn thing now the only way I can figure out what I have to really worry about or focus on is anything with a PRACTICAL attack that's easily automated and remotely exploitable.

Re: KeeWeb: Unofficial KeePass web and desktop client

#43
post #24
post #2

This is awesome. People are obviously going to give you a hard time about security and your implementation of the important parts of the software, but that's the advantage of open source! Edit: I am a daily user of KeePassX and get really tired of the UI after a while so I will definitely be trying this out ASAP!

Which version of KeePassX are you using? The 2.0 seems better. And if you use a Mac, have you tried MacPass?

I found 2.0 to be worse, but that's just my subjective opinion. I don't have a mac, so maybe that's a difference?

Re: KeeWeb: Unofficial KeePass web and desktop client

#44
post #36
post #29

Do not generate passwords with it, it uses insecure Math.random: https://github.com/antelle/kdbxweb/blob/906e927d3e3384db4dd3... https://github.com/antelle/keeweb/blob/master/app/scripts/ut... (in meme form: https://imgur.com/FcZNflQ ) Filed issue: https://github.com/antelle/kdbxweb/issues/5 (embarrassing/funny: it was me who wrote Salsa20 "user-space" generator used here ( https://github.com/antelle/kdbxweb/blob/906…

Is there a practical attack for this usage? The attacker would need to have a bunch of your passwords already? EDIT: Not that I'm justifying using Math.random, I just don't see why you so strongly recommend against using this tool.

I don't know of any published attacks on XorShift128+, which is used in most browsers for Math.random. What I know is that it's not a cryptographically secure PRNG, though, so all you have to do is sit and wait for one ;-)

Re: KeeWeb: Unofficial KeePass web and desktop client

#45

Check out pass for those wanting a solution in line with the Unix way: https://www.passwordstore.org/

One issue I have with pass is that it leaks meta-data about what you have stored. The contents are encrypted, yes, but the filename identifying the content is sitting right there in the open.

Re: KeeWeb: Unofficial KeePass web and desktop client

#46
post #36

Earlier quoted context omitted.

Is there a practical attack for this usage? The attacker would need to have a bunch of your passwords already? EDIT: Not that I'm justifying using Math.random, I just don't see why you so strongly recommend against using this tool.

>> Is there a practical attack for this usage? This is the question I ask every single time I read about anything in security. It feels like there's just SO MANY THINGS wrong about every damn thing now the only way I can figure out what I have to really worry about or focus on is anything with a PRACTICAL attack that's easily automated and remotely exploitable.

Cryptographic attacks become better, some of them become practical. RC4 attacks were not considered practical until recently, and now everyone runs with their heads on fire replacing it.

The best answer is to listen to what security people say. When they have a practical attack on something it is already too late.

Re: KeeWeb: Unofficial KeePass web and desktop client

#47
post #36

Earlier quoted context omitted.

Is there a practical attack for this usage? The attacker would need to have a bunch of your passwords already? EDIT: Not that I'm justifying using Math.random, I just don't see why you so strongly recommend against using this tool.

>> Is there a practical attack for this usage? This is the question I ask every single time I read about anything in security. It feels like there's just SO MANY THINGS wrong about every damn thing now the only way I can figure out what I have to really worry about or focus on is anything with a PRACTICAL attack that's easily automated and remotely exploitable.

I feel like your conclusion is the opposite of proper.

Proper would be: don't roll your own crypto, use what professionals created, and only in the way they document it to be used. When in doubt, email tptacek or another professional he would point out.

Re: KeeWeb: Unofficial KeePass web and desktop client

#48

Check out pass for those wanting a solution in line with the Unix way: https://www.passwordstore.org/

One issue I have with pass is that it leaks meta-data about what you have stored. The contents are encrypted, yes, but the filename identifying the content is sitting right there in the open.

[deleted]

Re: KeeWeb: Unofficial KeePass web and desktop client

#49

Earlier quoted context omitted.

You are uploading a file that is encrypted using very strong encryption, not plain text password. An employee of that company, or if the file was leaked due to technical errors, a member of the general public won't be able to decrypt it. If one of the richest governments wanted to, they might be able to, but if you had reasons to be a target you'd know better than using this. Also, take a look at SpiderOak.

Is strong-encryption something that 1password is fundamentally opposed to, or something they just haven't implemented yet? If I'm going to switch, the answer to question is pretty important.

>strong-encryption something that 1password is fundamentally opposed to?

where did you this idea?

Re: KeeWeb: Unofficial KeePass web and desktop client

#50

Earlier quoted context omitted.

MacPass is excellent. It finally helped me completely move to a password manager based life.

How is it better than KeyPassX? I (think I) want my manager to be simple..

It's native, much better user interface. Downside - for now: it's alpha, not even beta yet, so better keep a backup of your database.
Post reply on HN