-
Notifications
You must be signed in to change notification settings - Fork 13.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
force mixin to utilize ruby_smb
#17370
Conversation
When refactored recently the new code expects a `RubySMB` object this ensures the client returned meets that expectation.
Confirmed the Metasploitable 2 output is what is expected:
|
Before:
|
Seems to still be working with just SMBv1 enabled though we do get a bit of a funny message:
|
Following shows only SMBv1, then no protocol support, then SMB3 and SMBv2 support. I'll try just SMBv2 support next and if that works then I'll land this:
|
Release NotesA bug has been fixed in the |
When refactored recently the new code expects a
RubySMB
object this ensures the client returned meets that expectation.The following stack trace can occur (seen on macOS dev env):
Verification
List the steps needed to make sure this thing works
msfconsole
use auxiliary/scanner/smb/smb_enumshares