Installer.exe is still safe af
Had to install a VPN for work, and if you didn’t have a rhel-based distros you had to use a bash install script, and the installed executable had embedded bash and sh scripts. Needless to say I ran that thing in a docker container.
How did you get it to work? I can’t seem to figure out how to get my container VPN to connect with the host (and the containerized systemd daemon.service just crashes).
For me it had to be run with --privileged and --network=host
For some reason I also had to do “ip r add {remote IP}/{mask} via {the public IP assigned by the vpn}”. A friend who knows more about networking found that out for me though, so I’m not entirely sure about it.
Wouldn’t running it on privileged mode cancel out whichever safety measures of running that script in a container?
Somewhat, but it’s not a virus. It’s contained to it’s own file system unless it does something really stupid, and I can easily remove the while whole thing. But the reason i needed it privileged is because it loads the ppp kernel module, so if you know a way to do that without privileged mode, lmk.
AUTOEXEC.BAT has entered the chat
_AUTOEXEC.BAT.RAR
^password ^is: ^123
Instructions: when windows prompts you, click on install anyways.
curl $URL | sudo bashanyone?I non-ironically like this approach for package managers (cargo, gvm, conda, poetry, etc), because I eventually have problems when installing a manager with another manager.
