On bittornado I used these settings for encryption:

BTW, this client looks promising!

* forced - Only encrypted connections are allowed. Incoming connections that are not encrypted are closed and if the encrypted outgoing connection fails, a non-encrypted retry will not be made.KCE wrote:I previously used bittornado for a long time but decided I need something easier to manager multiple torrents (and it lagged my screen with beryl). I also used encryption and am trying to make sure I set it up properly and in the same manner on deluge. What does each setting of Level do?
BTW, this client looks promising!
azureus uses rc4 encryption, like we do, and other major clients. i wouldnt call it azureu's implementation, as it's not really theirs but used by them, but yeah, it's compatible if that's what you're asking.KCE wrote:Thank you for the quick reply.
BTW does the encryption standard follow Azuerus's implementation?
I think that the translation to spanish of these options is incorrect.markybob wrote: * forced - Only encrypted connections are allowed. Incoming connections that are not encrypted are closed and if the encrypted outgoing connection fails, a non-encrypted retry will not be made.
* enabled - encrypted connections are enabled, but non-encrypted connections are allowed. An incoming non-encrypted connection will be accepted, and if an outgoing encrypted connection fails, a non- encrypted connection will be tried.
* disabled - only non-encrypted connections are allowed.
* handshake - only the handshake is encrypted, the bulk of the traffic remains unchanged.
* full stream - the entire stream is encrypted with RC4
* either - both RC4 and plaintext connections are allowed.
prefer to encrypt the entire stream means you want to prefer the RC4 encrypted stream.