old ban evasion

Thanks, this works perfectly.

Good find. I wonder why it disables the peer sharing though.

Originally Posted by Asuran

Good find. I wonder why it disables the peer sharing though.

Supposedly that is the reason it was banned from torrentbytes.. but the recent azureus CVSs have had the same feature, and they haven't been banned.

Anyway, I emailed solidox, hopefully he will decide to create an optional version of the patch that does not disable the get_peers, as that is a great feature.

I have also emailed rnysmile, but I don't know if he is even involved with the bitcomet project anymore. Still waiting for his reply.

Originally Posted by bradVexille

Originally Posted by Asuran

Good find. I wonder why it disables the peer sharing though.

Supposedly that is the reason it was banned from torrentbytes.. but the recent azureus CVSs have had the same feature, and they haven't been banned.

Anyway, I emailed solidox, hopefully he will decide to create an optional version of the patch that does not disable the get_peers, as that is a great feature.

I have also emailed rnysmile, but I don't know if he is even involved with the bitcomet project anymore. Still waiting for his reply.

Not speaking for any site in particular, but, Azureus' peer sharing is disabled by default, as well as only acting when the tracker registers as being down (when activated). If solidox makes the peer sharing prevention optional, I have a strong feeling that Bitcomet will be fully banned from all those sites again. As it is, some are evaluating the patch, and considering allowing the users to use it.

The original intent of the feature is great for a public tracker. And if it could be coded to only share with those registered on your tracker, it would help reduce some load from the private trackers. But with respect to the get_peers feature, if it was an optional piece of the client, and showed a different peerid, based on the functional status of that feature, it might help alleviate the concerns of the private trackers, because it would be able to be banned based on the security needs and requirements of the individual tracker.

That's why instead of just switching the peer_id, I instead took a look at the Azureus HTTP request and made an attempt to imitate it exactly, so that to the tracker it would seem indistinguishable from the real thing. Too bad it gives some gzip error on some trackers.

AWESOME! thanks brad!!

Originally Posted by Asuran

That's why instead of just switching the peer_id, I instead took a look at the Azureus HTTP request and made an attempt to imitate it exactly, so that to the tracker it would seem indistinguishable from the real thing. Too bad it gives some gzip error on some trackers.

Can you think of any way around that gzip problem?

Originally Posted by bradVexille

Can you think of any way around that gzip problem?

I would need to be able to test the situation and torrentbytes requires a login that I don't have. If you know any public trackers where this problem exists I will try to find a fix to it.

Originally Posted by HiTechOutlaw

AWESOME! thanks brad!!

Hey bud, long time no see! How are ya?

Originally Posted by Asuran

Originally Posted by bradVexille

Can you think of any way around that gzip problem?

I would need to be able to test the situation and torrentbytes requires a login that I don't have. If you know any public trackers where this problem exists I will try to find a fix to it.

Shoot me an email at mailto:bhvexille@gmail.com, I will get you access to torrentbytes.

very interesting patch. is there a way to contact solidox? i was working on a similiar patch but didn't manage to fully test it out. it didn't seem to work on my computer (well, at work anyway. didn't test it at home. might have been a security issue).

what i would like to know is how he managed to change the peerid. it seems to be that he's just changing the "exbc" peerid defination. i've compared the original and the modded and that's what it seems. of course there are other changes but all in all, the main component that changes the peerid is that. then in this case, wouldn't changing this peerid defination to the azuerus' peerid allow bitcomet to spoof itself as azuerus?

i'm highly curious as i'm a programmer but i lack solid knowledge in assembly language.

Originally Posted by bradVexille

Originally Posted by HiTechOutlaw

AWESOME! thanks brad!!

Hey bud, long time no see! How are ya?

not bad, just chillin at TB I havnt seen ya over there this time around, although I dont browse the forums much since there are too many stupid posts.

the patch is working great, I was playing around with a hex editor and I saw what was changed to make it change its reported client, very funny but I wanted to re-enable the peer data crap so I could use it on other trackers and still get good speed (witch does help btw) dont get me wrong, it should be disabled for private trackers but I think it is still good for public ones. (for anyone reading this from TB, I will not even think about using it against the tracker.)

Originally Posted by tokens

very interesting patch. is there a way to contact solidox? i was working on a similiar patch but didn't manage to fully test it out. it didn't seem to work on my computer (well, at work anyway. didn't test it at home. might have been a security issue).

what i would like to know is how he managed to change the peerid. it seems to be that he's just changing the "exbc" peerid defination. i've compared the original and the modded and that's what it seems. of course there are other changes but all in all, the main component that changes the peerid is that. then in this case, wouldn't changing this peerid defination to the azuerus' peerid allow bitcomet to spoof itself as azuerus?

i'm highly curious as i'm a programmer but i lack solid knowledge in assembly language.

The peerid change consists solely of changing "exbc" to "FUTB" in a hexeditor. All the other changes apparently disable the get_peers extension.

You might want to work with Asuran on creating a spoof program that allows bitcomet to spoof itself as azureus. He created one, but it only works on some trackers.

You can contact solidox via the TorrentBytes irc channel, that's the only way I know, he's over there a lot!

Dunno if it's allowed to advertise irc channels over here, so pm me if you want to know how to get there


This patch actually works? No other stuff that shouldnt be in there?