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: README.md
+16-18Lines changed: 16 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -123,28 +123,26 @@ options:
123
123
## Installation
124
124
There are multiple ways to install the tool. Either the tool comes as a package with your Linux distribution or you need to do a manual install.
125
125
126
-
### Automatic Installation
127
-
I'm aware of the following Linux distributions which package the tool:
128
-
129
-
#### Kali Linux
126
+
### Kali Linux
130
127
```console
131
128
# apt install enum4linux-ng
132
129
```
133
130
134
-
#### Archstrike
135
-
131
+
### Archstrike
136
132
```console
137
133
# pacman -S enum4linux-ng
138
134
```
139
135
140
-
####NixOS
136
+
### NixOS
141
137
(tested on NixOS 20.9)
142
-
143
138
```console
144
139
$ nix-env -iA nixos.enum4linux-ng
145
140
```
146
-
### Manual Installation
147
-
#### Dependencies
141
+
142
+
## Manual Installation
143
+
If your Linux distribution does not offer a package, the following manual installation methods can be used instead.
144
+
145
+
### Dependencies
148
146
The tool uses the samba clients tools, namely:
149
147
- nmblookup
150
148
- net
@@ -163,29 +161,29 @@ For a faster processing of YAML (optional!) also install (should come as a depen
163
161
164
162
Some examples for specific Linux distributions installations are listed below. Alternatively, distribution-agnostic ways (python pip, python virtual env and Docker) are possible.
165
163
166
-
####Linux distribution specific
164
+
### Linux distribution specific
167
165
For all distribution examples below, LibYAML is already a dependency of the corresponding PyYaml package and will be therefore installed automatically.
Remember you need to still install the samba tools as mentioned above. In addition, make sure you run ```source venv/bin/activate``` everytime you spawn a new shell. Otherwise the wrong Python interpreter with the wrong libraries will be used (your system one rather than the virtual environment one).
0 commit comments