<br><br><div class="gmail_quote">On Thu, Mar 13, 2008 at 4:30 PM, Nicolas François <<a href="mailto:nicolas.francois@centraliens.net">nicolas.francois@centraliens.net</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
tags 470745 upstream<br>
tags 470745 fixed-upstream<br>
thanks<br>
<br>
On Thu, Mar 13, 2008 at 01:30:45PM +0100, <a href="mailto:rasmussen.thomas@gmail.com">rasmussen.thomas@gmail.com</a> wrote:<br>
><br>
> If /etc/gshadow file has been changed so two otherwise non-identical groups apear with the same groupname, usermod will loop and use all memory on system if called.<br>
><br>
> Reproducable by performing this:<br>
> # groupadd tr<br>
> # groupadd rtr<br>
> # useradd -g tr tr<br>
> # perl -pi -e 's/rtr/tr/g' /etc/gshadow<br>
> # usermod -G tr tr<br>
> <observe usermod using memory and proc time><br>
><br>
> Tested and reproduced on latest (4.0r3) netinst iso image and updated with all packages.<br>
<br>
Thanks for reporting it.<br>
<br>
This is currently fixed in the upstream repository.<br>
The last usermod call will raise an error and request the /etc/gshadow<br>
file to be cleaned with grpck:<br>
<br>
Multiple entries named 'tr' in /etc/gshadow. Please fix this with pwck or grpck.<br>
usermod: error adding new shadow group entry<br>
<br>
I still need a few weeks (2?) before the next upstream release to prepare<br>
a snapshot and call for translations.<br>
<br>
I don't think this bug is that critical. I doesn't cause any corruption,<br>
and it occurs only in case of configuration errors, which do not appear if<br>
the administrators use the recommended tools for user/group<br>
administration. Thus I will not issue a fix for this bug.<br>
<br>
Also, I don't think it is worth doing a update for Etch.<br>
Any other opinions?<br>
</blockquote><div><br>I agree that this should not be seen as admins should use the dedicated toos, but I still see this as a quite serious bug because it will crash either the system or random services running on the system when it hits the maximum amount of memory. <br>
<br>I have ofcourse fixexd the error on our running systems so we no longer hit it, but I'd prefer that it was fixed in etch as we have quite many systems running etch.<br><br>Kind regards<br>Thomas<br></div></div>