flag -nf not working in v5.0.1

[bjar]

Hi!
It seems like the -nf flag hasn't been implemented in version 5.

$ amass enum -d fredagskakan.se
$ amass subs -d fredagskakan.se -show
fredagskakan.se
www.fredagskakan.se
api.fredagskakan.se

$ cat nf_file
vote.fredagskakan.se

$ amass enum -d fredagskakan.se -nf nf_file
$ amass subs -d fredagskakan.se -show
fredagskakan.se
www.fredagskakan.se
api.fredagskakan.se

In the last enum call I expect vote.fredagskakan.se to be picked up.

[ParthAggarwal16]

I looked into why the -nf flag isn’t working in v5.
From tracing the flow, the negative filter names are parsed, but they don’t go through the asset ingestion path, so they never get stored in the engine/database. In contrast, inputs provided via -df do go through full ingestion, which is why they behave correctly.
I’m planning to route -nf inputs through the same ingestion pipeline as -df, while marking them as negative filters so the engine can apply them appropriately.

[686f6c61]

Hey! I've investigated this issue and submitted a fix in #1102.

The root cause was that ProvidedNames from -nf was never being processed by makeAssets(), and the blacklist from -blf was never passed to the engine scope.

The PR includes unit tests and has been manually verified. Let me know if you have any questions!

[ParthAggarwal16]

Thanks for putting together this fix — this approach is definitely cleaner and more aligned with how the ingestion flow is evolving.
I had worked on an earlier attempt in this area as well, so it’s helpful to see this direction land. Appreciate you taking the time to address this properly.
Happy to help test this further or assist with any follow-up improvements if needed — just let me know!