Historical posts from cs.rin.ru

These posts lead to form css.setti.info. The year is 2005 and bug.meh.not has just come up with this new invention of verifying server patches with relatively easy method.

UPDATED RELEASE: Source/HL Cracked Server Query Tool

bug.meh.not, Posted: Monday, 29 Aug 2005, 23:06 [ http://cs.rin.ru/forum/viewtopic.php?f=31&t=18244 ]

This online server query tool can tell you a vast amount of information about a Source/Half-Life server, but it most importantly can tell if a server is cracked or not instantly! And for Half-Life servers, it can even tell what crack the servers uses!

Everyone, if you know about a cracked server, ENTER IT AT THIS SITE so people will know about the server!

Future updates will include a dynamic database to keep track of all cracked servers with dynamic favorites lists generators! Once this tool is out of the beta phase I will also release the source code to the public :)

http://209.33.89.167:900/

Laughing

Also, if you find any bugs, just talk about them in here Smile

For devs, if you query a server and hit the "View all server info" link, you can find some special debug info that might clue you in on how to discover if a server is cracked or not.

Cracked server tester

Ghost, Posted: Sunday, 23 Oct 2005, 13:09 [ http://cs.rin.ru/forum/viewtopic.php?f=31&t=20032 ]

People can check server status with this tool:

http://css.setti.info/server-status.php

It will tell what kind of emulation server uses.

For example to check fal.setti.info CSS server: http://css.setti.info/server-status.php?server=fal.setti.info

This same thing used to be at http://dass.x10hosting.com/ but it's gone now.

[DEV]Cracked Server Finder:SourceCode

bug.meh.not, Posted: Sunday, 30 Oct 2005, 10:16 [ http://cs.rin.ru/forum/viewtopic.php?f=31&t=20137 ]

For finding out the ping, do you parse a system() call, or do you time a fsock connection to the server? Or something else? Just curious Wink

I found that it was more compatible to time a fsock connection, since parsing a system() call would involve a different procedure depending on the host OS.


Ghost, Posted: Sunday, 30 Oct 2005, 11:10

bug.meh.not wrote:
For finding out the ping, do you parse a system() call, or do you time a fsock connection to the server? Or something else? Just curious Wink

Nothing that clever. It's a perl script which calls qstat and parses the output. There's also separate perl script which could be used to get the info from the servers without external progams but it's not as fancy as qstat so I stick with it. Determining ping with perl would be quite easy with Net::Ping module.

Determining the emulation is done separately in a script which writes the legal servers in a file so the main script doesn't ever query the legal servers.

Where did you get the idea that you can determine server emulation quite easily with 2 UDP packets basically? Good thing that you had the details (or debug) option for the query so it was possible to rip off the USERAUTH packet and create my own query script Wink


bug.meh.not, Posted: Sunday, 30 Oct 2005, 13:55

Ghost wrote:
Where did you get the idea that you can determine server emulation quite easily with 2 UDP packets basically? Good thing that you had the details (or debug) option for the query so it was possible to rip off the USERAUTH packet and create my own query script Wink

One day I was trying to figure out why c360 doesn't work on swds.dll cracked or linux cracked hl servers. It turns out that hCUPa's steamemu uses a different protocol for submitting the user authentication packet than extracted hl, cs, etc.

I was gonna try to hack steamemu a little so it would use that protocol that extracted hl uses, but I couldn't derive a good enough layout from the packets I was getting. So I decided I was gonna write a server query tool that tests the server to find out which protocol it accepts.

The cool part is, the client is authenticated within the first couple packets sent back and forth to save resources like you said. So all the tool does is pretend its a client, tries to join the server, and depending on how the server responds, it can determine whether its cracked or not.

A Source server says the client is accepted when it responds with B, followed by 13 0's and one null byte (0x00).

A hl server says the client is accepted when it responds with the IP address and port of the server.

But thats pretty cool how you wrote some of your auth stuff based off the debug stuff mine reports. I knew adding that would be useful to some people Laughing