[cheiftiger]

For those of you who have been searching for a long time for a keypad cracker sWEP for your RP gamemodes, I have your answer!



Pic is on garrysmod.org

Please do not download Swoots' Keypad Cracker. I know it says that he did not make it, but it still steals downloads from mine. He just copied it and re-uploaded it (he even stole my pic! >.<). So please, only download my version. Thanks

DarkRP Keypad Cracker v1.0

This version of the keypad cracker uses the same base code as the lockpick in DarkRP. This keypad doesn't freeze you while cracking, looks just like the lockpick loading bar and behaves just as the lockpick does. This addon is good for servers that allow fading door tool and keypads.

Updates from old Keypad Cracker SWEP:

v1.0 (Initial Release)
[ADDED] - Noises to indicate a keypad is being cracked (much like the lockpick)
[FIXED] - Loading bar (redone with the style of the lockpick loading bar)
[FIXED] - Keypad cracker no longer sends two "access granted"s to the keypad (Basically broken)

I do in fact know that there is a bug with the loading bar. If you open the chat box to talk, the loading bar disappears. If you do not move off of the keypad, you will continue to crack and it will still work. I am still looking for the solution to this problem.

Extract this to the "garrysmod/garrysmod/addons" directory.

Comment / Post Bugs / Suggest please!

[WoodenSpoon]

Is this a server addon? Or is it Clientside. Cause I went into a server and I saw it under weapons but it as admin only.

[cheiftiger]

This is a server addon, it is not a lua hack. The server has to put it in, then they have to add it to their custom shipments. I added it to my thief class. Sorry, but it is impossible (without brute forcing) to hack a 1.4 keypad with a clientside script.

[Jamie932]

cheiftiger posted:

Sorry, but it is impossible (without brute forcing) to hack a 1.4 keypad with a clientside script.

No its not.

[kevkev]

Jamie932 posted:

No its not.

You can not hack secure keypads, everyone has tried and noone succeeded.

[Jamie932]

Its just rather hard. Im sure there must be a way to do it.

[Lexic]

Jamie932 posted:

Its just rather hard. Im sure there must be a way to do it.

you could monitor the eye traces of every player on the server in a think and check when they were looking at keypads. If they were, you could then somehow find out if they were pressing 'use', and record the keystrokes applied to that keypad. Then when 'enter' was pressed and access granted, you'd know the combination.
Good luck working out how to do it. :)

Edited:

Actually, if you were already recording the nwvar changes on the keypad, you could check which keys were being looked at when the 'code' int was updated. This might actually be possible, but would be ruined by two people looking at the keypad, or if a slight (random) delay was added between keypresses and updates.

[kevkev]

Lexic posted:

you could monitor the eye traces of every player on the server in a think and check when they were looking at keypads. If they were, you could then somehow find out if they were pressing 'use', and record the keystrokes applied to that keypad. Then when 'enter' was pressed and access granted, you'd know the combination.
Good luck working out how to do it. :)

Edited:

Actually, if you were already recording the nwvar changes on the keypad, you could check which keys were being looked at when the 'code' int was updated. This might actually be possible, but would be ruined by two people looking at the keypad, or if a slight (random) delay was added between keypresses and updates.

The problem is that you just can't see if another player is pressing use clientside.

[Lexic]

kevkev posted:

The problem is that you just can't see if another player is pressing use clientside.

Lexic posted:

Actually, if you were already recording the nwvar changes on the keypad, you could check which keys were being looked at when the 'code' int was updated. This might actually be possible, but would be ruined by two people looking at the keypad, or if a slight (random) delay was added between keypresses and updates.

when you press use, the keypad's keypad_num NWInt is updated with the current code, or if it's secure, the number of *s. Therefore, after a bit of testing to work out the general delay between press and update, you could work out which key was pressed to make the code be updated, if you stored the past n keys that were looked at.

[kevkev]

Lexic posted:

when you press use, the keypad's keypad_num NWInt is updated with the current code, or if it's secure, the number of *s. Therefore, after a bit of testing to work out the general delay between press and update, you could work out which key was pressed to make the code be updated, if you stored the past n keys that were looked at.

True, but i doubt that we can find the usermessage that garry used (If he used one we can use in Lua anyway).

[Lexic]

kevkev posted:

True, but i doubt that we can find the usermessage that garry used (If he used one we can use in Lua anyway).

hook.Add("Think", "keypadCheck",function()
	for _,ent in ipairs(ents.GetAll()) do
		if ent:GetClass() == "sent_keypad" then
			if ent._PrevKey ~= ent:GetNWInt"keypad_num" then
				MsgN"Key has changed!"
				ent._PrevKey = ent:GetNWInt"keypad_num"
			end
		end
	end
end)

