Google TechTalks: Crypto Strikes Back!

Gamasutra: Dirty Coding Tricks

"When the schedule is shot and a game needs to ship, programmers may employ some dirty coding tricks to get the game out the door. In an article originally published in Gamasutra sister publication Game Developer magazine earlier this year, here are nine real-life examples of just that." Read More ...

What a day ...

Man i m still shocked about what we have learned today. Our admin version of fps-death got leaked again and this time an admin of xj gave it away to someone who submitted a bhopscript demo to xj and then gave it to kayne who released it. Those people made him and other admins trust them. Since this is inexcusable he ll get kicked out today or tomorrow and we ll have to find a new admin who is doing his work and we can trust in.

What we learn from this is that you can t secure a program from leaking by giving it to as few people as possible ... still the temptation seems to be too big. So for future analysing programs there has to be a system that we know exactly who is using what and when and bind programs to computers even for people you think you can trust absolutly and of course an emergency shutdown so noone can use these progs after a leak. To do this and make it as hard to hack as possible will be a lot of work but it seems to be necessary.

Win 7 activation cracked 85 days ahead of general release

Image credit: user “arabmed” on mydigitallife.info forums

Looks like things haven’t changed all that much since Windows XP.

Small update ...

Well the last weeks were full of interesting and new things i learned, while working on kcac, and i can t really talk about them ... except that the next kcac version will be on a whole new level and in no way comparable with the old one. We are a team of experts now with gangien helping me out on the coding side and emti designing the artworks. Here is a preview screen of the current version:

I had to cut out the interface development completely for now because it would have taken too long. So we re working with winapi now to get the prog ready to use as fast as possible.

On the positive side you ll be able to record demos on servers once we released it.

Also there was an interesting story: While i was working on getting some data out of steam.exe we need for kcac i ran into my password saved in plain text in the memory ...

After investigating this a bit more i came to the conclusion that everyone with basic knowledge about reading other processes memory can read my steam password if he wants to. I talked about this with Soulfather and he sent a mail directly to his contact at Valve. Let s hope they ll take the appropriate actions.

Now about the fast demo-checker: The code is finished and i started with adding maps but since my focus is on kcac and i have to learn a lot for university atm i ll pause the map adding for some time. You can get an updated test version here. Ofc the interface will get a redo for the release. Once this is done it ll get the correct record time on all maps from the record list. So this will become the #1 tool for public demo checking.

River flows in you

me playing "river flows in you" on my keyboard: link

Fast demo checker pre-release!

Here is a test program for the demo-checker i m currently working on.
The loading code i wrote myself is streaming the demos with an 1mb buffer so it doesn t need more ram than that buffer to load demos. And it is really fast ;)

I ll release the code of the file-loading class with an explanation how it is done later.
The interface is not done yet but i ll add one when i m done with e2D and will officially release the prog after that.

You can download it here: Link

Note: This prog is not finished yet! I still have to change the average fps and server time to get the official results.