A library Linux foothold is non-root. The tester still wants a user-level forward. What privilege constraint should they remember conceptually?
Select an answer to reveal the explanation.
Short Explanation
No root does not mean no pivoting—it means you work with the seats you are allowed to sit in. Low ports are often reserved; user-level listens usually live higher up. Plan the forward around the account’s real limits instead of wishing the OS would look the other way.
Full Explanation
Listening privileges on Unix-like systems typically restrict low-numbered ports to privileged accounts. A non-root foothold can still forward using ports and methods the user may bind, but planners must account for those limits. Domain Admin is not a universal prerequisite for every forward, nor does a shell erase OS bind rules. Privilege-aware planning keeps pivot attempts realistic.