This bug was fixed in the package sudo - 1.7.2p1-1ubuntu5.5
---
sudo (1.7.2p1-1ubuntu5.5) lucid-proposed; urgency=low
* toke.{cl}: avoid duplicate fclose() of the sudoers file (LP: #553786)
- http://www.sudo.ws/repos/sudo/rev/164d39108dde
-- Marc DeslauriersThu, 22 Nov 2012
After installing sudo package from proposed, there is no longer crash:
sudo ls
sudo: /etc/sudoers.d/mama is mode 0644, should be 0440
>>> /etc/sudoers.d/README: /etc/sudoers.d/mama near line 18 <<<
sudo: parse error in /etc/sudoers.d/README near line 18
sudo: no valid sudoers sources found, quitti
** Branch linked: lp:ubuntu/lucid-proposed/sudo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/553786
Title:
*** glibc detected *** sudo: double free or corruption
To manage notifications about this
Hello Daniel, or anyone else affected,
Accepted sudo into lucid-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/sudo/1.7.2p1-1ubuntu5.5
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.
** Description changed:
- Binary package hint: sudo
+ [SRU]
- Lucid beta1, sudo 1.7.2p1-1ubuntu4. I added a file with incorrect
- permissions under /etc/sudoers.d/, and while that needed fixing, sudo(8)
- certainly shouldn't react like this:
+ [Impact]
+ Lucid users who create a file in /etc/su
Upstream fix: http://www.sudo.ws/repos/sudo/rev/164d39108dde
** Also affects: sudo (Ubuntu Lucid)
Importance: Undecided
Status: New
** Changed in: sudo (Ubuntu Lucid)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I have been hit by this bug and it's *extremely nasty*. I am instantly
locked out of my system with no way of fixing it.
Things like these MUST NOT happen. I get from this bugreport that there
is a fix.
BACKPORT THIS FIX TO LUCID!
--
You received this bug notification because you are a member o
Has Ubuntu changed its meaning of LTS? This issue still exists in Lucid.
Keith Baker already pointed out that the issue was fixed at least as
early as Natty. Can we get the fix back-ported to Lucid? Is there any
reason this shouldn't be considered critical as it can lock out
legitimate administrat
This bug appears to be fixed in precise. A message is output about the
wrong permissions, but sudo itself works correctly.
** Changed in: sudo (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I've just been bitten by this bug yet again. I've had to request to my
administrator to reboot our server into recovery mode to remove the
file. Why isn't a bug that locks administrators out of the operating
system (in an otherwise well-configured environment) not considered a
critical bug? The onl
Just happened to me on a fresh and updated lucid server installation.
This is really annoying since the server was a plain router. No keyboard
or monitor was connected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
Tried same thing on desktop version of natty. There the problem seems
fixed.
Still I'd consider this bug critical since lucid is the current long-
term-support version.
** Tags added: lucid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: sudo (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/553786
Title:
*** gl
How do you change the file rights if sudo doesn't work nor you have a
root password set nor you have direct access to the server to reboot
into single mode?
IMHO, this bug should be set as CRITICAL, given that you are "banned"
from administrate a remote server.
--
You received this bug notificat
Confirmed also on Ubuntu 10.4 - 1.7.2p1-1ubuntu5.2 . Changing the file
rights from 644 to 440 "fixed" it.
--
*** glibc detected *** sudo: double free or corruption
https://bugs.launchpad.net/bugs/553786
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
15 matches
Mail list logo