[Shankney]

Who needs a keypad cracker, just go mad as a SWAT with that door ram 8)

[Kirad]

I always guess everyone's pass is 1337

:D

[Carlisle]

What is sad is, Kirad's idea usually works...

[that or 1234 (or some pattern like that), or 1357 (it makes a "Y" on the Keypads. I've also seen 7951, which on a numpad makes a "Y")]

[Overv]

I just wrote one for 1.4, shall I post it so it might get fixed or not?

[Salads]

Overv posted:

I just wrote one for 1.4, shall I post it so it might get fixed or not?

You should keep it for yourself and enjoy it.

[Nisd]

Would it be possible for some one to add support for wire keypads? Because that could really be cool.

[hexpunK]

Overv posted:

I just wrote one for 1.4, shall I post it so it might get fixed or not?

You do have a choice, release it and chance it getting fixed, or keep it and get spammed by people (me too) trying to get it I would just keep it and only give it to people you trust won't release it.

[Jamie932]

hexpunK posted:

I would just keep it and only give it to people you trust won't release it.

*Hint* Me *Hint*

[CannedBeans]

Overv posted:

I just wrote one for 1.4, shall I post it so it might get fixed or not?

Don't post it. It'll only get fixed.

If you're srs, just give it to people you trust.

[Talishmar]

Lexic posted:

you could monitor the eye traces of every player on the server in a think and check when they were looking at keypads. If they were, you could then somehow find out if they were pressing 'use', and record the keystrokes applied to that keypad. Then when 'enter' was pressed and access granted, you'd know the combination.
Good luck working out how to do it. :)

Couldn't you strafe away from the keypad and press use and move mouse to confuse the script?

[CannedBeans]

Talishmar posted:

Couldn't you strafe away from the keypad and press use and move mouse to confuse the script?

I doubt that'd happen.

Couldn't it be possible though? Sort of like a spectating lua script?

[infinitywrai]

Jamie932 posted:

Its just rather hard. Im sure there must be a way to do it.

The keycode is stored serverside. There is no way the client can access it.

Please learn some basic LUA or programming at all before making a fool of yourself.

However using an LUA hack you could definitely find the keycode while someone else is opening it (tracking eye angle). It's easy to do using ULX spectate.

[Overv]

kevkev posted:

You can not hack secure keypads, everyone has tried and noone succeeded.

I beg to differ.

It's not visible, but this is a secured keypad.

[Pogostick]

overv posted:

i beg to differ.

it's not visible, but this is a secured keypad.

WANT

/caps.

[nibb1es]

Haha wow nice someone actually done that ;D
:P

[Lexic]

Overv posted:

I just wrote one for 1.4, shall I post it so it might get fixed or not?

Did you use my method or one of your own?

[Milata]

Overv posted:

I beg to differ.

It's not visible, but this is a secured keypad.

*Bites through the metal spoon in my mouth*
Want 0_0

[ihasaacount]

Milata posted:

*Bites through the metal spoon in my mouth*
Want 0_0

Same :/

[ZachPL]

I would like to "test" this please. :D

[Overv]

Lexic posted:

Did you use my method or one of your own?

Your method for secured, the 1.3 method for unsecured, though I hadn't looked at it before making this.

[Lexic]

Overv posted:

Your method for secured, the 1.3 method for unsecured, though I hadn't looked at it before making this.

Woot, concept proved. :c00l:

[Captain Lawlrus]

-snip-

[firestorm0]

Track where the player is looking, and compare to where each key is, record it, report code.

[Da Big Man]

Needs more clientside keypad cracker in here.

[Profanwolf]

Da Big Man posted:

Needs more clientside keypad cracker in here.

This.

[ihasaacount]

Profanwolf posted:

This.

This

[Overv]

lol.

Well, I'm still deciding, on one side I don't want every script kiddie to start hacking keypads, but on the other side I want to force a fix for it, since writing a cracker for this can be made tons harder my making a simple change to the keypad code.

[kevkev]

Overv posted:

lol.

Well, I'm still deciding, on one side I don't want every script kiddie to start hacking keypads, but on the other side I want to force a fix for it, since writing a cracker for this can be made tons harder my making a simple change to the keypad code.

Release it, i wan't to see a new keypad (version) anyway, and i am curious on how you did it exactly.

[ihasaacount]

kevkev posted:

Release it, i wan't to see a new keypad (version) anyway, and i am curious on how you did it exactly.

This