<p dir="ltr"><br>
On Jan 2, 2014 11:12 AM, "Chris Murphy" <<a href="mailto:lists@colorremedies.com">lists@colorremedies.com</a>> wrote:<br>
><br>
><br>
> On Jan 2, 2014, at 9:32 AM, Steve Searle <<a href="mailto:steve@stevesearle.com">steve@stevesearle.com</a>> wrote:<br>
><br>
> > Around 12:43am on Tuesday, December 31, 2013 (UK time), Patrick O'Callaghan wrote:<br>
> ><br>
> >> Conclusion: better look for some other way to cover your tracks, and note<br>
> >> that a forensic investigation can be carried out without having you log in<br>
> >> at all.<br>
> ><br>
> > Just to emphasise what Patrick says, if you boot Linux into singe user<br>
> > mode, you can get root access without needing a password, which would<br>
> > bypass any setup you had done this way.<br>
><br>
> Not on Fedora 20 at least, and I think since even Fedora 19, if you use "single" boot param you startup to rescue.target. It asks for a root password or to press Control-D to continue. If I control-D to continue, startup proceeds to default.target. That's typically multi-user.target (runlevel 3), or graphical.target (runlevel 5).<br>
><br>
> I could boot from alternate media, and presumably mount and chroot this installation, and compel a change to the root password. But apparently not from the installation itself.<br>
><br>
> Chris Murphy<br>
> --<br>
> </p>
<p dir="ltr">The kernel still accepts "init=/bin/sh" . An encrypted volume definitely slows things down, but physical access gives a lot of freedom.</p>
<p dir="ltr">--Pete</p>