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.

Sign up for GitHub

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

Jump to bottom

BEP 34: respecting DNS TXT record of tracker (DNS Tracker Preferences) #103

Closed
AnimMouse opened this issue May 30, 2020 · 3 comments · Fixed by #113
Closed

BEP 34: respecting DNS TXT record of tracker (DNS Tracker Preferences) #103

AnimMouse opened this issue May 30, 2020 · 3 comments · Fixed by #113
Assignees
@CorralPeltzer

Comments

@AnimMouse
Copy link
Contributor

Suggestion: Let newTrackon query for TXT record for "BITTORRENT" according to BEP 34

If "BITTORRENT DENY ALL" was found, delete the tracker on trackerlist.

If tracker uses UDP:X and/or TCP:X. Let newTrackon list what the server preferred to use.
@CorralPeltzer CorralPeltzer self-assigned this Jul 25, 2020
@CorralPeltzer CorralPeltzer linked a pull request Jul 26, 2020 that will close this issue
BEP-34 #113
Merged
@txtsd
Copy link

txtsd commented Nov 9, 2020

What's the holdup on this?

@AnimMouse
Copy link
Contributor Author

It seems like newTrackon is not deleting trackers when BITTORRENT DENY ALL is found, only saying Tracker denied connection according to BEP34 in the Raw Data and stops connection.
And using BITTORRENT TCP:X changes the protocol into UDP instead of HTTPS.

@CorralPeltzer
Copy link
Owner

@AnimMouse thanks for catching that! I've just fixed those 2 issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@CorralPeltzer CorralPeltzer

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

BEP-34 CorralPeltzer/newTrackon
3 participants
@txtsd @CorralPeltzer @AnimMouse