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 v2 support #480

Open
XfedeX opened this issue Jul 13, 2023 · 13 comments
Open

Bittorrent v2 support #480

XfedeX opened this issue Jul 13, 2023 · 13 comments
Labels

Comments

@XfedeX
Copy link

XfedeX commented Jul 13, 2023

It looks like bittorrent-tracker server does not support v2 torrents.

@github-actions
Copy link

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

@github-actions github-actions bot added the stale label Sep 11, 2023
@resession
Copy link

still relevant

@github-actions github-actions bot removed the stale label Sep 15, 2023
@kovalensky
Copy link

What do you mean by BT_v2 support, there is no need for a tracker to support it, since only difference here would be a longer v2 info hash, but due to specification even it is being truncated from 40 bytes to 20.

@Power2All
Copy link

Power2All commented Oct 25, 2023

What do you mean by BT_v2 support, there is no need for a tracker to support it, since only difference here would be a longer v2 info hash, but due to specification even it is being truncated from 40 bytes to 20.

Not true.
Bittorrent v2 uses a different structure of the torrent array.
https://www.bittorrent.org/beps/bep_0052.html

It also uses an different hashing method then the original Bittorrent.

@kovalensky
Copy link

@Power2All I meant tracker communication, since the question was about the server (announcer) software, yes hashing algorithm did change for meta files, additions to the client software for calculating their info-hash could be made + file tree info if necessary, I've read the BEP a couple of times.

@Power2All
Copy link

@kovalensky Not only meta files, also the main hashing is not done with SHA1 anymore. Tracker communication is still just a IP and port list, and can be retrieved with HTTP/HTTPS announce request as well. File tree structure is not exchanged with the announcements, so I do not see the point still.

@kovalensky
Copy link

Not only meta files, also the main hashing is not done with SHA1 anymore.

That's what I said, I also meant that client side of bittorrent-tracker could be improved to read v2 files (if there's such function), I didn't say that file list is being exchanged with the tracker, probably some misconception happened.

Copy link

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

@github-actions github-actions bot added the stale label Dec 26, 2023
@resession
Copy link

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

still relevant

@github-actions github-actions bot removed the stale label Dec 27, 2023
Copy link

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

@github-actions github-actions bot added the stale label Feb 25, 2024
@kovalensky
Copy link

@github-actions Still relevant

@github-actions github-actions bot removed the stale label Feb 26, 2024
Copy link

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

@github-actions github-actions bot added the stale label Apr 27, 2024
@kovalensky
Copy link

Is this still relevant?

Relevant lil g, no worries

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants