This is the mail archive of the
mailing list for the glibc project.
Re: [PATCH,HURD] Allow to override the /servers/socket path
- From: Roland McGrath <roland at redhat dot com>
- To: Samuel Thibault <samuel dot thibault at ens-lyon dot org>
- Cc: libc-alpha at sources dot redhat dot com
- Date: Mon, 20 Sep 2010 23:20:27 -0700 (PDT)
- Subject: Re: [PATCH,HURD] Allow to override the /servers/socket path
- References: <20100920195606.GE5004@const.famille.thibault.fr>
> The patch below permits to override the /servers/socket path with the
> user's own preference.
What's the rationale for this?
As written, this is a new security hole. Any Hurd-specific environment
variables affecting libc behavior have to both use __secure_getenv and
be listed in EXTRA_UNSECURE_ENVVARS. It doesn't fit any existing use
to have an open-ended space of environment variable names, rather than
just a fixed name, so you'd have to change that too.
But, I don't see any need for this at all. The Hurdish thing to do is
to run with a crdir that has /servers/socket interposed with whatever
you wanted. In the Hurd, /servers is no more magical than /etc or any
other file name built into libc and other such places. The way to
change the file name resolution your processes see is with translators.