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
MSF not writing run-time errors in a spool file. #18953
Comments
I believe that not logging this error out is intentional, the typical pattern is something like this
we're capturing the exception and using it to inform the user what option(s) failed to validate, since we're handling it there's not really a need for us to log it out If you can provide some more details on what you're trying to achieve though maybe we can help point you in the right direction? |
It was for some internal use which I can't disclose much about. But yeah, if that's intentional and can't be moved to logging, I can close this issue in that case. Thanks! |
Pull request: #18954 @kashyap-sodha If you're able to apply those changes locally, does that meet your expectations? |
Hey @adfoster-r7 That seems to be working fine. Thanks! |
Hi,
I'm trying to verify MSF runtime errors like
Msf::OptionValidateError
but it doesn't seem to be writing neither in the spool file nor inframework.log
.Steps to reproduce
How'd you, do it?
msfconsole
use auxiliary/scanner/ftp/ftp_version
This error does not get logged to
framework.log
regardless of the log level being set. LogMetasploit version
Framework: 6.3.27-dev
Console: 6.3.27-dev
The text was updated successfully, but these errors were encountered: