Explore >> Select a destination
|
You are here 
|
outflux.net | ||
| | | | |
gtfobins.github.io
|
|
| | | | | [AI summary] The text explains various methods to exploit Perl scripts for privilege escalation and maintaining access in restricted environments through techniques like reverse shells, SUID binaries, and capability manipulation. | |
| | | | |
hjr265.me
|
|
| | | | | I have lines like these in my /etc/hosts file: 127.0.0.1 toph.local 127.0.0.1 drafts.toph.local 127.0.0.1 quiz.toph.local I can run development servers locally and access them over .local hostnames (e.g. toph.local) instead of the loopback IP addresses (e.g. 127.0.0.1). It works fine. But every time I start working on a new project, I needed to add a new line to the /etc/hosts file. It didn't sit right with me. I should be able to point all *. | |
| | | | |
shibumi.dev
|
|
| | | | | How to identify the Operating System (OS) via ping utils | |
| | | | |
rolisz.ro
|
|
| | | I often need to set up a VM with a server to run some ML models. While I could package things in Docker and deploy them like that, whenever possible, I like to do things more directly, using systemd services. To create a systemd service, create a file called /etc/ | ||
