@LegendarySpork said:
@w0rtw0rt that is fair enough as long as there is some reasonable inferential way to get to the appropriate background information. The maddening part for me is simply not turning up what I’ve needed on google or man pages.I have no issues with doing plenty of homework. Fortunately folks have been sharing some general references. I still am lost but at least at this point I have stuff to research.
HTB and the box creators get to make the rules but I’m just saying that if you want to keep my interest there has to be at least a viable research path.
PS right now I am working through the mighty waterfowl example network diagram and configuration. Good stuff to know.
I will admit I am a little biased with this particular box because my background is in networking and security architecture. Therefore, I have a lot of background in this kind of stuff (although from the linux side of things, it’s a new ballgame). However, the knowledge you gain from this box would be immensely helpful for either offensive or defensive security specialists because of the literal construction of a configuration. Understanding what’s going on in the engine, so to speak, so that you can know exactly what’s going on.
All this to say is that every single resource you need is out there. There is nothing in the construction of the configuration that is left to chance here. It’s truly not a guessing game. There are definitely ways that are explained to get around things you do not or cannot know. This goes for the user portion and the root portion.