Bug#314539: [Pkg-shadow-devel] Bug#314539: please remove UMASK from login.defs

[Tomasz Kłoczko]

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--568760595-1476478048-1119275256=:28564
Content-Type: TEXT/PLAIN; charset=UTF-8
Content-Transfer-Encoding: QUOTED-PRINTABLE

On Mon, 20 Jun 2005, Tomasz K=C5~Boczko wrote:

> On Fri, 17 Jun 2005, martin f krafft wrote:
>=20
> > Package: login
> > Version: 1:4.0.3-31sarge5
> > Severity: wishlist
> >=20
> > Since any login session these days will invoke a shell, there is no
> > point in having login.defs set the umask -- the shell will override
> > it anyway. Thus, so that people do not have to decide between
> > login.defs and profile when trying to set an umask globally,
> > I suggest login.defs removes the setting.
>=20
> Only for describe how it is in shadow > 4.0.3: login and su from upstream=
=20
> source tree uses login.defs::UMASK only in case when shadow was compiled=
=20
> without PAM support.
>=20
> I just found lib/getdef.c have UMASK entry in part not dependent USE_PAM=
=20
> but I'll move this ASAP to part !USE_PAM.

Moment, wait .. login.defs::UMASK is also used in useradd, newusers ;>

kloczek
--=20
-----------------------------------------------------------
*Ludzie nie maj=C4=85 problem=C3=B3w, tylko sobie sami je stwarzaj=C4=85*
-----------------------------------------------------------
Tomasz K=C5=82oczko, sys adm @zie.pg.gda.pl|*e-mail: kloczek@rudy.mif.pg.gd=
a.pl*
--568760595-1476478048-1119275256=:28564--