Replies: 1 comment
-
|
I have identified that a similar problem also exists on katana@v1.5.0 as that version's domain filter is the domain name searched in the line. For example using -fs dn with a provided domain like DOM.tld, anything with DOM in the FQDN is matched. DOM.onmicrosoft.com for example. Which should be OUT of scope. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello! I recently updated my processes from Katana 1.5.0 to the latest 1.6.1 and have started seeing wildly different results. I believe this is because the -fs dn flag is not being respected.

Beta Was this translation helpful? Give feedback.
All reactions