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

To: tech-kern%netbsd.org@localhost, Emmanuel Nyarko <emmankoko519%gmail.com@localhost>
Subject: Re: Proposal to automatically make the owner/user of an accepted socket the current process
From: Jonathan Stone <kiwi_jonathan%yahoo.com@localhost>
Date: Thu, 5 Jun 2025 15:17:14 +0000 (UTC)

Have you considered making this an "opt-in" with a setsockopt() to enable/disable the change?
And maybe a sysctl to set the system-wide default for processes which don't explicitly set that setsockopt()? Or does that "go without saying"?

if nothing else, that lets the adventurous experiment with the change, for specific (modified and recompiled) services, without affecting anything else.

Follow-Ups:
- 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

Prev by Date: 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: 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