[-- Attachment #1: Type: text/plain, Size: 761 bytes --] Some programs (e.g. xpra) create files based on the hostname and it'd be useful to have control of this parameter. There's another reason to have custom hostnames within the container as well. From the guix manual[1]: While this will limit the leaking of user identity through home paths and > each of the user fields, this is only one useful component of a broader > privacy/anonymity solution—not one in and of itself. > Right now my hostname is leaking to the container and that is certainly a hint to my main persona. [1] https://guix.gnu.org/manual/en/html_node/Invoking-guix-environment.html [2] https://man.archlinux.org/man/core/man-pages/uts_namespaces.7.en -- Vinícius dos Santos Oliveira https://vinipsmaker.github.io/ [-- Attachment #2: Type: text/html, Size: 1212 bytes --]
Hi Vinícius,
Vinícius dos Santos Oliveira <vini.ipsmaker@gmail.com> skribis:
> Right now my hostname is leaking to the container and that is certainly a
> hint to my main persona.
AFAICS, ‘guix environment -C’ already starts contains in a separate UTS
namespace (see ‘%namespaces’ in (gnu build linux-containers)).
However, it does not attempt to change the host name, since you get a
non-zero UID inside that environment, you cannot change it.
What we could do is add a ‘--uid’ option to ‘guix environment’ and/or a
‘--host-name’ option.
WDYT?
Thanks,
Ludo’.
Em sáb., 17 de abr. de 2021 às 13:10, Ludovic Courtès <ludo@gnu.org> escreveu: > Hi Vinícius, Hi Ludovic, > What we could do is add a ‘--uid’ option to ‘guix environment’ and/or a > ‘--host-name’ option. > > WDYT? The --host-name option would work for me. That'd be enough to control xpra unix socket names. -- Vinícius dos Santos Oliveira https://vinipsmaker.github.io/