Custom Query (2449 matches)

deluge gtk appears to be requesting libtorrent to send an incorrect bitfield for crypto_provide on outbound connections.

original forum post: ​http://forum.deluge-torrent.org/viewtopic.php?f=8&t=43859

libtorrent ticket: ​https://code.google.com/p/libtorrent/issues/detail?id=474

in a nutshell, deluge gtk is sending via libtorrent:

bitfield 0x00 instead of 0x01 when requesting handshake/plaintext encryption from the outbound peer.

bitfield 0x01 instead of 0x02 when requesting fullstream encryption from the outbound peer.

bitfield 0x02 instead of 0x03 when requesting the outbound peer choose their preferred encryption method.

the implications of this vary depending on which encryption method the user has selected in the gui.

worst case scenario is no outbound peering occurs if the user has selected handshake/plaintext encryption as their encryption method.

outbound peering appears to occur for "fullstream" and "choose" but i suspect the encryption level selected by the peer is actually always "handshake/plaintext" and "fullstream" respectively. however i'm not 100% sure of this, it's a suspicion.

regards tristen

hey guys, long time user, great fan of your client.

a small and mildly annoying issue: when copying an info hash (typically from a webpage) there is often an extra whitespace character at the end.

deluge rejects the add if there is any trailing whitespace, forcing the user to (again) click "add", then "info hash", then paste, then remove the whitespace, then press enter or click ok.

it would be great if you could rtrim the info hash.

I'm using OSX 10.11.5

Under Settings and UI Notifications, Popups enabled and Sound enabled are greyed out. The Sound Customization tab is also greyed out.