From: Milan Broz <mbroz@redhat.com>
To: dm-crypt <dm-crypt@saout.de>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: [dm-crypt] [ANNOUNCE] cryptsetup 1.1.2
Date: Sun, 30 May 2010 20:45:23 +0200 [thread overview]
Message-ID: <4C02B243.8070404@redhat.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The stable cryptsetup 1.1.2 release is available at
http://code.google.com/p/cryptsetup/
Feedback and bug reports are welcomed.
Milan
mbroz@redhat.com
== Cryptsetup 1.1.2 Release Notes ==
This release fixes a regression (introduced in 1.1.1 version) in handling
key files containing new line characters (affects only files read from
standard input).
Cryptsetup can accept passphrase on stdin (standard input).
Handling of new line (\n) character is defined by input specification:
* if keyfile is specified as "-" (using --key-file=- of by "-" positional argument
in luksFormat and luksAddKey, like cat file | cryptsetup --key-file=- <action>),
input is processed as normal binary file and no new line is interpreted.
* if there is no key file specification (with default input from stdin pipe
like echo passphrase | cryptsetup <action>) input is processed as input from terminal,
reading will stop after new line is detected.
Moreover, luksFormat now understands --key-file (in addition to positional key
file argument).
N.B. Using of standard input and pipes for passphrases should be avoided if possible,
cryptsetup have no control of used pipe buffers between commands in scripts and cannot
guarantee that all passphrase/key-file buffers are properly wiped after use.
=== changes since version 1.1.1 ===
* Fix luksFormat/luksOpen reading passphrase from stdin and "-" keyfile.
* Support --key-file/-d option for luksFormat.
* Fix description of --key-file and add --verbose and --debug options to man page.
* Add verbose log level and move unlocking message there.
* Remove device even if underlying device disappeared (remove, luksClose).
* Fix (deprecated) reload device command to accept new device argument.
For changes in previous version please see Cryptsetup 1.1.1 Release Notes
http://code.google.com/p/cryptsetup/wiki/Cryptsetup111
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAkwCskMACgkQf1Jlc7shgi8qoACeJ/kHiVoasT7XR/hpfu4I2seA
KKIAn362smF2PNQFyI8OjL1fn0hrdsZy
=hHU3
-----END PGP SIGNATURE-----
next reply other threads:[~2010-05-30 18:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-30 18:45 Milan Broz [this message]
2010-05-31 16:32 ` [dm-crypt] passing passphares via stdin/pipes Christoph Anton Mitterer
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=4C02B243.8070404@redhat.com \
--to=mbroz@redhat.com \
--cc=dm-crypt@saout.de \
--cc=dm-devel@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox