Earlier quoted context omitted.
Cute - inserting the word 'professional' before rails dev, and then claiming to take security and code quality seriously! ROFL If a developer was professional, and cared about code quality and security, they would not use rails. Period.
Yeah! They'd use PHP! Or Java! Those never have any problems and their code-bases are always flawless . I'll take a bad Rails app any day over what people churn out in other platforms. I've seen Java apps so impenetrably opaque it's not even clear what it does. Rails is Rails. It's boring. It works. It's pretty hard to mangle the project so badly that you can't make sense of it. Unless, of course, you've got no idea…
A week with a Rails Security Strategy: More security, new habits
11–20 of 27 posts
Re: A week with a Rails Security Strategy: More security, new habits
#12Earlier quoted context omitted.
Cute - inserting the word 'professional' before rails dev, and then claiming to take security and code quality seriously! ROFL If a developer was professional, and cared about code quality and security, they would not use rails. Period.
Says the 8 hour old troll account.
Re: A week with a Rails Security Strategy: More security, new habits
#13I didn't even know there was such a thing as "Ruby on Rails Security".
To the people downvoting me: - http://www.cvedetails.com/product/22568/Rubyonrails-Ruby-On-... - http://www.cvedetails.com/vulnerability-list/vendor_id-12043...
Django: http://www.cvedetails.com/product/18211/Djangoproject-Django...
PHP: http://www.cvedetails.com/product/128/PHP-PHP.html?vendor_id...
JRE: http://www.cvedetails.com/product/19117/Oracle-JRE.html?vend...
.Net: http://www.cvedetails.com/product/2002/Microsoft-.net-Framew...
Re: A week with a Rails Security Strategy: More security, new habits
#14Re: A week with a Rails Security Strategy: More security, new habits
#15Earlier quoted context omitted.
Yeah! They'd use PHP! Or Java! Those never have any problems and their code-bases are always flawless . I'll take a bad Rails app any day over what people churn out in other platforms. I've seen Java apps so impenetrably opaque it's not even clear what it does. Rails is Rails. It's boring. It works. It's pretty hard to mangle the project so badly that you can't make sense of it. Unless, of course, you've got no idea…
The replacements in modern php were faster and more secure. But don't let your prejudice undo your argument.
Laravel has tried to push PHP in the right direction in a huge way, but it's not without its minor problems, either. Additionally, like any non-trivial code base it's had some vulnerabilities.
Now of course nobody uses Laravel, they just hand-roll, so the sorts of bugs you see in the PHP world are more pattern based (e.g. injection, XSS) than you'd see in a platform like Rails that is driven by convention.
Re: A week with a Rails Security Strategy: More security, new habits
#16Re: A week with a Rails Security Strategy: More security, new habits
#17Earlier quoted context omitted.
Cute - inserting the word 'professional' before rails dev, and then claiming to take security and code quality seriously! ROFL If a developer was professional, and cared about code quality and security, they would not use rails. Period.
Says the 8 hour old troll account.
Re: A week with a Rails Security Strategy: More security, new habits
#18Earlier quoted context omitted.
To the people downvoting me: - http://www.cvedetails.com/product/22568/Rubyonrails-Ruby-On-... - http://www.cvedetails.com/vulnerability-list/vendor_id-12043...
It's a complicated platform, but on the whole has a very good track record. Picking on it for having vulnerabilities without providing something in the way of a comparison is not very meaningful.
For example, all new gem releases should be signed and `HighSecurity` should be the policy but it's taken years to get very little progress. Changing to that policy would prevent entire classes of attacks, attacks that could subtly inject code into all sorts of apps in difficult-to-find ways. Large projects are still shipping unsigned gems, unsigned commits and unsigned tags. If RubyGems were hacked, progress might move slightly faster.
Re: A week with a Rails Security Strategy: More security, new habits
#19I didn't even know there was such a thing as "Ruby on Rails Security".
To the people downvoting me: - http://www.cvedetails.com/product/22568/Rubyonrails-Ruby-On-... - http://www.cvedetails.com/vulnerability-list/vendor_id-12043...
Re: A week with a Rails Security Strategy: More security, new habits
#20Earlier quoted context omitted.
It's a complicated platform, but on the whole has a very good track record. Picking on it for having vulnerabilities without providing something in the way of a comparison is not very meaningful.
It's imporant to pick out vulnerabilities and deficiencies compared to other projects to get them addressed, rather than only say nice things. However, the core issue is that people raising them are usually ignored until there's an embarrassing hack or demonstration (Homakov). For example, all new gem releases should be signed and `HighSecurity` should be the policy but it's taken years to get very little progress. C…
That being said, there's great services like GemCanary (https://gemcanary.com/) that will read your Gemfile and produce a list of vulnerable packages for you automatically. It'll even email you alerts when there's problems.
The security story in Rails might not be perfect, but at least there's reporting and tools.
Keep pushing for signed packages, though. Long overdue.