public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Recovering root password
Date: Tue, 25 Mar 2008 14:44:34 +0000	[thread overview]
Message-ID: <20080325144434.5b596f3d@loonquawl.digimed.co.uk> (raw)
In-Reply-To: <68b1e2610803250508r3c3a834xa7efe1c3e0047984@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 827 bytes --]

On Tue, 25 Mar 2008 13:08:04 +0100, Liviu Andronic wrote:

> I'd say the BIOS is not much of a security enforcer. Even with the
> BIOS password protected, one can plug out the hardrive, connect to
> another system and get access to all the data. It might need more time
> than a LiveCD approach, it would be as efficient. As Alan and Wael
> suggested, the approaches that can work in protecting your data are a
> physical key to a locked door or a root encrypted system.

If it is possible to have sufficient access to be able to remove the hard
drive, then an encrypted filesystem is essential. Any computer that isn't
nailed down behind a locked door should have this, unless it contains and
has access to absolutely nothing of value.


-- 
Neil Bothwick

I'll try being nicer if you'll try being smarter.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-03-25 14:44 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-24 20:30 [gentoo-user] Recovering root password Grant
2008-03-24 20:34 ` Boris Fersing
2008-03-24 20:39 ` Dale
2008-03-24 20:49   ` Florian Philipp
2008-03-24 20:40 ` Ricardo Saffi Marques
2008-03-24 20:45   ` Steven Lembark
2008-03-24 20:49     ` Ricardo Saffi Marques
2008-03-25  7:12     ` Dirk Heinrichs
2008-03-24 21:57   ` Neil Bothwick
2008-03-24 23:52     ` Steven Lembark
2008-03-25  0:14   ` Grant
2008-03-24 20:42 ` Alan McKinnon
2008-03-25  5:41 ` Uwe Thiem
2008-03-25  8:03   ` Liviu Andronic
2008-03-25  8:09     ` Dirk Heinrichs
2008-03-25  8:25     ` Alan McKinnon
2008-03-25  8:32       ` Dirk Heinrichs
2008-03-25 15:28         ` Alan McKinnon
2008-03-25 16:32           ` Grant
2008-03-25 17:04             ` Uwe Thiem
2008-03-25 17:26               ` Grant
2008-03-25 21:28                 ` [gentoo-user] " Michael Schmarck
2008-03-26  8:07               ` [gentoo-user] " Dirk Heinrichs
2008-03-26 10:04                 ` Uwe Thiem
2008-03-25 17:14             ` Florian Philipp
2008-03-25 17:55             ` Steven Lembark
2008-03-25 19:12               ` Alan McKinnon
2008-03-25  9:12       ` Neil Bothwick
2008-03-25 12:08         ` Liviu Andronic
2008-03-25 14:44           ` Neil Bothwick [this message]
2008-03-25 17:53             ` Steven Lembark
2008-03-25 18:02               ` Dirk Heinrichs
2008-03-25 20:06                 ` Wael Nasreddine
2008-03-26  7:59                   ` Dirk Heinrichs
2008-03-25 19:23               ` Neil Bothwick
2008-03-25  8:30     ` Wael Nasreddine
2008-03-25 17:23       ` Mick
2008-03-25 20:02         ` Wael Nasreddine
2008-03-25 17:51     ` Steven Lembark

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080325144434.5b596f3d@loonquawl.digimed.co.uk \
    --to=neil@digimed.co.uk \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox