Re: Guidance on solving the username namespacing problem

2020-01-05 Thread Philipp Kern
Thanks again, Russ, Colin and Simon! On 1/5/2020 7:25 PM, Russ Allbery wrote: > 9.2.1 feels like the right spot to me. I think that's close to 9.2.2. We > could also reiterate that guidance in 9.2.2. > >>> --- a/policy/ch-opersys.rst >>> +++ b/policy/ch-opersys.rst >>> @@ -228,13 +228,16 @@

Bug#948115: Revise init script Policy based on GR result

2020-01-05 Thread Russ Allbery
Lorenzo Puliti writes: > I wonder if it make sense to encourage or even recommend to use the > interpreter in /lib/init/init-d-script for writing init scripts. > Or maybe just citing that there is an interpreter and say that > it's the preferred way to create init scripts, I don't know.. >

Bug#948115: Revise init script Policy based on GR result

2020-01-05 Thread Lorenzo Puliti
Package: debian-policy Version: 4.4.1.2 Followup-For: Bug #948115 Hi, > Writing the scripts > ~~~ > ... > +The ``start``, ``stop``, ``restart``, and ``force-reload`` options should > +be supported by all init scripts. Supporting ``status`` is recommended but > +not required.

Re: Guidance on solving the username namespacing problem

2020-01-05 Thread Russ Allbery
Colin Watson writes: > As Simon said, EF00-FFEF = 61184-65519 covers more than just netplan > (https://salsa.debian.org/debian/base-passwd/blob/master/README), and > several of the IDs allocated there in the vaguely recent past are hard > to change (their rationales included "needs to be the

Re: Guidance on solving the username namespacing problem

2020-01-05 Thread Colin Watson
[I haven't been following the rest of this discussion. Thanks for the CC - let me know if I'm egregiously missing anything.] On Sun, Jan 05, 2020 at 10:25:37AM -0800, Russ Allbery wrote: > Philipp Kern writes: > > It looks like the range must be contiguous, as it is compiled in[1]. > > What are

Re: Guidance on solving the username namespacing problem

2020-01-05 Thread Russ Allbery
Philipp Kern writes: > I fear that we might need a local policy hook for migrations. If we end > up renaming users that are actively referenced elsewhere, there might be > cleanup tasks that need to be performed in lockstep. > At the same time I'd strongly suggest that we do not go the way of >

Re: Guidance on solving the username namespacing problem

2020-01-05 Thread Simon McVittie
On Sun, 05 Jan 2020 at 17:16:58 +0100, Philipp Kern wrote: > On 1/4/2020 5:08 PM, Simon McVittie wrote: > > It's also worth noting that the 61184-65519 uid range used for DynamicUser > > by default collides with the rarely-used 6-64999 uid range for system > > users that are "globally

Re: Guidance on solving the username namespacing problem

2020-01-05 Thread Philipp Kern
Hey, thanks, Sam, Simon and Russ! That was all very helpful! Much appreciated! [Adding the systemd maintainers to the Cc for Simon's question below.] On 1/4/2020 5:08 PM, Simon McVittie wrote: > On Sat, 04 Jan 2020 at 13:52:51 +0100, Philipp Kern wrote: >> now that we are talking again about