-
Notifications
You must be signed in to change notification settings - Fork 71
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
Comments
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. |
BitTorrent v2 and hybrid torrent file generation is being implemented at the moment. |
@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. |
Anything new? Looks like the "moment" takes a lot of time. :D |
If you are looking to create V2 or hybrid torrent this may be of interest: |
@zero77 thank you, do you know is there any other command line tools for creating new torrent besides this? |
@predb |
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 |
As far as I can see the In any case, please note that |
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.
The text was updated successfully, but these errors were encountered: