Multiple security flaws have been found in Revelation, a password manager for GNOME 2. Specifically: 1) It was found that Revelation limited effective password lengths to thirty two characters, which made it easier for context-dependent attackers to successfully conduct brute-force password guessing attacks, 2) It was found that Revelation did not iterate the particular passphrase through some of the SHA family of hashing algorithms, in order to derive the encryption key, which made it easier (in that scenario there were only 7 bits to vary on each character) for context-dependent attackers to successfully conduct dictionary based password guessing attacks. Upstream ticket: [1] http://oss.codepoet.no/revelation/issue/61/file-format-magic-string-version-mismatch Further references: [2] https://bugs.gentoo.org/show_bug.cgi?id=421571 [3] http://lists.fedoraproject.org/pipermail/devel/2012-June/168607.html [4] http://knoxin.blogspot.co.uk/2012/06/revelation-password-manager-considered.html [5] http://westhoffswelt.de/blog/0046_from_revelation_security_to_android_password_managers.html
CVE Request: [6] http://www.openwall.com/lists/oss-security/2012/06/18/1
Created revelation tracking bugs for this issue Affects: fedora-all [bug 833049] Affects: epel-5 [bug 833050]
The following two CVE identifiers have been assigned: http://www.openwall.com/lists/oss-security/2012/06/18/3 to the issues in question as follows: 1) CVE-2012-2742 one for the: "Revelation: Limits effective password length to 32 characters" issue, 2) CVE-2012-2743 one for the: "Revelation: Doesn't iterate the passphrase through SHA algorithm" issue.
Jan, Looks like the commits that are suppose to fix this landed about 5 hours ago in the upstream tree. Upstream is prepping a release for tomorrow. I'll push a new updates-testing package out into F16 and F17 as soon after upstream has the release out as I can. -jef
initial scratch build against rawhide with the upstream encryption subsystem patches. http://koji.fedoraproject.org/koji/taskinfo?taskID=4191839
(In reply to comment #4) > Jan, > > Looks like the commits that are suppose to fix this landed about 5 hours ago > in the upstream tree. Upstream is prepping a release for tomorrow. I'll > push a new updates-testing package out into F16 and F17 as soon after > upstream has the release out as I can. > > -jef Brilliant. Thank you for that, Jef.
It's been almost a month, I've seen no activity on this bug...
Sorry this bug wasn't linked to the update packages. packages are in updates-testing for F16 and F17. Packages are in rawhide. There is a lingering issue which gconf schema changes that causes the new revelation to not work correctly without manual intervention to delete the .gconf configs for revelation and restarting the user session. I haven't been able to nail down a complete fix for that and I can't get it to happen consistently on my test F16 and F17 machines. So the packages are lingering in updates-testing. -jef