Open noraj opened 2 years ago
You are correct. Sorry; mis-read this.
This is not needed.
@noraj should it go in remove list?
should it go in remove list?
No. nuclei PKGBUILD should be updated instead. In a way to use nuclei-templates as described above.
Just to summarize:
nuclei-templates
as dependency in nucleiconfig.yml
should contain only those two mentioned lines? The mentioned link is not consistent anymore. It is the updated one: https://docs.projectdiscovery.io/tools/nuclei/running#nuclei-configRemove
nuclei-templates
as dependency in nuclei
The idea is quite the contrary. It's to make nuclei really use nuclei-templates
Also right now our package nuclei-templates is pretty useless and not needed as a dependency of nuclei.
Ok... I misled this statement
Also right now our package
nuclei-templates
is pretty useless and not needed as a dependency ofnuclei
. Why? Because since 2.4.0 nuclei is auto-downloading and updating the templates to~/nuclei-templates
and is not aware of what we deployed at/usr/share/nuclei-templates
.So to make the nuclei-templates install system wide taken into account by nuclei we should complexify the install steps :
config.yml
file (cf. https://nuclei.projectdiscovery.io/nuclei/get-started/#nuclei-config)disable-update-check: true
to disable automatic nuclei/templates update checktemplates: \n - /usr/share/nuclei-templates
nuclei -config /usr/share/nuclei/config.yaml "$@"
So the templates would not be downloaded once per user and making the user home messy.