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.
Land #3245, installers are for users
Land #3242, SSLv3 support
Added feature to dump to file leaked memory
Fixed conflict and used OptRegexp type for pattern
fixed conflicts, used OptRegexp for pattern
- Rubbish that was left dangling here around
Fixed store on file option