I’ve gotten too the part where you move into the folder but I get this error when in the machine. I reset it and got it again can someone help ?
Welcome to the Luvit repl!
Uncaught exception:
[string “bundle:deps/readline.lua”]:485: attempt to call method ‘set_mode’ (a nil value)
stack traceback:
[string “bundle:deps/readline.lua”]:485: in function ‘readLine’
[string “bundle:deps/repl.lua”]:198: in function ‘start’
[string “bundle:main.lua”]:137: in function ‘main’
[string “bundle:init.lua”]:49: in function <[string “bundle:init.lua”]:47>
[C]: in function ‘xpcall’
[string “bundle:init.lua”]:47: in function ‘fn’
[string “bundle:deps/require.lua”]:310: in function <[string “bundle:deps/require.lua”]:266>
so did someone break the machine as this happens between resets or is this an intended thing ? it seems like its having issues with the program it self and loading the needed functions ?
I’ve gotten too the part where you move into the folder but I get this error when in the machine. I reset it and got it again can someone help ?
Welcome to the Luvit repl!
Uncaught exception:
[string “bundle:deps/readline.lua”]:485: attempt to call method ‘set_mode’ (a nil value)
stack traceback:
[string “bundle:deps/readline.lua”]:485: in function ‘readLine’
[string “bundle:deps/repl.lua”]:198: in function ‘start’
[string “bundle:main.lua”]:137: in function ‘main’
[string “bundle:init.lua”]:49: in function <[string “bundle:init.lua”]:47>
[C]: in function ‘xpcall’
[string “bundle:init.lua”]:47: in function ‘fn’
[string “bundle:deps/require.lua”]:310: in function <[string “bundle:deps/require.lua”]:266>
so did someone break the machine as this happens between resets or is this an intended thing ? it seems like its having issues with the program it self and loading the needed functions ?
Does this also happen, when you just load the repl, without any parameters?
This is my first box ever. It took me a few hours.
Once I became root, I used my root privileges to chattr +i all of the flags and the .bash_history of root and the other two accounts after clearing them. This way no bash history can be recorded, preventing it from giving away clues from other users. Only root will be able to delete critical files now. This could have been done “out of the box” by the author.
This is my first box ever. It took me a few hours.
Once I became root, I used my root privileges to chattr +i all of the flags and the .bash_history of root and the other two accounts after clearing them. This way no bash history can be recorded, preventing it from giving away clues from other users. Only root will be able to delete critical files now.
Well, on your server and until it is reset, yes.
This could have been done “out of the box” by the author.
True - and certainly worth suggesting. I’ve found quite often Linux boxes desperately need the creator to make critical files immutable - OpenAdmin was a good example of this.
My first non-walkthrough machine ever! I’m so happy
First i blocked myself by using php shell instead of planned backdoor route :trollface: (throwing logs under my feet)
Then i tried to get user by launching external script instead of using the compiler :trollface:
And at last i tried to use totally wrong scripts for reverse shell :trollface:
But in the end it all came through! Big thanks to the Author! I learned a lot today!