News for hackers. Stuff that matters.
Re:Rack - Important Security Upgrade by static_typed on Friday February 08, 2013 @03:17PM (#5189860)
Members of our team have been receiving recruiter calls for the past few days - it seems a few places running Rails apps are on the lookout for developers to help secure and update their apps. At least one has apparently experienced the awesomeness of the Ruby way, and had their servers compromised.

Make the decision to move onto Python seem more correct every day.

Re:Rack - Important Security Upgrade by rst on Friday February 08, 2013 @04:31PM (#5190263)
The Python world has had very, very similar problems. Two popular Django add-ons (piston and tastypie) had remote code execution vulnerabilities due to the exact same cause as the recent Rails RCE vulns: insecure deserialization of YAML.

See https://www.djangoproject.com/weblog/2011/nov/

This isn't an exactly equivalent situation, since this wasn't a problem with the core Django framework --- but that's in part because the core Django framework does less. Functionality similar to these extensions is bundled with Rails.

Re:Rack - Important Security Upgrade by heartbreak on Friday February 08, 2013 @03:45PM (#5190025)
It is impossible to write insecure web applications in Python. /s
Re:Rack - Important Security Upgrade by static_typed on Friday February 08, 2013 @04:23PM (#5190230)
We don't seem to see the Python community embrace magic and shiny quite so much as in Ruby. That alone seems to help.
Re:Rack - Important Security Upgrade by heartbreak on Friday February 08, 2013 @05:35PM (#5190532)
That is subjective. What is "magic and shiny" and who is doing this embracing? "Magic and shiny" is embraced more in Sinatra than in Django? "Magic and shiny" is, by your definition, a security vulnerability?