HP1

I think you cant create new signatures, but (correct me if i am wrong) maybe there are still unknown signatures that could be useful

That explains a lot of things If I put timeout kicks under effect of kick config, can it result any error? One more short notice, logging is a bit too detailed, I should have to buy a new hdd after a week of usage

you didnt have any issues concerning windows firewall users? some of them got randomly disconnected during loading or directly after login while kick wasnt even enabled.

So you dont know if it causes a client crash on mac or not? By the way a config option for turning off warden would be good, or a way to specify an account list to exclude them from warden checks

After 2 hours of testing I got a lot of fails on these two memory tests: (403, 243, '', '', 4609675, 5, '5E5DC20800', NULL), (438, 243, '', '', 11287980, 8, '04000000903C9F00', NULL) this one is same as uac false positives on page 4 I have no idea if the other is also a false positive or not. And i have a question, this implementation does not cause client freezes to mac users?

Thank you TOM_RUS! Could you give us a little manual or description about this implementation? Using this only one module it can detect different type of cheating programs? Are there any known false positive results? I am looking forward to see a new version of Neo2003s work

SignFinder, and you dont have any of these connection errors? I mean ERROR: Unexpected packet loop ... and the connection losses?

I think these files are signed and we cant reproduce it.

Warning, stupid question next: In the original Ace wrappers archive, there are example and test folders, they doesn't contain any helpful material?

I have a very similar crash, it occurs after every second server startup. 2011-05-01 16:49:50 ERROR: Unexpected packet [255] from Wardend, trashing it It repeats until world thread hangs and got kicked out. Wardend was running and didnt produce any log entry that could help, only this: 2011-05-01 16:46:50 Warden system initialized. 2011-05-01 16:49:59 Accepting connection from '192.168.32.1' 2011-05-01 16:49:59 World process connected. 2011-05-01 16:50:14 Terminating connection from '192.168.32.1' I used Warden110406b patch and 32bit debian lenny. I runned tests using wine and windows machine for wardend, but world daemon was always on linux. Then I started tcpdumping, and got the following results: http://pastebin.com/tRv1bmQ9 < during startup http://pastebin.com/G3wTGEBB < during startup http://pastebin.com/rcTjeKGY < after closing wardend I noticed, that there are only few packets after the loop begins, so mangosd was not getting so many bad packets as the count of log messages. Maybe one false tcp packet starts this kind of loop because world daemon cant move on. I hope I could help. Should I make a few crash backtraces too?

But that option makes only half work, it makes inventory and bank items lost