From: Milan Broz <mbroz@redhat.com>
To: Bryan Kadzban <cryptsetup@kdzbn.homelinux.net>
Cc: dm-crypt@saout.de,
Mario 'BitKoenig' Holbe <Mario.Holbe@TU-Ilmenau.DE>,
Jonas Meurer <jonas@freesources.org>
Subject: Re: [dm-crypt] [PATCH] Network passphrase reading
Date: Tue, 19 Jan 2010 10:44:01 +0100 [thread overview]
Message-ID: <4B557EE1.9070104@redhat.com> (raw)
In-Reply-To: <4B553032.2020707@kdzbn.homelinux.net>
On 01/19/2010 05:08 AM, Bryan Kadzban wrote:
>>> Would it be possible to drop askpass into the cryptsetup package here?
>>
>> IMHO, the best way would be to provide askpass as cryptsetup/contrib
>> content.
>
> Yeah, stuffing it into a contrib/ directory would work for me. What do
> the cryptsetup maintainers say? (If you aren't one of them, that is.)
If you mean upstream cryptsetup, I would be happy if we can commit these
Debian additional programs upstream and not patch distro later.
Just send patches to me or create new issue requesting it on project pages
http://code.google.com/p/cryptsetup/
Just a few notes:
- license must be compatible with GPL2
- I do not want anything working with network/sockets etc. in base cryptsetup
or libcryptsetup. No problem with specialized programs/wrappers.
- but please, if possible, use new libcryptsetup and not pipe passphrase
to cryptsetup binary, libcryptsetup should provide all needed callbacks now,
including optional locking of memory to avoid swapping some buffer with passphrase
(but maybe this is not possible because wrapper is used even for other
purposes)
Milan
next prev parent reply other threads:[~2010-01-19 9:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 3:36 [dm-crypt] [PATCH] Network passphrase reading Bryan Kadzban
2010-01-18 4:31 ` Dennis Furey
2010-01-18 5:14 ` Bryan Kadzban
2010-01-18 9:02 ` Mario 'BitKoenig' Holbe
2010-01-18 21:08 ` Bryan Kadzban
2010-01-19 0:39 ` Mario 'BitKoenig' Holbe
2010-01-19 4:08 ` Bryan Kadzban
2010-01-19 9:44 ` Milan Broz [this message]
2010-05-03 14:41 ` Jonas Meurer
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=4B557EE1.9070104@redhat.com \
--to=mbroz@redhat.com \
--cc=Mario.Holbe@TU-Ilmenau.DE \
--cc=cryptsetup@kdzbn.homelinux.net \
--cc=dm-crypt@saout.de \
--cc=jonas@freesources.org \
/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