private tracker passkey issue

[TuuS]

uTorrent 1.8.5 build 17414

WinXPsp2

Dlink dir655 extreme N gigabit router

Intel gigabit ethernet adapter

Verizon FiOS 25up/25down

I'm a private tracker admin and was investigating a problem with a members account. I started a torrent with the members passkey to confirm it was working correctly, which it was, no tracker errors and it showed on their account on my tracker (tbdev).

I then stopped the torrent, all was well.

I then deleted the tracker announce and entered the tracker with my passkey on it, and restarted torrent. It connected without any error message.

I was then alerted to the fact that this torrent was seeding on the other members account, and not my own. I double checked and it was seeding in utorrent with my passkey, and registering on the tracker on the other members account.

Is it possible that utorrent is using the tracker in the file.torrent, not the tracker that was added in the gui?

If you can confirm this is a bug, then please move this to bug reports, but I thought I'd ask here first.

Also, if it will help development, I'll try to reproduce this to confirm the problem is consistent.

TuuS

[DreadWingKnight]

Does a wireshark capture of the announce request show the original passkey or the modified passkey?

[TuuS]

I haven't done any testing that specific. If it will be helpful to development, I'll try to find the time to reproduce this then install wireshark to test, but I thought the first step should be to bring the subject up here, perhaps it had been seen before.

Please let me know if you want me to test this, then give me a week or so as my day-job is keeping me pretty busy this week.

[DreadWingKnight]

It would need to be done to rule out the tracker misbehaving.

[TuuS]

Very well, I will look into this and reply when I have more information.

Thank You

[DreadWingKnight]

Oh yeah, and 1.8.5 isn't supported anymore AT ALL.

Something I overlooked.

[TuuS]

I'm aware of that, but when I tried all post 2.0 versions I was getting constantly logged hang reports. I eventually reverted back to 1.85.

The computer in question is old, a P4, 2.0ghz. I had run uTorrent for years without issue even with only 256mb ram. I upgraded the ram to 1024mb and still got the constant (dozen or more per day) hang reports, so I reverted back.

If I can confirm this is actually a problem, I'll test it on one of my newer computers with the latest version of uTorrent.