0xD

Have fun exploring! I just have a simple Raspberry Pi at home with a few services, after working with this stuff all the time I rarely feel like tinkering at home :D

That is not overcompensation, that is risk management 101.

No, it's just the number of a specific signal.

https://www.man7.org/linux/man-pages/man7/signal.7.html

Skill issue.

You cannot catch SIGKILL.

https://stackoverflow.com/questions/2541597/how-to-gracefully-handle-the-sigkill-signal-in-java/2541618#2541618

It is the collateral of political ignorance.

Feel like I'm destroying the dataset with QWERTY so I'll wait until QWERTZ is available :)

Memory is still structured like a file and referenced over addresses, we just call it something else.

Your command needs to look something like this:

nmap -Pn -sVC -p- (IP) -o scan

-Pn skips the availability check per ping

-sVC performs a version and a script scan so you get more information

-p- scans ALL ports

-o puts out a file called scan.nmap

If you want you can share that output afterwards for further info.

Edit: You can also try enumerating the directories on the server if you find no content. I can help you with that if you want.

You sound like you're really fun and easy to work with.

It needs to be specific to be clear for its purposes. You can express everything in simpler terms but then you risk leaving things out of definitions. It's basically legal speak.

Normally, you'd read the scope of such a document to see whether it fits your purpose, then cherry-pick the chapters necessary. If something's unclear, you can google pretty much everything.

Doing that a few times will make it infinitely easier! You especially get to understand those broad, inaccessible definitions a lot easier.