All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Javier Juan Martínez Cabezón" <tazok.id0@gmail.com>
To: dm-crypt@saout.de
Subject: [dm-crypt] exclusive flag trouble
Date: Sun, 11 Mar 2012 11:27:22 +0100	[thread overview]
Message-ID: <4F5C7E0A.6060908@gmail.com> (raw)



Hi until now I used a tool to make hidden partitions called scubed (is
something like a partition tool that used cryptsetup to create the
needed volumes (really old but worked fine)

http://cube.dyndns.org/cgi-bin/viewvc.cgi/trunk/scubed.c?diff_format=l&sortdir=down&logsort=rev&sortby=log&view=markup&root=scubed

- I get realized from this:

http://code.google.com/p/cryptsetup/issues/detail?id=105

With scubed you create five cryptsetup levels in the same device and
with all unlocked you assign needed blocks to each of them with scubed)

I haven't get troubles with this is able for example to create read only
media (dvd+-r) with multiple ciphered layers.

Here is the readme (with a mini tutorial):
http://cube.dyndns.org/svn/scubed/trunk/README

I think this will not be compatible with --shared flag. If this is
correct is there any possibility to make non-exclusive flag available if
cryptsetup will not control resizing partitions if not an underlaying
tool? (as
this one does that use dm-linear I think?)

If not at least can be enabled the non-exclusive flags to read only media?

Thanks for your time.

             reply	other threads:[~2012-03-11 10:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-11 10:27 Javier Juan Martínez Cabezón [this message]
2012-03-12 22:54 ` [dm-crypt] exclusive flag trouble 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=4F5C7E0A.6060908@gmail.com \
    --to=tazok.id0@gmail.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.