All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Si St" <sigbj-st@operamail.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Bug in cryptsetup?
Date: Sun, 20 Jun 2010 13:54:52 +0100	[thread overview]
Message-ID: <20100620125452.560634FCE0@c-in3ws--03-06.sv2.lotusliveops.com> (raw)

I could try some newer version of cryptsetup if they will install. You probably remember that we tried out som debugging with cryptsetup 1.1.1 on my SLED_10, the apitest. The conclusion was that that an SLED_10 used a different patch....:
(excerpt from MilanBroz' returnmail):
--BEGIN
"> 0 18968 crypt cbc(aes)-cbc-essiv:sha256 
> 00000000000000000000000000000000 0 7:5 1032
> cipher: cbc(aes)-cbc-essiv:sha256

Great! thanks. Seems SuSe have some non-standard patch applied here,"
--END

But this might not apply to your question(?)
I have taken care of all the emails concerning this matter:apitest

But I could also try out this on my new SLED_11_SP1. Havent checked into the cryptsetup there,yet.
Let me hear from you in case.

SS

/* OFFTOPIC; To Heinz Diehl:Thanks for your answer, Heinz Diehl!) */

SS-NORWAY
---------------------------------------------------------------------


> ----- Original Message -----
> From: Milan Broz <mbroz@redhat.com>
> To: Si St <sigbj-st@operamail.com>
> Cc: dm-crypt@saout.de
> Subject: Re: [dm-crypt] Bug in cryptsetup?
> Date: Sat, 19 Jun 2010 23:50:04 +0200
> 
> 
> On 06/19/2010 07:20 PM, Si St wrote:
> > --cryptsetup version 1.0.3 , OS = SLED_10_SP3--
> 
> Quite old version, it works for me in 1.1.2
> 
> > cryptsetup luksDelKey /dev/hda5 1
> >
> > I receive only that I succeeded, and the actual Key in Slot 1 is 
> > disabled testing it with luksDump.
> 
> # cryptsetup luksDelKey 0 /dev/sde
> luksDelKey is a deprecated action name.
> Please use luksKillSlot.
> Device 0 doesn't exist or access denied.
> 
> # cryptsetup luksDelKey /dev/sde 0
> luksDelKey is a deprecated action name.
> Please use luksKillSlot.
> 
> WARNING!
> ========
> This is the last keyslot. Device will become unusable after purging this key.
> ...
> 
> # cryptsetup luksKillSlot /dev/sde 1
> Key 1 not active. Can't wipe.
> 
> # cryptsetup --version
> cryptsetup 1.1.2
> 
> 
> Can you reproduce it with recent version?
> And I think we already found more problems with SLED10.
> 
> Milan

>


-- 
_______________________________________________
Surf the Web in a faster, safer and easier way:
Download Opera 9 at http://www.opera.com

             reply	other threads:[~2010-06-20 12:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-20 12:54 Si St [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-06-19 17:20 [dm-crypt] Bug in cryptsetup? Si St
2010-06-19 20:16 ` Heinz Diehl
2010-06-19 21:50 ` Milan Broz
2010-06-19 22:13   ` Arno Wagner
2010-06-19 22:26     ` Christoph Anton Mitterer
2010-06-20 19:54       ` Arno Wagner

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=20100620125452.560634FCE0@c-in3ws--03-06.sv2.lotusliveops.com \
    --to=sigbj-st@operamail.com \
    --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.