All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonas Diemer <diemer@gmx.de>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: security issue: hard disk lock
Date: Mon, 11 Apr 2005 18:01:16 +0200	[thread overview]
Message-ID: <200504111801.16647.diemer@gmx.de> (raw)
In-Reply-To: <1113233800.9875.47.camel@localhost.localdomain>

Hi Alan!

Thanks for the info

Am Montag 11. April 2005 17:36 schrieb Alan Cox:
> It makes little difference as the attacker can replace the kernel and
> reboot.
> Anyway they can flash erase your video card bios, your IDE firmware,
> your BIOS
> and far more just as easily.

Yes, but a new video-card or Motherboard can be easily bought (although it 
costs), but the data on a locked disk is lost forever, unless you pay for 
professional recovery (which is also a time-issue, if time critical data is 
stored on the disk). Of course, this can be solved with a good backup 
strategy...

I agree with you though, that this really isn't a kernel issue, but a BIOS 
thing. Distributors should/could provide additional security by freezing the 
security-features early during boot, until BIOS vendors do their homework.

regards,
Jonas

PS: Still not on the list, so please CC me in an eventual reply.

  reply	other threads:[~2005-04-11 16:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-04 17:42 security issue: hard disk lock Jonas Diemer
2005-04-04 18:32 ` Horst von Brand
2005-04-04 23:00   ` Chris Friesen
2005-04-05 15:41   ` Vernon Mauery
2005-04-05 17:10     ` Jonas Diemer
2005-04-04 19:26 ` Florian Weimer
2005-04-11 15:36 ` Alan Cox
2005-04-11 16:01   ` Jonas Diemer [this message]
2005-04-14  3:20     ` Mark Lord
2005-04-15 15:09     ` Alan Cox

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=200504111801.16647.diemer@gmx.de \
    --to=diemer@gmx.de \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.