-
Notifications
You must be signed in to change notification settings - Fork 744
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
add new protocols #22
Comments
QUIC & SOCKS analyzers are already in the plans, though I haven't found the time to work on them yet. As for the rest... I believe these are cryptocurrency mining pools and not network protocols? |
The idea of this project is that we provide protocol analyzers and a rule engine so that users can use them to create any rule they need. For example, to block Google, we don't provide a "Google analyzer", we provide a TLS analyzer that can extract the domain from SNI, so a user can write a rule to match "google.com" or whatever they want. If we want to have the ability to block mining pools (which I agree is definitely useful), we need analyzers for cryptocurrency protocols. |
wireguard |
But these are very necessary to prevent users from mining in vps, and all mining protocols can be proactively probed, which is relatively simple to implement. |
Also the bittorrent protocol |
1.Socks5
2.Socks4
3.Socks4A
4.QUIC
5.Stratum
6.GBT
7.BetterHash
8.NiceHash
9.MEP
The above tests are relatively simple and require relatively large amounts of new ones.
The text was updated successfully, but these errors were encountered: