All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <mbroz@redhat.com>
To: Rudolf Deilmann <rudolf.deilmann@gmail.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] [ANNOUNCE] cryptsetup 1.3.0-rc1	(test	release	candidate)
Date: Tue, 22 Mar 2011 22:05:06 +0100	[thread overview]
Message-ID: <4D890F02.6010803@redhat.com> (raw)
In-Reply-To: <20110322214404.2592589a@gmail.com>

On 03/22/2011 09:44 PM, Rudolf Deilmann wrote:
> On Tue, 22 Mar 2011 20:09:56 +0100
> Milan Broz <mbroz@redhat.com> wrote:
>> I wonder how I missed that. Ok, the we just allow --skip and if
>> it is not explicitly defined, it will behave as now.
> 
> Yes.
> However the current behaviour is that skip is implicitly set to
> the same value as offset.
> The default behaviour for plain-cryptsetup is that skip is set to
> zero, if only offset is specified.
> But I don't think this inconistency matters.

Exactly. That's why I implemented it is as different command.

(But from the libcryptsetup point of view it is just another format,
no new functions, just format specific options.)

> There are also
> inconsistencies in the interface between cryptsetup/plain and
> cryptsetup/luks (e.g. order of name and device )

In fact, I hate these inconsistencies but I cannot switch order
or parameters now. And providing new commadline interface
causes even more problems...

> 
>> So @offset => --skip 0 --offset $offset/512, right?
> 
> Yes.

Code is already in svn, there is one change in library object
(format specific option missed skip option) but we can do that still,
so final 1.3.0 version will have that included.

> Btw, I can't report any problems with other ciphers. Twofish and
> serpent seem to work well, too.

Great.

Thanks again for testing,
Milan

  reply	other threads:[~2011-03-22 21:05 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-14 17:44 [dm-crypt] [ANNOUNCE] cryptsetup 1.3.0-rc1 (test release candidate) Milan Broz
2011-03-14 21:13 ` Rudolf Deilmann
2011-03-14 22:10   ` Milan Broz
2011-03-14 23:45     ` Rudolf Deilmann
2011-03-15  1:02       ` Arno Wagner
2011-03-15 11:11         ` Milan Broz
2011-03-15 11:43           ` Jonas Meurer
2011-03-15 12:19             ` Milan Broz
2011-03-15 12:09           ` Arno Wagner
2011-03-15 12:36             ` Milan Broz
2011-03-15 13:49               ` Arno Wagner
2011-03-21 18:21   ` Milan Broz
2011-03-22 18:47     ` Rudolf Deilmann
2011-03-22 19:09       ` Milan Broz
2011-03-22 20:44         ` Rudolf Deilmann
2011-03-22 21:05           ` Milan Broz [this message]
2011-03-23 14:14             ` Rudolf Deilmann
2011-03-23 14:37               ` Milan Broz
2011-03-23 16:00                 ` Rudolf Deilmann
2011-03-23 16:26                   ` Milan Broz
2011-04-14 14:28                   ` [dm-crypt] [ANNOUNCE] cryptsetup 1.3.0-rc1 ( test " Ludwig Nussel
2011-03-17 13:36 ` [dm-crypt] [ANNOUNCE] cryptsetup 1.3.0-rc1 (test " Ludwig Nussel
2011-03-17 14:02   ` Milan Broz
2011-03-22 12:50 ` [dm-crypt] [ANNOUNCE] cryptsetup 1.3.0-rc2 " Milan Broz
2011-04-05 20:02 ` [dm-crypt] [ANNOUNCE] cryptsetup 1.3.0 Milan Broz
2011-04-05 20:02   ` Milan Broz
2011-05-24 15:48 ` [dm-crypt] [ANNOUNCE] cryptsetup 1.3.1 Milan Broz

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=4D890F02.6010803@redhat.com \
    --to=mbroz@redhat.com \
    --cc=dm-crypt@saout.de \
    --cc=rudolf.deilmann@gmail.com \
    /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.