[Pkg-mailman-hackers] [bsb@debian.org: Bug#186642: Must blame mailman preinst]

[Laszlo 'GCS' Boszormenyi]

--LQksG6bCIzRHxTLp
Content-Type: text/plain; charset=iso-8859-2
Content-Disposition: inline

Hi Siggy,

On Thu, Mar 25, 2004 at 09:00:02PM +0100, Siggy Brentrup <bsb@debian.org> wrote:
> this is an ancient bug no one was able to reproduce. IMO the bogus
> code might be from a ancient version (suidmanager comes to mind).
 I think it is reproducable if you remove the list uid/gid. I know some
sysadmin who is really scare and remove every uid/gid not currently in
use (it's cause more pain later IMHO, see this).

> I'm not yet decided how to handle this case. If we continue
> to use this code (after adding --system on addgroup), file
> ownership must be adjusted in the postinst.
 It would violate the LSB, so this is a no-go.

> Alternatively we can recreate list.list with uid/gid 38
> like this, bailing out when the situation requires admin
> interaction.
 This is the preferred action, list should have uid/gid 38. But instead
of doing it ourselves, I think a call for update-passwd would be better.
It's in base-passwd (essential, so it's present on every system). Sum:
do a test for list being uid/gid 38, if not, call update-passwd which if
fail, then we should exit with error, if not, all is good. What about this
route?

Cheers,
Laszlo/GCS

--LQksG6bCIzRHxTLp
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFAY8EoMDatjqUaT90RArb1AKCdwczW+HEHrSzWTVxBgVu/EA/7BwCcDNzo
TNh7mHnNdqK59TgdDbK7Z6g=
=Rqrk
-----END PGP SIGNATURE-----

--LQksG6bCIzRHxTLp--