DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] [ANNOUNCE] cryptsetup 1.6.6
Date: Sat, 16 Aug 2014 13:25:04 +0200	[thread overview]
Message-ID: <20140816112504.GB29774@tansi.org> (raw)
In-Reply-To: <53EF373A.4020700@gmail.com>

On Sat, Aug 16, 2014 at 12:49:30 CEST, Milan Broz wrote:
> The stable cryptsetup 1.6.6 release is available at
[...]
> Cryptsetup API NOTE:
> The direct terminal handling for passphrase entry will be removed from
> libcryptsetup in next major version (application should handle it itself).
> 
> It means that you have to always either provide password in buffer or set
> your own password callback function through crypt_set_password_callback().
> See API documentation (or libcryptsetup.h) for more info.

I think this is an excellent idea. Direct terminal handling is
not the job of a disk-encryption library. The way it is done 
may also have quite a few details that are not readily obvious,
but can have security implications.

It may be a good idea to put the old way into the documentation
though and have some source-code fragment for it. If not too 
long, I could use that as the start of a libcryptsetup section 
in the FAQ or as the start of a libcryptsetup-specific FAQ.

Arno
-- 
Arno Wagner,     Dr. sc. techn., Dipl. Inform.,    Email: arno@wagner.name
GnuPG: ID: CB5D9718  FP: 12D6 C03B 1B30 33BB 13CF  B774 E35C 5FA1 CB5D 9718
----
A good decision is based on knowledge and not on numbers. -  Plato

      parent reply	other threads:[~2014-08-16 11:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-16 10:49 [dm-crypt] [ANNOUNCE] cryptsetup 1.6.6 Milan Broz
2014-08-16 10:59 ` .. ink ..
2014-08-16 11:56   ` Milan Broz
2014-08-16 11:25 ` Arno Wagner [this message]

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=20140816112504.GB29774@tansi.org \
    --to=arno@wagner.name \
    --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