Yeah, but that's slock.it (not the Ethereum foundation) who were the same ones who found a similar bug in their code elsewhere are just plastered over it while

Yeah, but that's slock.it (not the Ethereum foundation) who were the same ones who found a similar bug in their code elsewhere are just plastered over it while claiming that there was no risk. They have a history of being cocksure about their programming, and didn't even think to take a quick look at the rest of their code. It's unsurprising that they're being scuzzy about this too, and I think the Ethereum community is pretty fed up with them at this point :P