Proper use of the encryption toggle

[Technarch]

If one looks at the peers column, a I means incoming connection. If you have allow legacy it won't try to force E on an I if the incoming connection didn't have 'enabled' on.

However I am of the opinion that it may be beneficial to encourage clients under certain circumstances supporting E to activate it on an incoming connection because there may be a bunch of people who have throttling full or partial and don't know that it can be worked around.

Problem is, the disallow legacy is a broad brush. It will disallow everyone who doesn't support E on an incoming. I'm not even sure if it'll negotiate.. if a utorrent 1.5 tries to connect but E is set to none, will my client just drop the request or make it renegotiate with an E? Because I am connected to

Ideally there probably could be a sub-option such as 'if clientver => azureus2400 or utorrent 141B then disallow legacy else allow for everyone else'.

Once in awhile I'll see an outgoing to a utorrent or azureus and there is no E, but there is a connection regardless which is strange because I thought remotes were supposed to accept incoming E requests.

If anyone is confused, I want to have an E flag on both incoming and outgoing on all clients that have the technical ability to support it, but still allow non-E on clients that don't have it, and they can try their luck.

[emtec666]

Good idea. I frequently get incoming legacy connections from uTorrent 1.5 & Azureus 2.4.0.x peers.

Then I have to start/stop the torrent to get the encrypted connection (of course this only works if the user is connectable).

Something like "Force encrypted incomng connections from supported clients" would be nice (maybe with a legacy fallback for them too)

[The Mighty Buzzard]

Encryption support is propogated through PEX so the brush isn't quite as broad as you think. The "Force encrypted incomng connections from supported clients" idea has been hashed over so many times it's getting silly now and the answer has been a definitive "no" every time.

[Firon]

Yeah, the answer is no because it's not possible. Simple as that. The connection was already established and is already throttled.