there its no need to reimplement check as a boolean. doing so means that
there its no way to run the check command from the console.

http://www.offensive-security.com/metasploit-unleashed/Msfconsole_Commands#check
On May 22, 2013 10:48 PM, "sinn3r" <notifications@github.com> wrote:

> In modules/auxiliary/gather/coldfusion_pwd_props.rb:
>
> > @@ -43,7 +44,8 @@ def initialize(info = {})
> >
> >  		register_options(
> >  			[
> > -				Opt::RPORT(8500),
> > +				Opt::RPORT(80),
> > +				OptBool.new('CHECK', [false, 'Only check for vulnerability', false]),
>
> A check() makes sense before doing anything malicious to a target machine,
> so OptBool is perfect for that.
>
> To be honest, we lack consistency on this design decision -- we have
> modules that implement checks as actions, we also have some of them as
> complete separate modules... and without surprise, some are implemented as
> OptBool.
>
> Let me ask what other devs think....
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/rapid7/metasploit-framework/pull/1855/files#r4353643>
> .
>