Add CVE-2013-0634: Adobe Flash Player 11.5 memory corruption
Fix bugs
SSH user enumeration script
Add CVE 2006-5229 reference
Add Oracle Demantra 2013-5795 (Database Credentials Retrieval)
Remove the broken lorcon module set

None of the lorcon / lorcon2 modules have been functional for a long
time, due to the lack of a "Lorcon" gem. It's unclear where it went.

I'm happy to include it and get these working again, but until someone
comes up with some functional code (hint: 'gem install' doesn't work) I
don't see any reason to keep shipping these.

Is there some trick people are doing to make these work? As far as I can
see, they are broken by default.

````
msf auxiliary(wifun) > show options

Module options (auxiliary/dos/wifi/wifun):

   Name       Current Setting  Required  Description
   ----       ---------------  --------  -----------
   CHANNEL    11               yes       The initial channel
   DRIVER     autodetect       yes       The name of the wireless driver
for lorcon
   INTERFACE  wlan0            yes       The name of the wireless
interface

msf auxiliary(wifun) > run

[*] The Lorcon2 module is not available: cannot load such file --
Lorcon2
[-] Auxiliary failed: RuntimeError Lorcon2 not available
[-] Call stack:
[-]
/home/todb/git/rapid7/metasploit-framework/lib/msf/core/exploit/lorcon2.rb:67:in
`open_wifi'
[-]
/home/todb/git/rapid7/metasploit-framework/modules/auxiliary/dos/wifi/wifun.rb:29:in
`run'
[*] Auxiliary module execution completed
````
Get rid of requires, too
Don't try to be too helpful

John cares not one whit how many colons are in a hash line, only that
there are enough for the format (at least 2 for regular /etc/passwd, at
least 3 for NTLM, etc). So there is no simple way to programmatically
determine whether a password had a colon or there was just an extra on
the end of the original hash line.

[MSP-9778]
See #2515
Refactor jtr_linux copy pasta

Move it to a nifty method
Micro optimizations for jtr_linux
More refactor on jtr_linux

Reducing complexity in `run` makes modules easier to read
Update to include SSL Version 3 protocol

SSL Version 3 will also respond to this and a server configured to respond to SSL version 3 but not TLS will show false negative without this option (proven).  May need to update cipher suites to include this option.
Updated hash value to SSLv3

Tested and working on server that has SSLv3 only enabled
Fix intendation
Bump version to 4.9.2
Update spec to reflect the correct version.
Merge release back into master
Land #3241 back into master
Land #3243, merge release back into master
Encourage use of the installer for users.