-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature: Filestealer truncate
doesnt work with gluapack, possible ideas / solutions
#49
Comments
truncate
doesnt work with gluapack, possible ideas / solutions
Someone wrote a bypass in rust here https://github.com/imfriendly/gmod-filestealer-rs |
Using I imagine the best solution is to add a function or variable to the gluasteal environment that gives the user the ability to decide whether or not to write a file, per execution of gluasteal.lua. For example: if gluasteal.SOURCE:find("some_packer()()") then
gluasteal.SetShouldWriteFile(false)
end or, even better, return a second value from gluasteal.lua (alongside the should load value which is already present): local should_load = not gluasteal.SOURCE:find("while true do end")
local should_write = not gluasteal.SOURCE:find("some_packer()()")
return should_load, should_write This way, any hard coded logic for a specific packer (which is fragile by nature) is moved from the source code of gluasteal to the user's gluasteal.lua file. I suppose a I would love to hear thoughts on this or any better solutions to the problem. |
If you can test it, please do. You can download the pre-compiled update from the bottom of this page. |
Just tested it, works great! I like the idea of write_mode |
Billy added a way to opt out. |
Describe the issue
Servers that run gluapack()() don't work with
write_mode
truncate
but work withappend
. This was expected when truncate was introduced and is logical. It might be cool to have gluapack automatically detect gluapack or other kinds of script steal preventions and "bypass them", i know this sounds and likely painful to do. But having the option to specifically disable known preventions like gluapack might be useful to people as truncate is a preferrable alternative for servers that don't run these preventions.Maybe a complete different way of solving this would be a mode where only new code would be appended to the file while old code would still be kept.
Extra information
Might be useful, https://www.unknowncheats.me/forum/garry-s-mod/486883-gluapack-bypass.html
The text was updated successfully, but these errors were encountered: