seed.helper Posted January 22, 2008 Report Share Posted January 22, 2008 what the hell is this client lol ?is from future Link to comment Share on other sites More sharing options...
DreadWingKnight Posted January 22, 2008 Report Share Posted January 22, 2008 Looks like a badly done fake. Link to comment Share on other sites More sharing options...
jewelisheaven Posted January 22, 2008 Report Share Posted January 22, 2008 ...or a well-done fake. It's not registering as [FAKE]. Link to comment Share on other sites More sharing options...
seed.helper Posted January 23, 2008 Author Report Share Posted January 23, 2008 LOL ! well done or bad done ? Link to comment Share on other sites More sharing options...
Ultima Posted January 23, 2008 Report Share Posted January 23, 2008 If there's any obvious indication that it's fake, then it's badly done. The point behind faking one's client ID would be so that no one (or nothing) could tell it was fake Link to comment Share on other sites More sharing options...
amc1 Posted January 23, 2008 Report Share Posted January 23, 2008 No way I can hold back from commenting on this - I didn't spend an obscene amount of time improving the client identification code in Azureus without learning a few things. My guess is - there's a buglet in UT 1.5 and 1.6 where the client name transmitted in the extended protocol handshake (you know the one - the one causing the buffer overflow crash) isn't properly Unicode encoded like it should be, and just falls back on using some default encoding. If Azureus and UT just used displayed the name in the format it was transmitted, it would probably display a square bracket rather than the µ symbol.So - I think that although UT doesn't really think that it is another UT client (and even if it does, the version number doesn't make it perform a "fake" check), it's probably applying the hack to deal with the square bracket character and putting a µ character - which is fine for older clients, but isn't appropriate for non-UT clients. The peer ID doesn't say it is a UT client either (though that isn't obvious from the screenshot). I've seen a few of these peers around - but I still have no idea what client it is, other than the few times I've seen them, the peers seem to be from Israel... Link to comment Share on other sites More sharing options...
Firon Posted January 23, 2008 Report Share Posted January 23, 2008 It's just some poorly hacked client in this case. Link to comment Share on other sites More sharing options...
amc1 Posted January 23, 2008 Report Share Posted January 23, 2008 It's just some poorly hacked client in this case.Perhaps. Nothing to say that it's a hack of µTorrent though. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.