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
+28-16Lines changed: 28 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -117,7 +117,26 @@ optional arguments:
117
117
-oA OUT_FILE Writes output to YAML and JSON file (extensions are added automatically)
118
118
```
119
119
120
-
## Installing dependencies
120
+
## Installation
121
+
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.
122
+
123
+
### Automatic Installation
124
+
I'm aware of the following Linux distributions which package the tool:
125
+
126
+
#### Archstrike
127
+
128
+
```console
129
+
$ pacman -S enum4linux-ng
130
+
```
131
+
132
+
#### NixOS
133
+
(tested on NixOS 20.9)
134
+
135
+
```console
136
+
$ nix-env -iA nixos.enum4linux-ng
137
+
```
138
+
### Manual Installation
139
+
#### Dependencies
121
140
The tool uses the samba clients tools, namely:
122
141
- nmblookup
123
142
- net
@@ -136,36 +155,29 @@ For a faster processing of YAML (optional!) also install (should come as a depen
136
155
137
156
Some examples for specific Linux distributions installations are listed below. Alternatively, distribution-agnostic ways (python pip, python virtual env and Docker) are possible.
138
157
139
-
### Linux distribution specific
158
+
####Linux distribution specific
140
159
For all distribution examples below, LibYAML is already a dependency of the corresponding PyYaml package and will be therefore installed automatically.
(tested on Kali Linux 2020.1, recent Debian (e.g. Buster) or Ubuntu versions should work, for Ubuntu 18.04 or below use the Docker or Python virtual environment variant)
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