You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/feature_request.md
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,11 @@
1
+
---
2
+
name: Feature request
3
+
about: Request a new feature or enhancement
4
+
title: ''
5
+
labels: ''
6
+
assignees: ''
7
+
8
+
---
1
9
**Please Describe The Problem To Be Solved**
2
10
(Replace This Text: Please present a concise description of the problem to be addressed by this feature request. Please be clear what parts of the problem are considered to be in-scope and out-of-scope.)
about: Update code to fix a bug or add an enhancement/feature
4
+
title: ''
5
+
labels: ''
6
+
assignees: ''
7
+
8
+
---
9
+
## Description
10
+
11
+
Please include a summary of the change and which issue is fixed, or what the enhancement does.
12
+
Please also include relevant motivation and context.
13
+
List any dependencies that are required for this change.
14
+
15
+
## Type of change
16
+
Please delete options that are not relevant.
17
+
-[ ] Bug fix (non-breaking change which fixes an issue)
18
+
-[ ] New feature (non-breaking change which adds functionality)
19
+
-[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
20
+
-[ ] This change requires a documentation update
21
+
-[ ] This requires a third party update (such as Impacket, Dploot, lsassy, etc)
22
+
23
+
## How Has This Been Tested?
24
+
Please describe the tests that you ran to verify your changes (e2e, single commands, etc)
25
+
Please also list any relevant details for your test configuration, such as your locally running machine Python version & OS, as well as the target(s) you tested against, including software versions
26
+
27
+
If you are using poetry, you can easily run tests via:
28
+
`poetry run python tests/e2e_tests.py -t $TARGET -u $USER -p $PASSWORD`
29
+
There are additional options like `--errors` to display ALL errors (some may not be failures), `--poetry` (output will include the poetry run prepended), `--line-num $START-$END $SINGLE` for only running a subset
30
+
31
+
## Screenshots (if appropriate):
32
+
Screenshots are always nice to have and can give a visual representation of the change.
33
+
If appropriate include before and after screenshot(s) to show which results are to be expected.
34
+
35
+
## Checklist:
36
+
37
+
-[ ] I have ran Ruff against my changes (via poetry: `poetry run python -m ruff check . --preview`, use `--fix` to automatically fix what it can)
38
+
-[ ] I have added or updated the tests/e2e_commands.txt file if necessary
39
+
-[ ] New and existing e2e tests pass locally with my changes
40
+
-[ ] My code follows the style guidelines of this project (should be covered by Ruff above)
41
+
-[ ] If reliant on third party dependencies, such as Impacket, dploot, lsassy, etc, I have linked the relevant PRs in those projects
42
+
-[ ] I have performed a self-review of my own code
43
+
-[ ] I have commented my code, particularly in hard-to-understand areas
44
+
-[ ] I have made corresponding changes to the documentation (PR here: https://github.com/Pennyw0rth/NetExec-Wiki)
std_parser.add_argument("--use-kcache", action="store_true", help="Use Kerberos authentication from ccache file (KRB5CCNAME)")
79
85
std_parser.add_argument("--log", metavar="LOG", help="Export result into a custom file")
80
86
std_parser.add_argument("--aesKey", metavar="AESKEY", nargs="+", help="AES key to use for Kerberos Authentication (128 or 256 bits)")
81
-
std_parser.add_argument("--kdcHost", metavar="KDCHOST", help="FQDN of the domain controller. If omitted it will use the domain part (FQDN) specified in the target parameter")
87
+
std_parser.add_argument("--kdcHost", metavar="KDCHOST", help="IP Address of the domain controller. If omitted it will use the domain part (FQDN) specified in the target parameter")
0 commit comments