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

Update for BitTorrent Protocol Specification v2 #29

Open
paxter opened this issue Jan 1, 2019 · 13 comments
Open

Update for BitTorrent Protocol Specification v2 #29

paxter opened this issue Jan 1, 2019 · 13 comments
Assignees
Labels
feature request The issues requests a yet unimplemented feature. under construction The issue is being worked on.

Comments

@paxter
Copy link

paxter commented Jan 1, 2019

Would be nice, if this tool would be updated with the latest BitTorrent Protocol Specification v2 described here: http://bittorrent.org/beps/bep_0052.html
Especially the part with stronger hash functions (SHA2-256) would be nice.

@paxter paxter changed the title Update for BitTorrent Protocol Specifaction v2 Update for BitTorrent Protocol Specification v2 Jan 15, 2020
@maddovr
Copy link

maddovr commented Sep 9, 2020

@sbrudenell
Copy link

SHA-1 chosen-prefix attacks are now in the USD 10k-100k range. This presents a very real threat, for example against bittorrent-distributed software that might be used by dissidents or whistleblowers.

BitTorrent v2 should be high priority now.

@pobrn
Copy link
Owner

pobrn commented Oct 27, 2020

BitTorrent v2 and hybrid torrent file generation is being implemented at the moment.

@Rudde
Copy link
Collaborator

Rudde commented Oct 28, 2020

@sbrudenell What potential attack vector do you see could be used against a torrent file, or its usage?

@sbrudenell
Copy link

@sbrudenell What potential attack vector do you see could be used against a torrent file, or its usage?

I admit I don't have a specific vector in mind, but sha1 is used in many places in the torrent protocol so it's hard to convince myself there are no attacks.

@paxter
Copy link
Author

paxter commented Aug 5, 2021

Anything new? Looks like the "moment" takes a lot of time. :D

@zero77
Copy link

zero77 commented Jan 7, 2022

If you are looking to create V2 or hybrid torrent this may be of interest:
https://github.com/alexpdev/torrentfile-legacy

@predb
Copy link

predb commented Jul 18, 2023

If you are looking to create V2 or hybrid torrent this may be of interest:如果您想创建 V2 或混合种子,您可能会对此感兴趣: https://github.com/alexpdev/torrentfile-legacy

@zero77 thank you, do you know is there any other command line tools for creating new torrent besides this?

@zero77
Copy link

zero77 commented Jul 18, 2023

@predb
That's the only one i am aware of but, i haven't checked to see if any torrent clients can do this from command line, maby libtorrent.

@ceed0
Copy link

ceed0 commented Jul 27, 2023

https://github.com/fbdtemme/torrenttools supports V2 torrents, it hasn't been updated for some time too, but it works.

Also you can find other tools in the comparsion graph there.

@jerryfreak
Copy link

jerryfreak commented May 20, 2024

https://github.com/fbdtemme/torrenttools supports V2 torrents, it hasn't been updated for some time too, but it works.

Also you can find other tools in the comparsion graph there.

i cant find a build for ubuntu jammy and trying to compile from source didnt work for me. i was able to use appimage tho.

how does one use the "similar torrents" switch? my application is to update an existing torrent fileset with new version with edited/appended files. how would one do that efficiently

@pobrn
Copy link
Owner

pobrn commented May 21, 2024

how does one use the "similar torrents" switch?

As far as I can see the --similar and --collection options of torrenttools are supposed to implement BEP38.


In any case, please note that torrenttools sometimes does not seem to generate correct v2 or hybrid files.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request The issues requests a yet unimplemented feature. under construction The issue is being worked on.
Projects
None yet
Development

No branches or pull requests

9 participants