From: "Boyd Stephen Smith Jr." <bss03@volumehost.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] LUKS
Date: Mon, 9 Jan 2006 11:39:00 -0600 [thread overview]
Message-ID: <200601091139.00695.bss03@volumehost.com> (raw)
In-Reply-To: <7babdf270601090857w75cd06d6o88a0fee6e8e30c49@mail.gmail.com>
On Monday 09 January 2006 10:57, Cláudio Henrique
<rapaduraatomica@gmail.com> wrote about '[gentoo-user] LUKS':
> has anybody here used LUKS?
I haven't, but when I next create an encrypted pv/lv, I will be.
> If I used on any of my HDs, will I be able to update them?
What do you mean by update? LUKS does allow you to change the key.
> What if the
> data of some file gets corrupted, will I loose the whole HD?
Depends on how the corruption occurs. There are a least to ways for this
to happen:
1) Hardware. For one reason or another, a bit gets swapped on the HD. In
this case what you lose will depend on your cypher, key size, and key
schedule. It may be as small as 8 bytes on disk or as large as a full 512
byte sector. Of course, if this happens in the fs superblock (or other
critial area, like the LUKS header) this could be enough to render the
disk inaccessible, but even a single bit being swapped in the superblock
can do that.
2) Software. In particular misbehaving software that accesses the HD via
LUKS. In this case the read data will be exactly what is written; LUKS
can't magically fix errors, but it's not going (supposed) to introduce
them either.
--
Boyd Stephen Smith Jr.
bss03@volumehost.com
ICQ: 514984 YM/AIM: DaTwinkDaddy
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-01-09 17:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 16:57 [gentoo-user] LUKS Cláudio Henrique
2006-01-09 17:26 ` Richard Fish
2006-01-10 13:13 ` Cláudio Henrique
2006-01-10 13:31 ` Boyd Stephen Smith Jr.
2006-01-10 13:42 ` Dirk Heinrichs
2006-01-10 16:20 ` Richard Fish
2006-01-10 13:36 ` Dirk Heinrichs
2006-01-09 17:39 ` Boyd Stephen Smith Jr. [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-23 9:46 Jorge Almeida
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=200601091139.00695.bss03@volumehost.com \
--to=bss03@volumehost.com \
--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