From: Jan Janssen <medhefgo@web.de>
To: dm-crypt@saout.de
Subject: [dm-crypt] Tcrypt hidden volume
Date: Mon, 01 Jul 2013 12:33:51 +0200 [thread overview]
Message-ID: <51D15B0F.6080201@web.de> (raw)
Hi,
while testing how the tcrypt passphrase + keyfile logic works, I
realized that there doesn't seem to be a way to protect the hidden
volume from being damaged by writes to a mounted outer volume like
truecrypt does. I think this deserves a warning in the man page
since this is a potential data loss.
Thanks,
Jan
next reply other threads:[~2013-07-01 10:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-01 10:33 Jan Janssen [this message]
2013-07-01 19:17 ` [dm-crypt] Tcrypt hidden volume Milan Broz
2013-07-02 1:05 ` Arno Wagner
2013-07-02 1:25 ` Arno Wagner
2013-07-02 5:29 ` Milan Broz
2013-07-02 9:45 ` Justin Tracey
2013-07-02 21: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=51D15B0F.6080201@web.de \
--to=medhefgo@web.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox