We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Adversary lab outputs rules, but it gives no idea of how good they are.
In the example below, we were trying to differentiate traffic to google from traffic to github over HTTPS:
sudo ./client-cli rules example2 {"":{"byte_sequences":[{"action":"block","incoming":[0,0,22,3,1],"outgoing":[],"rule_type":"adversary labs"}],"name":"example2","target":"example2"}} {"":{"byte_sequences":[{"action":"block","incoming":[0,0,22,3,1],"outgoing":[0,0,22,3,3],"rule_type":"adversary labs"}],"name":"example2","target":"example2"}}
The rule just identifies the TLS handshake, and cannot tell the traffic apart. However, there's no indication of that.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Adversary lab outputs rules, but it gives no idea of how good they are.
In the example below, we were trying to differentiate traffic to google from traffic to github over HTTPS:
The rule just identifies the TLS handshake, and cannot tell the traffic apart. However, there's no indication of that.
The text was updated successfully, but these errors were encountered: