hypnosec writes “Linus Torvalds, in response to a petition on Change.org to remove RdRand from /dev/random, has lambasted the petitioner by called him ignorant for not understanding the code in Linux Kernel. Kyle Condon from UK raised a petition on Change.org to get Linus to remove RdRand from /dev/random in a bid “to improve the overall security of the linux kernel.” In his response, Torvalds asked the Condon and the supports of the petition to gain an understanding of Linux drivers, cryptography and then “come back here and admit to the world that you were wrong.” Torvalds stressed that kernel maintainers knew what they were doing and the petitioner didn’t. Torvalds, in a similar outburst just yesterday, hoped that “ARM SoC hardware designers all die in some incredibly painful accident.” This came in response to a message from Kevin Hilman when he noted that there were quite a few conflicts in the ARM SoC pull request for Linux 3.12, which were a result of the platform changes conflicting with driver changes going in to the V4L tree.”… hypnosec writes “Linus Torvalds, in response to a petition on Change.org to remove RdRand from /dev/random, has lambasted the petitioner by called him ignorant for not understanding the code in Linux Kernel. Kyle Condon from UK raised a petition on Change.org to get Linus to remove RdRand from /dev/random in a bid “to improve the overall security of the linux kernel.” In his response, Torvalds asked the Condon and the supports of the petition to gain an understanding of Linux drivers, cryptography and then “come back here and admit to the world that you were wrong.” Torvalds stressed that kernel maintainers knew what they were doing and the petitioner didn’t. Torvalds, in a similar outburst just yesterday, hoped that “ARM SoC hardware designers all die in some incredibly painful accident.” This came in response to a message from Kevin Hilman when he noted that there were quite a few conflicts in the ARM SoC pull request for Linux 3.12, which were a result of the platform changes conflicting with driver changes going in to the V4L tree.”

Read more of this story at Slashdot.






Read more http://rss.slashdot.org/~r/Slashdot/slashdot/~3/mjnTzwKUqxM/story01.htm