mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 2/2] avahi: add user to /etc/passwd
Date: Wed, 17 Dec 2014 09:30:13 +0100	[thread overview]
Message-ID: <cc7a7db70ab262c70e6c0052bf7564a1@localhost> (raw)
In-Reply-To: <1418768450-15876-1-git-send-email-r.schwebel@pengutronix.de>

Hei hei, 

Am 2014-12-16 23:20, schrieb Robert Schwebel:
> We re-use the uids from Debian.

Which are not fixed. See from the desktop I'm working on:

% grep avahi /etc/passwd
avahi:x:105:112:Avahi mDNS daemon,,,:/var/run/avahi-daemon:/bin/false

Same for messagebus btw:

% grep messagebus /etc/passwd
messagebus:x:101:105::/var/run/dbus:/bin/false

Or systemd (on another machine):

% grep systemd /etc/passwd
systemd-timesync:x:107:112:systemd Time
Synchronization,,,:/run/systemd:/bin/false
systemd-network:x:108:113:systemd Network
Management,,,:/run/systemd/netif:/bin/false
systemd-resolve:x:109:114:systemd
Resolver,,,:/run/systemd/resolve:/bin/false
systemd-bus-proxy:x:110:115:systemd Bus Proxy,,,:/run/systemd:/bin/false

AFAIK Debian uses the next free uid when a service is installed for the
first time and creates its system users. See `man 8 adduser`.

>  sshd:x:100:65534:SSH Server:/var/run/sshd:/bin/false

Three different UIDs on three different Debian machines: 100, 103, 114 …
I would probably find even more.

>  messagebus:x:103:104:messagebus:/dev/null:/bin/false
> +avahi:x:107:115:Avahi mDNS daemon:/var/run/avahi-daemon:/bin/false
>  systemd-network:x:202:202:systemd-network:/dev/null:/bin/false
>  systemd-resolve:x:203:65534:systemd-resolve:/dev/null:/bin/false
>  systemd-timesync:x:203:65534:systemd-timesync:/dev/null:/bin/false

Long story short: there are no fixed UIDs in Debian, just something like
classes. See "9.2.2 UID and GID classes" on
https://www.debian.org/doc/debian-policy/ch-opersys.html for details.

Of course its fine to choose any default uid/gid for ptxdist, but
re-using them from Debian is misleading. ;-)

HTH & Greets
Alex

-- 
»With the first link, the chain is forged. The first speech censured,
the first thought forbidden, the first freedom denied, chains us all
irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601  D1D5 8FBA 7744 CC87 10D0 ***

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2014-12-17  8:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-16 22:20 Robert Schwebel
2014-12-17  8:30 ` Alexander Dahl [this message]
2014-12-17  9:31   ` Robert Schwebel
2014-12-17 15:29     ` Uwe Kleine-König

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cc7a7db70ab262c70e6c0052bf7564a1@localhost \
    --to=post@lespocky.de \
    --cc=ptxdist@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox