Earlier quoted context omitted.
I use and like 1Password.
What do you think about pass [1]? [1] - http://www.passwordstore.org/
This one looks really great. Properly following the UNIX philosophy, at last.
KeePass – questionable security
151–160 of 231 posts
Re: KeePass – questionable security
#152Earlier quoted context omitted.
Well LastPass has had a breach now twice but the integrity of their password database is still holding strong. If you're using Dropbox to share your password database, LastPass having a breach shouldn't be of any concern. I'm fairly certain Dropbox has been broken into more times than LastPass ever will be. As someone who works in the security industry, I use LastPass and recommend it to everyone. It's no less safe t…
Well dropbox is excellent and secure in combination with Encfs.
Encfs didn't survive its security audit very well: https://defuse.ca/audits/encfs.htm (I don't know how much has it improved since then, though)
Re: KeePass – questionable security
#153Ok, your password database was affected by malicious modification. So what? How it can break the confidentiality of your data? Update: By the way, what's wrong with the bytearray compare code snippet?
I notice that the "change-password" function of yourbank.com is accidentally being served over HTTP instead of HTTPS. I just need to trick you into changing your password. I have access to your kdbx db (ex. you sync to Dropbox and I'm Dropbox employee). I can alter the kdbx file to change your password so that it is no longer valid. KeePass doesn't complain at all. You have a WTF moment and try to change your passwor…
> I can alter the kdbx file to change your password so that it is no longer valid.
How are you generating a kdbx file that has the record where they think it is? The entire file is encrypted en-mass except the header.
You can certainly make a kdbx file that KeePass will open, but it is impossible to make one that will fool the user without more than enough information to just compromise the database.
Re: KeePass – questionable security
#154These has been a security audit, ordered by the french ANSSI (French government IT Security agency). This audit resulted in a "CSPN" certificate, which basically means that 35 days were spent by a competent auditor (Thales), and no important vulnerabilities were found in KeePass 2.0 Portable.
Report: http://www.ssi.gouv.fr/uploads/IMG/cspn/anssi-cspn_2010-07fr...
Re: KeePass – questionable security
#155http://www.passwordstore.org/
Uses well-audited GPG, high level crypto functions which makes it difficult for the developer to get the crypto wrong.
Re: KeePass – questionable security
#156Re: KeePass – questionable security
#157Earlier quoted context omitted.
Password Safe [1] was designed by Bruce Schneier, that could fit the bill. It seems to have done quite well in the paper cited by xenophonf in [2], too. [1] http://passwordsafe.sourceforge.net/ [2] https://news.ycombinator.com/item?id=9727522
Looking the C++ code for this project, this appears to be unauthenticated TwoFish in ECB mode . (I thought, no, no way is this actually ECB mode, maybe they just did the XOR'ing for CBC mode outside the TwoFish class, but no: they appear to pad blocks explicitly to block boundaries and then ECB them.) I looked for a total of 4 minutes, so if someone wants to correct me...
You need to look at the PasswordSafe file format. It can be found here (among other places):
http://sourceforge.net/p/passwordsafe/git-code/ci/333dd9f23a...
ECB mode is only used for the internal keys. The database records are encrypted in CBC mode, and there is an integrity authenticator HMAC as well. However, the format was designed in the days when Mac-then-encrypt was considered proper. So the authentication HMAC is over the plaintext prior to encrypting.
Re: KeePass – questionable security
#158Earlier quoted context omitted.
Linux support seems to be BETA.
Where did you get that information?
http://passwordsafe.sourceforge.net/news.shtml
Under 28 Dec 2014 it mentions 0.95, but there is a 0.96 from 12 June of 2015 available at
http://sourceforge.net/projects/passwordsafe/files/Linux-BET...
Re: KeePass – questionable security
#159Earlier quoted context omitted.
Looking the C++ code for this project, this appears to be unauthenticated TwoFish in ECB mode . (I thought, no, no way is this actually ECB mode, maybe they just did the XOR'ing for CBC mode outside the TwoFish class, but no: they appear to pad blocks explicitly to block boundaries and then ECB them.) I looked for a total of 4 minutes, so if someone wants to correct me...
You need to look at the PasswordSafe file format. It can be found here (among other places): http://sourceforge.net/p/passwordsafe/git-code/ci/333dd9f23a... ECB mode is only used for the internal keys. The database records are encrypted in CBC mode, and there is an integrity authenticator HMAC as well. However, the format was designed in the days when Mac-then-encrypt was considered proper. So the authentication HMAC…
Yes, @tehjh on Twitter pointed this out. The CBC code is in Util.cpp, _readcbc; it appears to be length-delimited instead of padded, so there's probably another error oracle in the decoding of the length/type block.
Also: in PWSfileV3.cpp, are they HMAC'ing the IV?
This is interesting; we might be able to make an exercise out of it.
Re: KeePass – questionable security
#160Earlier quoted context omitted.
More about password safe: https://www.schneier.com/passsafe.html
Too bad it is hosted on SourceForge.
Password Gorilla is compatible with the PasswordSafe DB v3 file format, and is not hosted on SourceForge: