Working more on VersionCheck
Fixing hidden chars
Continuing integrating new version check into dependency check
Most all the integration is over and CVE-2014-0080 is completed. However
there are some issue to fix in regression tests...
Introduced a save_major flag. The idea is to handle this way different
"safe versions" with different major release number
Removed stuff from basic check.
Save minor and major fixes are now in Dependency check, passing them to
VersionCheck automagically.
spec for dependency check is back to green
Initial VersionCheck usage for Ruby interpreter version check
Renamed spec files to follow convention
cve_2014_0082 is now green again
Working on CVE-2011-2930
Merge branch 'issue_34_MVC_and_Ruby_deprecation_warning' of github.com:codesake/codesake-dawn into issue_34_MVC_and_Ruby_deprecation_warning

Conflicts:
	lib/codesake/dawn/kb/version_check.rb
CVE-2011-2930 is green again
Removed a non sense test. If a version is safe, I don't care about other
releases... it's safe
Dependency check is green again after introducing an helper to check
detected version if explicitly cited in safe version array
CVE-2011-3187 is green again. With the new VersionCheck I have to
declare not to consider earlier version number as vulnerable. An issue
can be just on 3.x.x rails tree and not in 2.3.x one
Working on CVE-2011-4319 spec@35
CVE-2011-4319 back to green
I removed a non sense rspec test in CVE-2011-5036. If rack version 1.1.3
is in the safe list, why on earth it should be marked as vulnerable?
CVE-2012-1098 is green again and save_[minor|major]_fixes is renamed in
save_[minor|major]_fix