Literally my first thought when reading the article: "oh look- somebody else whining without RTFM."

I kept waiting for the author to mention capabilities, and give some reason why they aren't ideal- nope. The author is (was) simply oblivious.

I believe this has been the recommendation for quite some time. It's how users are able to use ping, for example.

That said, I kinda agree with the author that it feels weird today. And the vast majority of people will just reach for the sudo hammer instead of researching to find setcap, which is a security nightmare.

I'd probably argue keeping the idea of privileged ports, but not having it enabled by default anymore, I guess.

Saw the title and came here to post this; simple and effective.

I use this in combination with `kubectl port-forward` and `/etc/hosts` almost daily to easily proxy to internal services.

I don't want to delegate the port to a program. I want to delegate it to a user. The user should be able to open the port with any server he wants. Apache today, Django tomorrow - fine by me. Furthermore no one else should be able to run the server, they could set malicious arguments which again I don't want. Oh and finally it can get any port it wants with that CAP. I want it to only be allowed one specific port.