4 ms·
This is nonsense, of the class of nonsense that regularly comes up on Raymond Chen's blog with the title, "It rather involved being on the other side of this ai
by geofft 10y ago
This is nonsense, of the class of nonsense that regularly comes up on Raymond Chen's blog with the title, "It rather involved being on the other side of this airtight hatchway." https://blogs.msdn.microsoft.com/oldnewthing/20141217-00/?p=43373 https://blogs.msdn.microsoft.com/oldnewthing/20141217-00/?p=... is a good example.
Specifically, the argument here is that SipHash is insecure because you can read the private key out of the process's memory, or you can convince the process to dump its private key by setting an environment variable.
But anyone who can read your process memory or set environment variables has a million easier ways to attack your process. The thing SipHash is protecting you from is not yourself. It's protecting you from attackers on the network, that is, not on your machine, giving you malicious data to abuse your hash table. Nobody can protect you from attackers who can run opcodes in your Perl VM.
In the kernel, there's no such thing as a Perl VM or environment variables. There is a such thing as private kernel memory, and it is kept secret from userspace and (of course) from other people on the network, for very good reason. If you can read kernel memory, or execute kernel code, you have already won.
This is like a military officer saying, "These improved missile launchers don't keep us safe. There's a secret code to launch the missiles, and if the enemy happens to captures our capital and breaks into our military installations and kidnaps the president and steals the launch codes, they can launch our own missiles against us."
- zx2c4 10y agoWell put. I'm pretty sure "rurban" is a well known Internet troll with a reputation for spreading non-sense like this.
- geofft 10y agoOh, apparently so! https://twitter.com/szbalint/status/795992687556042752 https://twitter.com/szbalint/status/795992687556042752 Making weird but reasonable-sounding claims about cryptanalysis of SipHash seems to be his MO. More Googling finds an amazing history of poorly-reasoned complaints about Perl's adoption of SipHash. Masterful trolling, rurban. We all took you seriously.