News for hackers. Stuff that matters.
Re:The most dangerous code in the world by tptacek on Thursday October 25, 2012 @12:36AM (#4696395)
Oh yeah? Interesting. Tell me, what is the point of checking to see if a certificate has a common name field in it but then not checking to see if that common name is related to the connection bearing the certificate? Make it clear for me, will you?
Re:The most dangerous code in the world by Natsu on Thursday October 25, 2012 @05:26AM (#4696903)
That option exists to punish those evil people who don't read the documentation.

I'm kidding... I think.

Re:The most dangerous code in the world by tptacek on Thursday October 25, 2012 @04:32PM (#4699421)
Of course, who it really punishes is the user.
Re:The most dangerous code in the world by Natsu on Friday October 26, 2012 @01:21AM (#4700960)
Some developers seem to believe that more options are always better, even if removing the bad options makes the software better and easier to use.