i have always wonderd what md5 tools are? i see people getting kicked by pb all the time for it missing (today 9 times!) what is it?

MD5 stands for Message Digest 5.
It's an algorithm that computes a 128-bit 32 hex character MD5 strings for each file.
This way it can compare the files on the client to insure they haven't been changed.
For example, lots of cheats work by hacking the the opengl32.dll file.
So PB makes sure the file hasn't been changed.
It also does this for every file in the COD directory to insure the files are stock.

The magority of kicks are for ignoring MD5 checks.
This isn't a result of the player doing anything wrong just a bad connection or packetloss.

There for a while after the last patch came out lots of people were getting kicked for MD5 mismatch of uo_game_mp_x86.dll. This wasn't because the player was trying to do anything wrong but had mistakenly install the wrong patch. They installed the server patch not the client patch.

Does that answer your question?

It's pretty easy to cause an MD5 collision now. It can be done in a few hours now on most PC's. PB needs to start using something else.

I have noticed alot of pb kicks ,how do you know when they are cheating? i used to get kicked for my ping on rein valley but when i refreshed my monitor (thanks to you guys and the forums) ive never had a problem.

but what im trying to say is ive never been kicked ,why are so many getting kicked by pb lately?

one guy today was kicked 2 or 3 times.

Yes, no, and probably not.

Dig back through the Slashdot archives for the past few months. While MD5 is getting weaker, it's still not quite as simple as that.

(Those who wish to be in the know should subscribe to Bruce Schneier's monthly CRYPTO-GRAM e-mail newsletter. http://www.schneier.com/crypto-gram.html )

Does that answer your question? [/quote]



a little ,im not to familiar with pb. thanks for the info druid

According to that article it only takes a few hours.

http://it.slashdot.org/article.pl?sid=05/11/15/2037232

Forgot the link to the source code and even a Windows binary. According to the guys who wrote it it will take about 45 minutes to find a collision on a 1.6Ghz Notebook PC.
http://www.stachliu.com.nyud.net:8090/collisions.html

The way PB uses MD5 doesn't apply to the point of the disputed weakness in MD5.
From the slashdot topic
"Tampering a signed binary is only possible using a preimage attack"

Ah ok. I don't know much about it. I just knew there were some algorithms out to cause collisions. Thanks for the correction.