News for hackers. Stuff that matters.

A comment on Bug #9424: ruby 1.9 & 2.x has insecure SSL/TLS client defaults.

Re:Bug #9424: ruby 1.9 & 2.x has insecure SSL/TLS client def... by steveklabnik on Tuesday January 21, 2014 @03:11PM (#7097971)
There's been a lot of anger around Twitter on this. I've also seen a lot of people cherry-picking a non-native speaker's words out of context too. Specifically, "Ruby is not a project for security."

That doesn't mean that this bug is not important, or that the Ruby team's decision as it currently stands is a good one. But it's a complex issue.

[ Parent | on HN ]
Re:Bug #9424: ruby 1.9 & 2.x has insecure SSL/TLS client def... by coherentpony on Tuesday January 21, 2014 @03:21PM (#7098043)
If someone gave me that sentence, I wouldn't know whether the person that wrote it was a native speaker or not.
[ Parent | on HN ]
Re:Bug #9424: ruby 1.9 & 2.x has insecure SSL/TLS client def... by steveklabnik on Tuesday January 21, 2014 @03:24PM (#7098072)
Exactly. And it implies something different than what was meant if you read the surrounding context.
[ Parent | on HN ]
Re:Bug #9424: ruby 1.9 & 2.x has insecure SSL/TLS client def... by insecure_ruby on Tuesday January 21, 2014 @03:51PM (#7098262)
"It's a complex issues" == Ruby Security Fails again.

It is a crackers dream that so much Ruby code is being exposed to the web these days. Such low hanging fruit. Even the script kiddies laugh at the ease of compromise.

Sigh.

[ Parent | on HN ]
Re:Bug #9424: ruby 1.9 & 2.x has insecure SSL/TLS client def... by steveklabnik on Tuesday January 21, 2014 @03:56PM (#7098299)
A throwaway troll account, how novel.
[ Parent | on HN ]