Guest wrote:
To prevent this, enabling DHT privacy must affect the torrent's info-map, and therefore its infohash, which means enabling DHT privacy must result in a new torrent that's not backwards compatible. This means that it must be implemented as part of a new protocol
I agree that a torrent with
DHT privacy must be resistant to downgrade attacks. Though I think there are ways to add it in fully backwards-compatible way. Yes, it must affect the
info-hash, but the
info dictionary may include arbitrary data (IIRC). This is where it could be put in at torrent creation. Thus preventing downgrades.
https://www.bittorrent.org/beps/bep_0003.html (btw in my opinion the level of detail of the BEPs is awful for a good understanding of the protocol)
Additional
upgrades from plain v1 to v1+DHT Privacy don't seem to make much sense at first, because you start from a known secret (v1 infohash + constant salt).
Yet isn't it still a valid proposition, if you consider the timeframe of decades? Allow a capable client to have a cut-off date, say 2035, and from then on only allow v1-upgraded-DHT-privacy activity. Why? The attackers would need to have seen ALL v1 infohashes ever created to be able to derive v1+DHTpriv infohashes. It is not a strong privacy guarantee, more like a rectification of mistakes. Like the torrents of the past 25 years. Or whatever new torrent is gonna be created by mistake in v1-only mode. Due to the optional nature of these upgraded torrents, the client will always have the option to allow v1/ only upgraded v1 or above / v1.5 DHT privacy.
// The security guarantee of upgraded v1 is marginal, because it is enough for one client to leak the infohash to DHT by searching for it & attacker happens to be online to capture it.
I have tried to read the specification written by KH twice, but it was too dense for me and too split in many pages to understand.
Most importantly, like Guest said,
motivations/reasons must be clearly laid out. Not only is this an argument in support of your own proposal, it helps readers to understand the technical details and solutions proposed.
Further, the documents need to be rewritten for comprehension. I am offering myself for these discussions, but I wouldn't want to do it without an active Q&A style of communication with KH. Whatever his brain holds, needs to be put down in writing as humanly as possible :) As part of these rewrites the structure of the documents (headings/topics) needs to change too.
Lastly, I agree that the
naming "v3" needs to change. Why? It feels hostile to the "mainstream group" working on Bittorrent: libtorrent, qBittorrent. This tension alone will hinder productive discussion and neutral consideration. To put shortly, this needs better marketing.
This includes Tixati users here! You using LLMs only adds fuel to the fire and portrays Tixati developer, the proposal and the user community as a whole in a negative light. It is not reddit, it's not a normie forum, where your emotional discussions can overcome technical doubts. Slinging shit until it sticks doesn't work. Calm down, what
you can
focus on are the direct benefits this brings to the end users:
- (weak-moderate) stronger hashing than SHA1: fortunately or unfortunately too few attacks have been observed in practice
-> it doesn't help that this page is 4 levels deep (help Dora find 3 links leading there):
https://tixati.com/specs/bittorrent/collision_demo
- (moderate) peer connection encryption is mandatory: there's no reason to make it easy for ISPs and middleboxes to easily recognize BT traffic and its aggregate bandwidth. Support is practically universal. The default setting is not ON. Still, DHT will continue to be an obvious marker.
- (weak-strong) DHT privacy. For some reason people participating in the libtorrent discussion weren't impressed. I believe this is the strongest reason to make a switch. The open internet is no more, openness itself has become adversarial. I2P is good, but this alone shouldn't be an excuse to ignore reality in light of its adoption rate.
This needs a lot of 'administrative' work, but I do support this in general.