Vulnerability evidence is now written on standard output.
Entering development cycle for version 1.0.1
Owasp Ruby on Rails cheatsheet is now managed as separated bunch of
security checks.

This is done since a lot of persons feel the need of imrpoved clarity
when dealing with quality checks output.
Added the avoid_comments flay telling the pattern matching check to
ignore lines starting with the '#' character. It must set to true inside
the check. Already done for RoR Cheatsheet Command Injection check.

This should fix issue #22
The previous commit fixes issue #22.
Now you can specify evidences in check initialization. This is useful
when you need a fixed evidence not depending on the context itself.
Owasp RoR cheatsheet check about session storage in a database now it
has a better message explaining what went wrong.
Added a comprehensive message, and reverted the negative_flag... yes
this is bug here...
Reverted the vulnerability print as logger.err to have a red colored
string. This causes dawn to print the vulnerability on STDERR, please
take care of it when using dawn in a shell script
Fixing issue #21. Added mitigation string for existing RoR security
cheatsheet tests. This would lead to a better and more comprehensive
output for rails apps.
Added two stuff I want to introduce in upcoming 1.1.0 version
This commit eventually fixes issue #21.
Merge branch 'issue_21_unpack_ror_cheatsheet' into development
Development branch version is 1.1.0
Merge branch 'issue_21_unpack_ror_cheatsheet'
Version 1.0.1
Version 1.0.1 announcement text
Added a date in changelog
Development branch version is 1.1.0
Merge branch 'development' of github.com:codesake/codesake-dawn into development