[Pkg-shadow-devel] (forw) Bug#280212: lastlog: fails when high UIDs are present
Thu, 6 Jan 2005 07:10:30 +0100
(please respect Reply-To, possibly)
Thanks for report this, Steve. I forward this to Tomasz as upstream
for having his advice on the issue.
Steve, as release manager, you're aware of the situation of shadow
currently and the fact that I'm trying to build a maintenance team for
post-sarge maintenance of the package. In the meantime, I'm doing my
best (or less worse) for properly maintaining it in good shape.
As you didn't tag this bug report release critical, I guess you don't
consider it worth being fixed in sarge. Am I right?
If so, we'll probably deal with it post-sarge.
BTW, even if I know you're already wearing too much hats, you're
obviously welcome for joining the team..:-)
----- Forwarded message from Steve Langasek <firstname.lastname@example.org> -----
Subject: Bug#280212: lastlog: fails when high UIDs are present
Reply-To: Steve Langasek <email@example.com>, firstname.lastname@example.org
Date: Wed, 5 Jan 2005 19:19:44 -0800
From: Steve Langasek <email@example.com>
Attention was drawn to this bug on IRC today. Since using a 32-bit index
for a file that has more than one byte of data per entry makes it very
possible to have files that exceed a 32-bit file size limit, I agree that
this is a bug and should be fixed.
Two caveats, however:
- it is not safe to use the 64-bit flags in a program if it also exchanges
file-related structs with a library that does not have 64-bit support
enabled (I don't think this is a problem here)
- the 64-bit flags don't necessarily have the expected effect on platforms
that are natively 64-bit -- c.f. bug #280213 (hmm, what a coincidental bug
#) on exim. The safe way to do this seems to be to use the output of
----- End forwarded message -----