Closed ntzb closed 11 months ago
maybe I'm missing a configuration, but can't get the spoofed client to actually be sent.
the client that was configured to be spoofed is sent in communications to tracker and other peers
when I turn on spoofing useragent, the log shows that the change was saved, but the announces to the tracker include the regular libtorrent peer_id
2022-05-30 23:51:18.419 T:3924816768 NOTICE: [plugin.video.elementum] INFO bittorrent ▶ configure UserAgent: Transmission/1.93, PeerID: -TR1930- 2022-05-30 23:55:41.240 T:3670471552 NOTICE: [plugin.video.elementum] NOTI bittorrent ▶ logAlerts torrent_log_alert: Obi-Wan.Kenobi.S01.WEB-DLRip.HDrezka Studio: ==> TRACKER_REQUEST [ url: http://bt3.t-ru.org/ann?info_hash=XXXXXX&peer_id=-LT11D0-n0a0jpQYDk*M&port=6891&uploaded=0&downloaded=0&left=1366000648&corrupt=0&key=XXXXX&event=paused&numwant=200&compact=1&no_peer_id=1&supportcrypto=1&redundant=0 ] 2022-05-30 23:55:45.285 T:3670471552 NOTICE: [plugin.video.elementum] NOTI bittorrent ▶ logAlerts peer_log_alert: Obi-Wan.Kenobi.S01.WEB-DLRip.HDrezka Studio [XXXXXXX:26714] >>> HANDSHAKE [ sent peer_id: XXXXXXXXXXXXXXX client: libtorrent 1.1.13 ]
tested on multiple versions (latest was tried first), and on different torrents.
using on private trackers
seems that the last working version with changing useragent is 0.1.47
maybe I'm missing a configuration, but can't get the spoofed client to actually be sent.
Expected Behavior
the client that was configured to be spoofed is sent in communications to tracker and other peers
Current Behavior
when I turn on spoofing useragent, the log shows that the change was saved, but the announces to the tracker include the regular libtorrent peer_id
tested on multiple versions (latest was tried first), and on different torrents.
Steps to Reproduce (for bugs)
Context
using on private trackers