Re: Proposal to automatically make the owner/user of an accepted socket the current process

To: Emmanuel Nyarko <emmankoko519%gmail.com@localhost>
Subject: Re: Proposal to automatically make the owner/user of an accepted socket the current process
From: Jason Thorpe <thorpej%me.com@localhost>
Date: Thu, 5 Jun 2025 18:42:51 -0700

> On Jun 5, 2025, at 9:36 AM, Emmanuel Nyarko <emmankoko519%gmail.com@localhost> wrote:
> 
> Errmmm, I was thinking that it maybe becomes a default behavior.
> 
> I mean every socket should be owned by the process that the socket was created for.

This actually seems not that great.  It’s de rigueur to have a more privileged process create a socket (or other sort of file descriptor) in a controlled fashion to pass off to a less-privileged process.  This should be opt-in behavior on a per-file descriptor basis.

-- thorpej

Follow-Ups:
- Re: Proposal to automatically make the owner/user of an accepted socket the current process
  - From: Emmanuel Nyarko
- Re: Proposal to automatically make the owner/user of an accepted socket the current process
  - From: Emmanuel Nyarko

References:
- Proposal to automatically make the owner/user of an accepted socket the current process
  - From: Emmanuel Nyarko
- Re: Proposal to automatically make the owner/user of an accepted socket the current process
  - From: Jonathan Stone
- Re: Proposal to automatically make the owner/user of an accepted socket the current process
  - From: Emmanuel Nyarko

Prev by Date: Re: Proposal to automatically make the owner/user of an accepted socket the current process
Next by Date: Re: Proposal to automatically make the owner/user of an accepted socket the current process
Previous by Thread: Re: Proposal to automatically make the owner/user of an accepted socket the current process
Next by Thread: Re: Proposal to automatically make the owner/user of an accepted socket the current process
Indexes:

Home | Main Index | Thread Index | Old Index