which should be medium confidence warnings

which is a good thing

instead of "UnknownModel"

Also commit Rails 3 test file which I forgot, oops

make the check methods line up with the specific CVE numbers

Again, the check for this already exists, just need a test for it

check already exists, but no tests for it

and also SQL injection duplicates in views, because that
is incidentally also fixed

Again, the check for this already exists, just need a test for it

check already exists, but no tests for it

when target is a model

when target is a model

Add concept of a safe-ening method to mark hrefs as safe

Feature:
Warn when using unsafe hrefs.  This is a very specific case that as of now produces a ton of noise.  This came out of an xss vuln where the value was escaped but still vulnerable.

    link_to 'asdf', h(@scary)

where

    @scary = 'javascript:alert(1)'

or

    @scary = 'data:  # http://palpapers.plynt.com/issues/2010Oct/bypass-xss-filters/

This branch accomplishes slightly intelligent warnings by adding a new command line option to declare methods that make a string URL safe (unless there is already a standard one out there).  e.g.:

    $ brakeman . --url-safe-methods ensure_valid_protocol!

    link_to 'asdf', ensure_valid_protocol!(@scary, :javascript)

closes #44

for issue #32