Highlights 2014-04-14 13:45
The next gotofail?
"correct cases of code occuring directly after goto/break/returnok miod@ guenther@"
I have no indication that this would lead to a genuine vulnerability, but christ the code-smell
The Entropy is 2014-04-14 13:43:13
"So the OpenSSL codebase does "get the time, add it as a random seed"in a bunch of places inside the TLS engine, to try to keep entropy high.I wonder if their moto is "If you can't solve a problem, at least tryto do it badly".ok miod"
Apparently OpenSSL is adding the time to their entropy pool? But attackers can easily guess the time that your server thinks it is, so is this actually breaking things, or is the entropy pool sufficiently resistant to these kinds of boo-boos?
Highlights 2014-04-15 12:04
FOR GLORY"Send the rotIBM stream cipher (ebcdic) to Valhalla to party for eternity with the bearded ones... some API's that nobody should be using will dissapear with this commit."
I love this guy's sense of humor. I didn't even know there was a "rotIBM" stream cipher. I'm sure it must've undergone a rigorous cryptanalysis, and IBM have never gotten in bed with nefarious government agencies. Oh, and pigs fly.
Header"strncpy(d, s, strlen(s)) is a special kind of stupid. even when it's right,it looks wrong. replace with auditable code and eliminate many strlen calls to improve efficiency. (wait, did somebody say FASTER?) ok beck"
I think the commit message says it all.