Cita:
16:31 < o2T7> Hi, how to repair sudoers.conf --without root perms-- when getting "sudoers file: syntax error" ???
16:31 < o2T7> Remotely
16:32 < Bushmills> o2T7: just su, then fix it
16:32 < inigo> o2T7, do you have a backup system ?
16:32 < doublehp_> o2T7: user cant get root ?
16:32 < o2T7> Bushmills: I'm afraid that there are no root privileges at all
16:33 < doublehp_> o2T7: ssh -l root :)
16:33 < o2T7> doublehp_: neither root pass for ssh :S
16:33 < jelly-home> o2T7: first, su to root. second, it's "/etc/sudoers", not "sudoers.conf". third, fix it
16:33 < doublehp_> o2T7: if you REALLY cant get root at all, i got a trick, 2mn
16:33 < RoyK> o2T7: type 'visudo'
16:33 < Bushmills> o2T7: fire the person who broke sudo without providing an alternative way to become root
16:34 < o2T7> Bushmills: heh, that's probably the best solution xD
16:34 < o2T7> RoyK: Visudo needs root privs too
16:34 < jelly-home> !tell o2T7 -about forgot root password
16:34 < doublehp_> n-iCe: I asked twice mplayer's logs !
16:35 < doublehp_> o2T7: reboot, and pass this to kernel arguments: init=/bin/bash
16:35 < RoyK> o2T7: if course...
16:35 < doublehp_> o2T7: after boot, run : mount -o remount,rw /dev/hda1 / (or whatever your / is )
16:35 < o2T7> doublehp_: It must be done remotely
16:35 < doublehp_> o2T7: then, you have full access to system: run passwd to change root pass, edit any file
16:35 < RoyK> o2T7: that's the whole point - if you can't get root, missing the root password, boot on a cd and
change the root password
16:36 < doublehp_> o2T7: when done: mount -o remount,ro /dev/hda1 / ; sync
16:36 < jelly-home> o2T7: is there a reason you can't use "su"?
16:36 < doublehp_> o2T7: then you can reboot
16:36 < o2T7> jelly-home: Yes, no root pass
16:36 < jelly-home> o2T7: who set up that Debian system?
16:36 < doublehp_> o2T7: there are things that cant be done "for good security reasons"
16:37 < o2T7> I see it just lilke a privileges scalation, since there is no root privs at all and no phisical
access by now to the server.
16:37 < o2T7> doublehp_: Yes, and I thanks it ;)
16:37 < jelly-home> o2T7: sucks to be you. :-)
16:37 < RoyK> o2T7: boot on a debian install cd, mount the root fs from the disk somewhere, chroot into it,
passwd ... and you're done
16:37 < o2T7> RoyK: Nop, that needs phisical access too
16:38 < RoyK> o2T7: well, then you're probably fscked :P
16:38 < jelly-home> o2T7: if you often have to admin servers with no physical access, I recommend hardware with
remote console access, like most brand-name servers have.
16:38 < o2T7> heh, sure xD
16:39 < o2T7> jelly-home: Well, I'll do your recommendation ;)
16:39 < Bushmills> o2T7: no rescue system? net boot which you can select by web interface?
16:39 < jelly-home> o2T7: eg. HP has remote console, power/reset buttons, virtual serial and cdrom capabilities
(can mount and boot from remote iso images)
16:39 < o2T7> Bushmills: I don't know that
16:39 < RoyK> o2T7: with no root password and no sudo access, you won't get in...
16:39 < Bushmills> o2T7: find out
16:39 < o2T7> jelly-home: Yes, I translated some good stuff about that not long ago. Good tools indeed.
16:40 < jelly-home> o2T7: other vendors have similar stuff (dell, sun, ibm...)
16:41 < o2T7> jelly-home: Yes, the pity is that they're not standarized. Something a bit weird, being such a
vital issue.
16:42 < jelly-home> o2T7: I think some bits are standardized, but not much. google "IPMI"
16:42 < o2T7> Yes
16:43 < o2T7> I know, although didn't experiment with it directly
Por otro lado, el procedimiento recomendado ante la pérdida de root en nuestro sistema:
Cita:
16:34 <dpkg> methinks ifrp is 1) press 'e' to edit the kernel setting in the grub
command line (add 'init=/bin/sh' to the end of it) 2) 'fsck' your root file system, 3) 'mount -o
remount,rw /', 4) 'passwd root' 5) 'mount -o remount,ro /' 6) 'reboot -d -f' (exec /sbin/init should
work); For LILO (e.g. pre-sarge): 1) 'linux init=/bin/sh' at a lilo boot prompt (hold Shift while
booting), steps 2-6 are the same; yaboot: 1) 'Linux init=/bin/sh' at y
