• What do you want to see in SE 3
    21 replies, posted
SE = Scriptenforcer Well since SE2 was the biggest fail since SE1 what do you want to see in SE3?
It actually working like it should, no more no less.
There will always be ways around it, no matter how much security you apply.
Uhhh SE2 works pretty well, you know. It doesn't catch people that bypass it, but that's what admins are for, since the people that are bypassing it in the first place are in the minority. That is, until a viable option comes out that doesn't make people think they're going to get VAC banned for such a thing. Almost all of the general script kiddies that run around with jetbot.lua are stopped dead in their tracks.
[QUOTE=JIAC;20920929]Uhhh SE2 works pretty well, you know. It doesn't catch people that bypass it, but that's what admins are for, since the people that are bypassing it in the first place are in the minority. That is, until a viable option comes out that doesn't make people think they're going to get VAC banned for such a thing. Almost all of the general script kiddies that run around with jetbot.lua are stopped dead in their tracks.[/QUOTE] VAC is never going to be used in garrys mod garry likes to strike fear into people
[QUOTE=|King Flawless|;20921058]VAC is never going to be used in garrys mod garry likes to strike fear into people[/QUOTE] Never say never.
[QUOTE=|FlapJack|;20921199]Never say never.[/QUOTE] It wont happen
[QUOTE=|King Flawless|;20921739]It wont happen[/QUOTE] It's possible an engine change might bring on working VAC.
[QUOTE=|FlapJack|;20921760]It's possible an engine change might bring on working VAC.[/QUOTE] Why didnt orangebox engine change do it then
Garry's Mod is on its own build of the OB engine. It's close to TF2's one, but it isn't the exact same.
I think it's built on the ep2 engine actually. Which is a part of OB, as is TF2.
VAC would kill all the fun clientside modules...
I want to see something that keeps players from being banned for their files incorrectly downloading or blank lua files being frozen in lua_temp interfering with SE2. As well as the normal inconsistencies being removed from Gmod which get people automatically banned.
[QUOTE=|King Flawless|;20921958]Why didnt orangebox engine change do it then[/QUOTE] Because. Just wait 'till ep3 and we have vac I want to see the look on your face not so flawless anymore :fuckyou:
VAC is not in gmod because the modules made for gmod require a method used to usually hack games, therefore it is not enabled and will never be enabled. There's a really, really easy way to stop all scripts from loading and that is to lockdown the actual Lua C code versus the gmod interface. Garry should also research a thing or two about assembly before trying because the current SE1 and SE2 are so easily bypassable it's laughable.
Only way SE could get better (no bypassing) is if there was some sort of super being to watch over the server when he/she can..and do a good job of it...oh wait.. [editline]01:36AM[/editline] Oh and I think there should be a way to allow certain things..like lets say I wanted to make a panel that would have some useful darkrp commands..so i can be like "yo kidz im leet now check dis shit out" when I'm playing with my 9 year old brethren on my fav server.
[QUOTE=Gbps;20926718]VAC is not in gmod because the modules made for gmod require a method used to usually hack games, therefore it is not enabled and will never be enabled. There's a really, really easy way to stop all scripts from loading and that is to lockdown the actual Lua C code versus the gmod interface. Garry should also research a thing or two about assembly before trying because the current SE1 and SE2 are so easily bypassable it's laughable.[/QUOTE] Then why don't you do us all a great favor and tell him what he should be doing? It's not good enough to say Scriptenforcer is shit, do something about it. [editline]1[/editline] This is directed at anyone saying they know better. Most of the time they look like they're talking out of their [dog's] ass.
I think the best thing to come from SE3 would be the courtesy of it working.
[QUOTE=Gbps;20926718]VAC is not in gmod because the modules made for gmod require a method used to usually hack games, therefore it is not enabled and will never be enabled. There's a really, really easy way to stop all scripts from loading and that is to lockdown the actual Lua C code versus the gmod interface. Garry should also research a thing or two about assembly before trying because the current SE1 and SE2 are so easily bypassable it's laughable.[/QUOTE] Virtual Machined lua_shared + remove useless exports + mess up the lua_State structure(already done) + sign byte code in Proto objects. All secure lua functions check where the call originated from(top of the C stack), ensure it comes from client.dll or server.dll or lua_shared.dll. And last of all, Garry should be signing clientside dlls. If a non signed dll is loaded, you can't join a SE game. But all this would still be unstopped by CreateRemoteThread, WriteProcessMemory, ReadProcessMemory and the huge range of debug functions provided by M$.
The lua_State structure is messed up?
The order of the members in the lua_State are not the same as normal lua. This kindof stops people using their own lua functions to load code.
I personally could care less that SE can be defeated using whatever methods, I just want to see it work properly and for Garry's Mod to stop freezing empty folders in lua_temp and downloading compressed .bz2 files into the cache/dua folder so the file won't download. This happens to about 10% of my clients because of crashing problems I have emailed garry about 2-3 times now. Not only that but for what it seems like for no reason clients will have mismatched core files (mainly includes/util.lua) and will be kicked or their gamemode will completely refuse to load and they won't be kicked (doesn't even make sense..). 15% of clients won't even fucking send their MD5 and it will stay as Undefined which I hear is some magical exception to SE which won't be kicked by SE2 either. Fuck binary module bypasses, fuck memory editing, fuck assembly. SE doesn't work anyways and at least 15% of clients either have an incorrect MD5, stay Undefined or have frozen/uncompressed files mucking up their lua_temp. I would think about using SE2 but cutting off 15% of players compared to around 4-5% which can be fixed easily with a little instruction but has a method which can be bypassed by my friend's 8 year old brother to use JetBot anyways is as good as I am going to get.... I don't want a SE3, I just want SE to work before any other protection is added. Why add protection to something that is still broken?
Sorry, you need to Log In to post a reply to this thread.