Skip to content
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

Added TunnelBear VPN detection patterns. #1615

Merged
merged 1 commit into from
Jul 1, 2022
Merged

Conversation

utoni
Copy link
Collaborator

@utoni utoni commented Jul 1, 2022

Signed-off-by: Toni Uhlig matzeton@googlemail.com

Signed-off-by: Toni Uhlig <matzeton@googlemail.com>
@sonarqubecloud
Copy link

sonarqubecloud bot commented Jul 1, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@mmanoj
Copy link
Contributor

mmanoj commented Jul 1, 2022

@utoni

Do we need to add Packet communication patterns, like from first packet bytes, etc? or are DNS entries enough?

@utoni
Copy link
Collaborator Author

utoni commented Jul 1, 2022

@mmanoj

If you want to detected the DNS flow which may occur either before or not at all due to DoH/DoT, yes.
But more important is the VPN communication itself, be it via TLS, OpenVPN or something proprietary.

@utoni utoni merged commit bb72aa4 into ntop:dev Jul 1, 2022
utoni added a commit to utoni/nDPI that referenced this pull request Jul 1, 2022
Signed-off-by: Toni Uhlig <matzeton@googlemail.com>
@mmanoj
Copy link
Contributor

mmanoj commented Jul 2, 2022

@utoni
Thanks for the clarifications, I captured Ultraserf communication, and I will upload it to the original communication thread.

utoni added a commit that referenced this pull request Jul 2, 2022
Signed-off-by: Toni Uhlig <matzeton@googlemail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants