xbt icon indicating copy to clipboard operation
xbt copied to clipboard

Implementation of SHA256 for decryption of Passkey

Open BoraVivek opened this issue 2 years ago • 5 comments

Hello,

Do we need to change the encryption and decryption of torrent pass keys using sha256, in order to support V2 Torrents? If so can you please implement those changes at the earliest.

https://blog.libtorrent.org/2020/09/bittorrent-v2/

Thankyou

BoraVivek avatar May 06 '22 03:05 BoraVivek

With so many clients now supporting v2 torrent it's only a matter of time before xbt is left behind. You should really consider implementing hybrid and V2 torrents.

madness85 avatar Feb 13 '23 21:02 madness85

With so many clients now supporting v2 torrent it's only a matter of time before xbt is left behind. You should really consider implementing hybrid and V2 torrents.

In XBT Client?

OlafvdSpek avatar Feb 13 '23 21:02 OlafvdSpek

With so many clients now supporting v2 torrent it's only a matter of time before xbt is left behind. You should really consider implementing hybrid and V2 torrents.

In XBT Client? https://alternativeto.net/list/32585/bittorrent-v2-supported-torrent-clients/

But xbt tracker doesn't support hybrid or v2.

madness85 avatar Feb 13 '23 21:02 madness85

It doesn't?

To handle this, DHT- and tracker announces and lookups for v2 torrents use the SHA-256 info-hash truncated to 20 bytes.

OlafvdSpek avatar Feb 13 '23 21:02 OlafvdSpek

It doesn't?

To handle this, DHT- and tracker announces and lookups for v2 torrents use the SHA-256 info-hash truncated to 20 bytes.

Need support hybrid mode (v1 + v2) for compatibility with old clients. In DB need info_hash binary(20) AND info_hash2 binary(32) (i.e. 2 hashes).

AngelOfFear avatar Mar 06 '23 18:03 AngelOfFear