blob: cb0f52915606bffa2fcd336a9a6b7d6e27bdc2a8 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
|
{ buildGoModule
, fetchFromGitHub
, lib
}:
buildGoModule rec {
pname = "amass";
version = "3.18.2";
src = fetchFromGitHub {
owner = "OWASP";
repo = "Amass";
rev = "v${version}";
sha256 = "sha256-2HE+hzvEbM+68x3YJq8rIMCKAld9MLrCEuHBA4uuetI=";
};
vendorSha256 = "sha256-hYrv5z+9JY7gXkC4xQvko7qhwBtzywUy0TMqrlgqXb0=";
outputs = [ "out" "wordlists" ];
postInstall = ''
mkdir -p $wordlists
cp -R examples/wordlists/*.txt $wordlists
gzip $wordlists/*.txt
'';
# https://github.com/OWASP/Amass/issues/640
doCheck = false;
meta = with lib; {
description = "In-Depth DNS Enumeration and Network Mapping";
longDescription = ''
The OWASP Amass tool suite obtains subdomain names by scraping data
sources, recursive brute forcing, crawling web archives,
permuting/altering names and reverse DNS sweeping. Additionally, Amass
uses the IP addresses obtained during resolution to discover associated
netblocks and ASNs. All the information is then used to build maps of the
target networks.
Amass ships with a set of wordlist (to be used with the amass -w flag)
that are found under the wordlists output.
'';
homepage = "https://owasp.org/www-project-amass/";
license = licenses.asl20;
maintainers = with maintainers; [ kalbasit fab ];
};
}
|