John Plocher wrote:
> Garrett D'Amore wrote:
> > I wonder if a small NOTE in the man page indicating that memory is not
> > cleared, and therefore fast reboot should not be used to boot to
> > alternative and untrusted environments is appropriate.
>
> I would consider this advice or TCA at most
I agree. I never meant to imply anything stronger than that. Sorry if
that wasn't clear.
>
> If I have access to a system, I can compromise it anyways, and if
> there are trojan horses out there, a note in a manpage can't even
> hope to address the problem.
>
> "fast reboot doesn't zero out memory" is a good note,
>
> "fast reboot... alt BE...malicious trojan..." begs the question of why
> we don't point out all the *other* places trojans might bite you, as
> well as all the other potential social engineering, worm and virus
> risks that might or might not exist... Might as well stick a label
> on it that says "might contain nuts" just to be safe :-)
Heh. Okay, I agree that the first comment (doesn't zero out memory) is
good enough. Smart people can figure out the corollaries, if they
care. (And admittedly, most people won't care. :-)
-- Garrett
>
>
> Sherry Moore said:
> > I don't know the history behind the requirement stated above. I will
> > contact the Live Upgrade team to see if's OK to support -e for regular
> > reboot as well. If anybody knows the answer, feel free to chime in.
>
> lu uses init.d K* scripts to copy volatile files and perform the
> magic needed to switch things under the covers so that the system
> actually reboots elsewhere (eeprom boot-env changes, grub menu
> updates, whatever)
>
> If you bypass those scripts with commands like reboot, halt and
> uadmin, lu can't switch BEs for you.
>
> -John
>
>
