|
[an error occurred while processing this directive]
|
|
| |
OpenGL32.dll
Hack or Not?
 Home > Interviews
& Columns > OpenGL32.dll Hack or Not?
The long wars of words over the opengl32.dll has raged on for many months when
the first load of players were flagged up for being cheaters with the
opengl32.dll being at the heart of it. Well time has moved on and so have many
of the players but the old opengl32.dll still remains on many cheat name &
shame sites. So what is the story behind the so graphics dll hax and why hasn't
it been completly whiped out?
Quoted from: www.counter-hack.net
Wall Hax
There are three major types of wall hacks: Transparent, Partial Transparent,
and Sprite. Each one has a different method of achieving the wall hack effect
of seeing people through walls. This gives the cheater the advantage of knowing
were the enemy will be so that it's easier to kill them without them killing
the cheater first. In Counter-Strike it gives the cheater the advantage of
shooting through walls with powerful guns to kill the enemy.
Transparent
Transparent wall hacks make all the walls on a map transparent, usually about
50% transparent. It is like having a window with a small layer of frost, you
can see through the window partially, but you can also see the frost so you
know where the window (or in a game the wall) is.
Hackers achieve this effect by several methods, usually either replacing the
OpenGL32.dll file in the windows system files, or they “hook” the
OpenGL32 file when it is loaded into the memory, altering its information to
achieve this effect. This wall hack method is harder to use for cheaters unless
they know the map well, because it is harder to tell if your are actually
shooting someone through open space, or through a thick wall, and navigating
the map is hard. Usually these wall hacks do not have an aimbot included, which
forces the hacker to use their skills.
Partial Transparency
Partial Transparency wall hacks make only certain objects transparent. Most
hacks that "hook" the Half-Life game engine use this method. In the
picture, all the walls are solid, but you can see through the bridge.
Things such as doors, ladders, bridges, and usually anything interactive within
the map that aren’t “walls” are transparent. Most hacks that use
this method have other cheating methods included such as Aimbots, ESP, Speed
Hacks, etc. This method is easier to use for cheaters, since they don’t
get lost as easy.
Sprites
The Sprite Method is simply an only let what you want to see be seen through
the walls. This method edits OpenGL files and the memory to allow player
models, and other things that are not walls, to be seen through walls.
See the hostages? Unlike the Transparent method, it shows only hostages through
the walls. This is the most effective wall hack, since the cheater knows where
the enemies are and the cheater doesn't see everything else behind the wall.
|
CS map de_dust where you can clearly see the OpenGL32 being used to remove
all the textures.
Quoted from: www.quakeworld.nu
OpenGL32.DLL
Hacking
Recently, a “new” type of Quakeworld wall hack is appearing more
and more often on the horizon. The serious nature of this hack is that it works
in all Quakeworld GL clients, as well as all other OpenGL games. What is also
very disturbing is that it is currently undetectable by any kind security
measure that FuhQuake, More Quakeworld, or Qizmo offer. The wall hack itself is
a modified “opengl32.dll” file. I’ve had a small question and
answer session with the author of Fuhquake about this topic, and here is his
insight.
How does the hack work and what does it do?
A library called opengl32.dll is modified to alter the way OpenGL games are
rendered. This hack has nothing to do with Quakeworld specifically. It affects
all OpenGL games equally, including Quake3 and Half-Life. When a game draws a
3D world it needs to do tests to make sure that things that are behind a wall
in the 3D sense don't appear in front of the wall on your 2D screen. The
opengl32.dll hack basically disables the game's ability to determine whether an
object is behind or in front of another object in the 3D world. This makes
players (almost always) appear in front of walls when they are behind.
The good news is that this isn't the most useful wall hack, and in some cases
can actually make it harder to play. The reason is it doesn't just draw players
in front of walls when they are really behind it. It also draws walls in front
of walls that they are really behind. This can really distort what a map looks
like (by putting walls in wrong places). The degree of distortion depends on
the map and what room you are in. It makes unplayable in dm3's ra room (imho),
but has little effect on dm6 (so you have an effective wall hack there).
Can we check if an opengl32.dll is
modified?
You can't check if an opengl32.dll is modified directly. You can however check
an opengl32.dll against a list of 'known non-cheat' opengl32.dll's and assume
that any opengl32.dll not in that list is hacked. The problem here is that
there are lot's of opengl32.dll's, especially for older cards like the 3dfx.
Actually an even bigger problem is that this cheat can be placed in other
libraries besides opengl32.dll, and overall there would easily be thousands of
libraries that would need to be checked. This makes it unpractical.
Is there anything we can do?
Well this is a serious issue and so I will be taking steps to eliminate this
problem for FuhQuake. Eliminating cheats that work the same/similar to the
hacked opengl32.dll's that are currently out on the market is a realistic goal,
and this is what I will be doing. For a permanent solution, someone with more
resources than me (someone who gets f*cking paid?) will need to get off their
asses.
Can we check if someone is using this cheat by taking
remote screenshots?
The problem is this cheat is toggle able. It is configured to turn on/off at
the press of a key. So it will only be useful to take a screenshot in game when
two players are close but separated by a wall. This will cause a sudden 1+
second lag (taking into account writing the screenshot to disk and then sending
it) in a critical point of the game, so I don't think remote screenshots will
be very useful.
|
de_dust again this time the OpenGL is being used to wall hack, seen
above.
Finally de_inferno again the textures are removed.
I leave you to decide whether you can trust players found having invalided
OpenGL32.dll files. Yes they could just be a case of invalided driver patches
or then again they could be a found of cheat. We may never know the full story
but like I aways say "Don't be fooled into over tweaking your drivers,
just stick to what works & get on a play the game fair".
Previous Page
|
|
