MESSAGE
| DATE | 2017-01-26 |
| FROM | Rick Moen
|
| SUBJECT | Re: [Hangout-NYLXS] coreboot and payloads
|
Quoting Ruben Safir (ruben-at-mrbrklyn.com):
> no, the hardware us pulled, to my understanding.
Ah, socketed BIOS ROM? That's actually very nice. I have a Lenovo T60
of which that's not true: The BIOS chip is surface-mounted on the
motherboard.
> > alteration of the booting kernel's bootloader parameters, and can add
> > the word 'single', while also removing 'quiet' or any rubbish like that,
> > that was inserted to show you soothing pictures and hide boot-process
> > information.
> >
>
> that doesn't work fwiw. single is not a grub key word.
I did not _say_ 'single' is a GRUB key word. Will you pay closer
attention, please?
It's a parameter to the booting kernel, and has meaning to Linux. It
gets passed along to PID 1, the init process, which in turn acts on that
instruction to put you into single-user mode, which usually means a
single /bin/sh process with root authority (and the root filesystem
mounted read-only). (Some Linuxes do this with the root FS mounted
read-only; some do not.) If you get that far, you are golden, because
you can then do 'mount -o rw,remount /', mount any other filesystems you
really need at that moment (probably none), and change the installed
system's root-user password to whatever you want. Having done that, as
per usual, you make sure the file cache has been flushed to disk by
doing
# sync
# sync
# sync
...and then rebooting.
This is all Linux 101, Ruben. This is the standard way of breaking into
a system from the physical console if you presently lack the root
password.
And I might add that sometimes, if some idiot has taken measures to
try to prevent the local console user from getting to root authority,
it's useful to pass the booting kernel 'init=/bin/sh' rather than kernel
keyword 'single'. This instructs the booting kernel to _not_ load the
regular PID 1 init process, but rather a single root-user /bin/sh
process with the root filesystem mounted read-only.
If you get that far, proceed as deescribed above. Again, this is
totally Linux 101, sir.
> Yeah - thats it. You need to declare the kernel to boot first, not
> simple when you have no os running to do a dmesg, and then you can run a
> nornmal live disk and do an install. bios features need to run through
> something called nvram... something or other. When I get home I'll post
> the exact name. Its a command line program that flips bios bits.
I see you do a lot of basically pointless talking, here, but zero
attempt to answer the implied question about whether you can get control
of GRUB by timely pressing of a Shift key or Esc keystroke.
If you can get GRUB's attention, then you can alter the booting kernel's
command line (if some idiot hasn't forced GRUB to lock out the local
administrator from doing so). If you can do _that_, then you can get
single-user mode as the root use. And if you can do _that_, you can
change the root password, and you now have total control of your system.
Stop ignoring the expert trying to help you, Ruben. Answer the
goddamned implied question, do what I suggest, and report back
competent, precise, concise diagnostic information. OK? Stop acting
like the flakiest and most ungrateful of novices. Sheesh. You'd think
you were being paid to make damned sure I was unsuccessful in helping
you gain control of your system.
_______________________________________________
hangout mailing list
hangout-at-nylxs.com
http://www.nylxs.com/
|
|
