-
Notifications
You must be signed in to change notification settings - Fork 553
Allow for specifying specific users to kerberoast #831
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
Conversation
What do you think about adding a universal --users flag that could be used across For example:
|
I think that might be confusing with the |
Signed-off-by: Marshall Hallenbeck <[email protected]>
I mentioned --user because in SMB we already use it for --ntds. The main point is just to have a universal targeting flag, whatever the final name is, it could very well be --target or something similar |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR adds functionality to allow users to specify specific users for kerberoasting attacks, rather than targeting all available users. The implementation allows users to provide a list of usernames either directly via command line arguments or through a text file.
- Adds
--kerberoast-users
argument to specify target users for kerberoasting - Refactors duplicate
get_conditional_action
function to a shared location - Implements conditional argument requirement where
--kerberoast-users
requires--kerberoasting
Reviewed Changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 3 comments.
Show a summary per file
File | Description |
---|---|
nxc/helpers/args.py | Adds shared get_conditional_action function for argument dependencies |
nxc/protocols/ldap/proto_args.py | Adds --kerberoast-users argument with conditional requirement on --kerberoasting |
nxc/protocols/ldap.py | Implements logic to filter kerberoast targets based on specified users |
nxc/protocols/ssh/proto_args.py | Removes duplicate get_conditional_action function |
nxc/protocols/smb/proto_args.py | Removes duplicate get_conditional_action function |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
Co-authored-by: Copilot <[email protected]> Signed-off-by: Marshall Hallenbeck <[email protected]>
Changed context.log.fail to context.log.highlight when if tampered = true
Co-authored-by: Copilot <[email protected]> Signed-off-by: Marshall Hallenbeck <[email protected]>
uhh what happened here? Why is the commit history so messed up? |
I have no idea. I'll have to fix it. |
Nuking this PR, the branch got entirely feffed. |
Description
Allows users to specify a list of users to Kerberoast via the command line or text file.
Type of change
Insert an "x" inside the brackets for relevant items (do not delete options)
Setup guide for the review
Shouldn't need anything other than kerberoastable users in your lab - just define them via
--kerberoast-users
and list them either by--kerberoast-users user1 user2 user3
or--kerberoast-users kerb-users.txt
Screenshots (if appropriate):
I can provide some if needed
Checklist:
Insert an "x" inside the brackets for completed and relevant items (do not delete options)
poetry run python -m ruff check . --preview
, use--fix
to automatically fix what it can)tests/e2e_commands.txt
file if necessary (new modules or features are required to be added to the e2e tests)