-
-
Notifications
You must be signed in to change notification settings - Fork 15.4k
amass: init at 2.8.3 #50490
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
amass: init at 2.8.3 #50490
Conversation
ab61802
to
f2a99aa
Compare
Success on aarch64-linux (full log) Attempted: amass Partial log (click to expand)
|
Success on x86_64-linux (full log) Attempted: amass Partial log (click to expand)
|
There seems to be v2.8.3 already on https://github.com/OWASP/Amass/releases |
@c0bw3b yes I saw that but v2.8.3 does not compile so I went with the latest release instead of the latest tag. |
f2a99aa
to
07b8e9d
Compare
07b8e9d
to
94ee915
Compare
Success on aarch64-linux (full log) Attempted: amass Partial log (click to expand)
|
Success on x86_64-linux (full log) Attempted: amass Partial log (click to expand)
|
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.
$ ./result-bin/bin/amass -version
version 2.8.3
$ ./result-bin/bin/amass -v -ip -brute -min-for-recursive 3 -d somedomain.tld
[...]
OWASP Amass v2.8.3 https://github.com/OWASP/Amass
--------------------------------------------------------------------------------
44 names discovered - api: 15, scrape: 11, brute: 1, dns: 2, cert: 15
--------------------------------------------------------------------------------
Running great. I wondered if we should ship the wordlists with it but it would increase the closure size significantly and by default if -brute
is passed the tool will just use https://raw.githubusercontent.com/OWASP/Amass/master/wordlists/namelist.txt
@c0bw3b thx for merging! w.r.t the wordlist, we could write a wrapper around the binary to download the wordlist from master and caches it by the commit hash somewhere in XDG_CACHE? That way we always get the freshest set and the closure size would not increase by more than the wrapper itself. |
Humm XDG_CACHE_HOME is user-specific and we want to share an identical set of wordlists among users. There is XDG_DATA_DIRS maybe... The nix way would really be to install it into |
@c0bw3b Perhaps we can bring that wordlist into the source code |
Oh hey! nice to see the original author here :) (btw nice tool) For you upstream I guess it's good to keep the wordlists as separate data. Plus it allows distro packagers to choose whether they want to ship it or not (or just a subset of it). Another random idea: ship the wordlists compressed (.txt.gz) and |
Yes I was thinking reading the compressed text file directly at runtime from the Go code. |
@kalbasit I'd be happy to receive your contribution. Thank you! |
@caffix thx for merging owasp-amass/amass#56! @c0bw3b should I simply put the wordlist under |
There is multiple wordlists and I think we should let the user decides when to use one, and which one. You can explain this in |
Motivation for this change
Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)nix path-info -S
before and after)