All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Using plain64/plain IV (initialisation vector) in	dm-crypt
Date: Tue, 27 Jul 2010 18:08:10 +0200	[thread overview]
Message-ID: <20100727160810.GA7331@tansi.org> (raw)
In-Reply-To: <1280240232.11350.13.camel@etppc09.garching.physik.uni-muenchen.de>

On Tue, Jul 27, 2010 at 04:17:12PM +0200, Christoph Anton Mitterer wrote:
> On Tue, 2010-07-27 at 12:47 +0200, Arno Wagner wrote: 
> > Yes. My FAQ recomendation is to make a backup, create a new
> > container in the target size and then restore the data. I 
> > think resizing the filesystem is just too risky otherwise.
> Why exactly do you mean? Any other pitfalls than that a user continues
> to use plain instead of plain64?
> I thought everything else in the LUKS header would be independent of the
> amount of storage after it.

Yes, but you need to 

  a) resize the raw container (partition, file, disk)
  b) reboot to make the kernel see the changed size
  c) decrypt the container 
  d) wipe the additional space from the decrypted side
  e) resize the filesystem in the container

d) is optional but highly recommended. 

If you get anything wrong here, the risk of wiping your 
LUKS header (with complete data loss) or damaging the filesystem
for dm-crypt (with at least partial data loss) are high enough to
justify doing a backup. Also, power loss or a system crash during
the filesystem resizing can also result in arbitrary bad data loss.

But if you have a backup, recreating the filesystem in the new
size is the easiest option. You do not strictly need to recreate 
the LUKS header, but if you are prepared to do it, you are not 
screwed if it turns out that it suffered damage. 

So, yes, you can do this without backup and just keeping the
original LUKS header. But I will continue to recomend a full
data backup and recreating the container after resizing it. 
If you are proficient enough to not need that, be my guest,
but if you mess up and lose all your data, I will be entitled
to make fun of you ;-)

Arno 
-- 
Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno@wagner.name 
GnuPG:  ID: 1E25338F  FP: 0C30 5782 9D93 F785 E79C  0296 797F 6B50 1E25 338F
----
Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans

If it's in the news, don't worry about it.  The very definition of 
"news" is "something that hardly ever happens." -- Bruce Schneier 

  reply	other threads:[~2010-07-27 16:08 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-22 14:57 [dm-crypt] Efficacy of xts over 1TB David Santamaría Rogado
2010-07-25 10:34 ` Arno Wagner
2010-07-25 11:18   ` Christoph Anton Mitterer
2010-07-25 12:29     ` Heinz Diehl
2010-07-25 12:25   ` Milan Broz
2010-07-25 13:14     ` Christoph Anton Mitterer
2010-07-25 13:52       ` Milan Broz
2010-07-25 22:37         ` Christoph Anton Mitterer
2010-07-26  0:14           ` Milan Broz
2010-07-26 20:38             ` Christoph Anton Mitterer
2010-07-27  8:46               ` [dm-crypt] Using plain64/plain IV (initialisation vector) in dm-crypt Milan Broz
2010-07-27 10:47                 ` Arno Wagner
2010-07-27 14:17                   ` Christoph Anton Mitterer
2010-07-27 16:08                     ` Arno Wagner [this message]
2010-07-27 14:15                 ` Christoph Anton Mitterer
2010-07-27 15:45                   ` Mario 'BitKoenig' Holbe
2010-07-27 15:55                     ` Milan Broz
2010-07-27 18:59                       ` Christoph Anton Mitterer
2010-07-27 19:37                         ` Arno Wagner
2010-07-27 18:58                     ` Christoph Anton Mitterer
2010-07-27 19:35                       ` Mario 'BitKoenig' Holbe
2010-07-28  8:42                     ` Milan Broz
2010-08-20 21:11                       ` [dm-crypt] XTS cipher mode limitations Christoph Anton Mitterer
2010-08-21  0:22                         ` Arno Wagner
2010-08-22 12:50                           ` [dm-crypt] XTS cipher mode limitations (FAQ additions) Christoph Anton Mitterer
2010-08-23  0:46                             ` Arno Wagner
2010-08-25  9:36                               ` Christoph Anton Mitterer
2010-08-22 12:56                           ` [dm-crypt] tool to account the written number of bytes to a block device (was: XTS cipher mode limitations) Christoph Anton Mitterer
2010-08-22 16:01                             ` Arno Wagner
2010-08-22 21:57                               ` Christoph Anton Mitterer
2010-08-23  7:14                                 ` [dm-crypt] tool to account the written number of bytes to a block device Milan Broz
2010-08-25  9:27                                   ` Christoph Anton Mitterer
2010-08-24 16:19                           ` [dm-crypt] XTS cipher mode limitations Ramius
2010-07-26  8:53           ` [dm-crypt] Efficacy of xts over 1TB Arno Wagner
2010-07-26 20:47             ` Christoph Anton Mitterer
2010-07-26 21:01               ` Arno Wagner
2010-07-26 21:28                 ` Christoph Anton Mitterer
2010-07-26 21:35                   ` Arno Wagner
2010-07-25 22:52         ` Christoph Anton Mitterer
2010-07-26  9:42           ` Mario 'BitKoenig' Holbe
2010-07-26 18:09             ` Arno Wagner
2010-07-27 18:16               ` [dm-crypt] Including the FAQ in the tarball? Christoph Anton Mitterer
2010-07-27 18:23                 ` Arno Wagner
2010-07-29  8:17                 ` Heinz Diehl
2010-07-25 15:32       ` [dm-crypt] Efficacy of xts over 1TB Arno Wagner
2010-07-25 22:48         ` Christoph Anton Mitterer
2010-07-25 23:42           ` Milan Broz
2010-07-26 18:35             ` Christoph Anton Mitterer
2010-07-25 15:28     ` Arno Wagner
2010-07-25 18:11       ` Milan Broz
2010-07-26  9:04   ` Mario 'BitKoenig' Holbe
2010-07-27 18:21     ` Christoph Anton Mitterer
2010-07-27 21:02       ` Mario 'BitKoenig' Holbe
2010-07-26  9:17 ` Mario 'BitKoenig' Holbe
2010-07-27 18:42 ` David Santamaría Rogado

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=20100727160810.GA7331@tansi.org \
    --to=arno@wagner.name \
    --cc=dm-crypt@saout.de \
    /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.