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

Bittorrent: improve detection of UTPv1 #2259

Merged
merged 1 commit into from
Jan 12, 2024

Conversation

IvanNardi
Copy link
Collaborator

@IvanNardi IvanNardi commented Jan 12, 2024

  • fix header length check: we must take into account optional extension header
  • it seems the check on UTPv1 header is weak only in the DATA case: wait for multiple packets only in that case

@IvanNardi IvanNardi requested a review from utoni January 12, 2024 12:49
@IvanNardi
Copy link
Collaborator Author

IvanNardi commented Jan 12, 2024

The endianess issue is unrelated to these changes (see #2260)
Since I don't have time to look into that (see #1828 for tracking the issue), I remove the new trace: it is kind of cheating, but I don't want to have failures on the CI...

* fix header length check: we must take into account optional extension
header
* it seems the check on UTPv1 header is weak only in the DATA case: wait
for multiple packets only in that case
Copy link

sonarcloud bot commented Jan 12, 2024

Quality Gate Passed Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

@0xA50C1A1
Copy link
Contributor

0xA50C1A1 commented Jan 12, 2024

The endianess issue is unrelated to these changes (see #2260) Since I don't have time to look into that (see #1828 for tracking the issue), I remove the new trace: it is kind of cheating, but I don't want to have failures on the CI...

Btw, what was the problem? I've got a s390x Alpine Linux VM, so I guess I can tinker with this stuff at my leisure.

@IvanNardi
Copy link
Collaborator Author

The endianess issue is unrelated to these changes (see #2260) Since I don't have time to look into that (see #1828 for tracking the issue), I remove the new trace: it is kind of cheating, but I don't want to have failures on the CI...

Btw, what was the problem? I've got a s390x Alpine Linux VM, so I guess I can tinker with this stuff at my leisure.

The pcap attached in #2260 returns different results only on s390x CI test

@0xA50C1A1
Copy link
Contributor

The endianess issue is unrelated to these changes (see #2260) Since I don't have time to look into that (see #1828 for tracking the issue), I remove the new trace: it is kind of cheating, but I don't want to have failures on the CI...

Btw, what was the problem? I've got a s390x Alpine Linux VM, so I guess I can tinker with this stuff at my leisure.

The pcap attached in #2260 returns different results only on s390x CI test

Ok, I'll create a PR when I figure out what's wrong.

@IvanNardi
Copy link
Collaborator Author

The endianess issue is unrelated to these changes (see #2260) Since I don't have time to look into that (see #1828 for tracking the issue), I remove the new trace: it is kind of cheating, but I don't want to have failures on the CI...

Btw, what was the problem? I've got a s390x Alpine Linux VM, so I guess I can tinker with this stuff at my leisure.

The pcap attached in #2260 returns different results only on s390x CI test

Ok, I'll create a PR when I figure out what's wrong.

I have seen similar issues for years so I don't think that the issue is the newer code....

@IvanNardi IvanNardi merged commit 61a1862 into ntop:dev Jan 12, 2024
32 of 33 checks passed
@IvanNardi IvanNardi deleted the bittorrent-utpv1 branch January 12, 2024 17:53
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.

3 participants