Paolo Perego

This part is about the old Orizon implementation. You can try to give more memory to java interpreter

This is odd. This is an error fixed last year (or it was supposed to). Can you please tell me the exact gem install command are you issuing ?

Guys @twmills @nicolasmery @phspies ... can you share more details about the error. I need to know details about your env (ruby version, gem version, os)

@Allevon412 you can check the dependencies for known issues with the -G flag specifying the Gemfile.lock path

I'll postpone LanguageCheck in next major release. Of course this will be moved in the future Codesake::Dawn::Core namespace I'm going to introduce when 2.0 development will start. There are a...

This is an issue #41 duplicate. I'm going to improve this check in next major

I'll postpone XSS detection for Ruby on Rails applications in next major release. There are a lot of changes actually (March 26, 2014) in development I'd like to push to...

Hi guys, I'll double check how rails 4 handle those headers and eventually I'll disable the check for rails version >=4

Because I didn't disable check family for rails 4.x automagically yet. In next version, 1.1.0 you can disable the family with `--disable-owasp-ror-cheatsheet`

With --disable-owasp-ror-cheatsheet you disable (or you should :-)) all Owasp RoR Cheatsheet checks. So the whole family On 4 April 2014 14:30, Justin Coyne [email protected] wrote: > It's not the...