Skip to content
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

Fix: undo untested breaking changes from #1311 that change getErrorString #1714

Merged
merged 3 commits into from
Mar 18, 2024

Conversation

Marshall-Hallenbeck
Copy link
Contributor

@Marshall-Hallenbeck Marshall-Hallenbeck commented Mar 16, 2024

#1311 was untested and broke how NetExec (previously crackmapexec) handle errors. Ironically, the PR was intended to fix something for CME, but instead it broke how all nt_status errors were handled via getErrorString.

This PR reverts the changes to the getErrorString function, which is required for NetExec to be able to use Fortra's Impacket upstream. We need to use Fortra's Impacket to have NetExec packaged on Kali Linux, so please consider testing and merging this ASAP. Thank you!

…hange getErrorString for nt_status errors
@gabrielg5 gabrielg5 self-assigned this Mar 18, 2024
@gabrielg5
Copy link
Collaborator

Mistested #1311 and some unwanted changes were merged in master.

getErrorString should continue working as before.

Eventually we may want to check if self.error is in our dictionary to avoid raising an exception and handle that scenario with a custom unknown error message tuple.

@Marshall-Hallenbeck will merge this PR after you fix the suggestion.

thanks!!

Co-authored-by: Gabriel Gonzalez <[email protected]>
@gabrielg5 gabrielg5 merged commit 0d2b72a into fortra:master Mar 18, 2024
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants