News for hackers. Stuff that matters.
Re:Key for chromium's encrypted cookies store in Linux is “p... by userbinator on Sunday June 14, 2015 @09:40AM (#9714843)
I guess a lot of others are also wondering, "What's the point?"

If an attacker can read the file the cookies are stored in, you have already lost.

It even mentions "obfuscation" - which might be a slight obstacle if this was closed-source - but Chromium is open-source.

Re:Key for chromium's encrypted cookies store in Linux is “p... by bbrazil on Sunday June 14, 2015 @09:45AM (#9714852)
Obfuscation is still useful.

For example if a sysadmin is investigating a problem they're less likely to accidentally see a user's data in human-readable form, it also provides a level of defence against unsophisticated attackers.

[deleted]
Re:Key for chromium's encrypted cookies store in Linux is “p... by detaro on Sunday June 14, 2015 @10:13AM (#9714965)
They are talking about obfuscating the stored data, not the code.
Re:Key for chromium's encrypted cookies store in Linux is “p... by justinschuh on Sunday June 14, 2015 @10:32AM (#9715036)
The obfuscation isn't really intentional IIRC. It's an artifact of the assumption that a proper base credential will be available from either libsecret, Gnome Keyring, or KDE Wallet. The fixed key is just a placeholder that gets used when none of those secure mechanisms is installed on the system. Although, that file has a number of outdated comments, which add to the confusion.