On Fri, 2022-02-25 at 02:45 -0600, Daniel Lewart wrote:
> Also "sudo apt install openssh-server" warns:
> useradd warning: sshd's uid 116 outside of the UID_MIN 1000 and
> UID_MAX 6 range.
Daniel:
Thanks for making note of this. Using "-r" does solve the issue, but
more needs to be done
Debian Adduser Developers,
Also "sudo apt install openssh-server" warns:
useradd warning: sshd's uid 116 outside of the UID_MIN 1000 and
UID_MAX 6 range.
Tested patch which keeps options in alphabetic order is below.
Thank you!
Daniel Lewart
Urbana, Illinois
---
diff -ru
On Tue, 2022-02-22 at 15:02 +0100, Marc Haber wrote:
> adduser --system should enforce policy for system users. The local
> administrator is free to ignore Debian policy as they see fit. adduser
> should not enforce things on the local admin that don't apply to them.
>
> Maybe we add, some time
On Sun, Feb 13, 2022 at 01:52:14PM -0500, Jason Franklin wrote:
> On Sun, 2022-02-13 at 19:18 +0100, Marc Haber wrote:
> > On Sun, Feb 13, 2022 at 12:27:26PM -0500, Jason Franklin wrote:
> > > That warning is not emitted here when "-r" is added to the call made
> > > from within adduser. The range
On Sun, 2022-02-20 at 10:03 +0100, Ricardo Fraile wrote:
> Only to point that adduser is the recommended way to handle accounts in
> maintainer scripts [1] and Debian Code Search reports 267 packages using
> it [2], but dh_sysusers [3] seems to handle the same task on the
> packages and works
Only to point that adduser is the recommended way to handle accounts in
maintainer scripts [1] and Debian Code Search reports 267 packages using
it [2], but dh_sysusers [3] seems to handle the same task on the
packages and works with useradd under the hood too.
[1] -
On Sun, 2022-02-13 at 19:18 +0100, Marc Haber wrote:
> On Sun, Feb 13, 2022 at 12:27:26PM -0500, Jason Franklin wrote:
> > That warning is not emitted here when "-r" is added to the call made
> > from within adduser. The range discrepancy needs to be sorted out with
> > discussion, I think.
>
>
On Sun, Feb 13, 2022 at 12:27:26PM -0500, Jason Franklin wrote:
> That warning is not emitted here when "-r" is added to the call made
> from within adduser. The range discrepancy needs to be sorted out with
> discussion, I think.
Policy also helps here, it's rather explicit in defining the uid
On Sun, 2022-02-13 at 18:14 +0100, Marc Haber wrote:
> Should useradd emit a warning in this case? I mean, we WANT the low UID
> in this case. Is it inside the limits of a low-level tool to impose its
> own standards on the system or is this possible a bug in useradd?
As part of this bug, we will
On Sun, Feb 13, 2022 at 12:09:44PM -0500, Jason Franklin wrote:
> I also came across this warning when investigating this bug.
>
> When I get this bug fixed, the warning will go away.
Should useradd emit a warning in this case? I mean, we WANT the low UID
in this case. Is it inside the limits of
On Sun, 2022-02-13 at 16:04 +0100, Ricardo Fraile wrote:
> Adding _tuptime user...
> useradd warning: _tuptime's uid 106 outside of the UID_MIN 1000 and UID_MAX
> 6 range.
> Created symlink /etc/systemd/system/multi-user.target.wants/tuptime.service →
> /lib/systemd/system/tuptime.service.
>
Package: adduser
Version: 3.118
Followup-For: Bug #1004710
X-Debbugs-Cc: rfra...@rfraile.eu
Dear Maintainer,
I think that I received a warning related to this issue. This is the related
information:
* What led up to the situation?
Installing tuptime package
* What exactly did you do
12 matches
Mail list logo
