Subj : Fresh install error
To   : StackFault
From : Accession
Date : Tue Jan 16 2024 01:53 pm

Hello StackFault,

On Tue, 16 Jan 2024 20:40:20 -0500, you wrote:

 S> MIS should not be run as root.

Okay. Whatever. While opinions are like assholes, this is another topic completely. What I was asking him is if he DID run it as root (even just once) it would ruin his permissions if in the future he started running it as a regular user, or even using sudo.

 S> You should use setcap instead to provide the MIS binary the capability
 S> to bind to privileged port using this command:

 S>   sudo setcap 'cap_net_bind_service=+ep' /path/to/mis

 S> This way, MIS can be started with a regular user and still be able to
 S> bind to a low port, without root privilege.

Thank you, Mr. Linux Guru.

....and all I was trying to say is even if you use sudo to start MIS, it binds to the low ports and passes permissions off to the user that used sudo immediately after. It was done on purpose by the developer himself. You can take it up with him if you want to argue about what should and shouldn't be done. *shrug*

To be fair, Synchronet also does this. And it seems so does just about anything that uses systemd if you use the USER and GROUP keywords in your .service file. So you may as well tell all those people how they should do it, too. ;)

Regards,
Nick

.... "Take my advice, I don't use it anyway."
--- Claws Mail 4.2.0 (GTK 3.24.38; x86_64-w64-mingw32)
 * Origin: _thePharcyde distribution system (Wisconsin) (21:1/200.0)

.