Added Pandora FMS RCE and SQLi module
Implemented @jlee-r7 requested changes
Pull the copy-pasted sqli into a method
Pull the copy-pasted verification into a method
auth_succeeded? is a better name for this method
Also extract admin hash if password auth failed
Make the password hash stand out as more important
Merge pull request #1 from jlee-r7/land-2985-pandorafms-sqli

Improvements for PandoraFMS SQLi module
New module to build wordlist for use by JtR, oclhashcat, etc generated by pulling info from multiple Active Directory fields
corrections based on feedback
Merge branch 'master', remote-tracking branch 'upstream/master'
Fail before suite if more than 1 thread exists

MSP-11147

Detect thread leaks in a `before(:suite)` configured by
`Metasploit::Framework::Spec::Threads::Suite.configure!` and fail if any
leaks are found.
Log caller for each Thread.new for `rake spec`

MSP-11147
Merge branch 'feature/MSP-11130/metasploit-framework-spec-constants' into feature/MSP-11147/thread-leak-detection

MSP-11147

Merge to get framework instance cleanup, which should clean up a lot of
thread leaks too.

Conflicts:
	Rakefile
	lib/metasploit/framework/spec.rb
	spec/spec_helper.rb
Remove prior log/metasploit/framework/spec/threads/suite.log

MSP-11147
Check that threads/suite.log exists before reading

MSP-11147

Even with leaked threads, there may be no log if the suite is run
without `rake spec`, such as when `rspec` is used directly to run a
subset of specs.
Tell use to run with `rake spec` to see Thread.new caller

MSP-11147

If the log isn't available, tell the user to rerun with `rake spec`
instead of printing nothing after the `:\n`, which looks incomplete.
Fix multiline string indentation

MSP-11147
Remove empty define_task

MSP-11147
Give Threads UUIDs for spec run so caller can be correlated

Have 'metasploit/framework/spec/threads/suite/logger' generate a UUID
for each Thread.  This UUID is printed on the "BEGIN Thread.new caller"
line and is assigned as a thread-local variable,
'metasploit/framework/spec/threads/logger/uuid'.  In `after(:suite)`,
the log can be parsed to map the caller back to each UUID and then only
the UUID of the still existing threads is used to look up the caller and
print their stacktraces.  This means only leaked threads callers will be
printed.