From: Kyle Moffett <mrmacman_g4@mac.com>
To: johnpol@2ka.mipt.ru
Cc: James Morris <jmorris@redhat.com>,
linux-kernel@vger.kernel.org, cryptoapi@lists.logix.cz,
David Miller <davem@davemloft.net>,
Herbert Xu <herbert@gondor.apana.org.au>,
Andrew Morton <akpm@osdl.org>,
Fruhwirth Clemens <clemens@endorphin.org>
Subject: Re: [0/many] Acrypto - asynchronous crypto layer for linux kernel 2.6
Date: Tue, 8 Mar 2005 09:46:30 -0500 [thread overview]
Message-ID: <DB5F652C-8FE0-11D9-A2CF-000393ACC76E@mac.com> (raw)
In-Reply-To: <20050308160747.2ffc842c@zanzibar.2ka.mipt.ru>
On Mar 08, 2005, at 08:07, Evgeniy Polyakov wrote:
> On Tue, 8 Mar 2005 07:22:01 -0500 Kyle Moffett <mrmacman_g4@mac.com>
> wrote:
>> I'm not exactly familiar with asynchronous block device, but I'm
>> guessing that it would need to get its crypto keys from the user
>> somehow, no? If so, then the best way of managing them is via
>> the key/keyring infrastructure. From the point of view of other
>> kernel systems, it's basically a set of BLOB<=>task associations
>> that supports a reasonable inheritance and permissions model.
>
> Above setup may be implemeted for the userspace/kernelspace
> application,
> which requires continuous access to the key material from the both
> sides,
> but asynchronous block device (and existing cryptoloop and dm-crypt)
> use
> different model, when controlling userspace application only one time
> provides required key material(using ioctl) and exits, but key material
> remains in kernelspace in device's private area.
The above application works perfectly with the design of the keyring
system. A process (An init-script or something) creates a "key" either
with a file or through some complex method that only user-space needs to
care about, then it calls the keyctl syscall to create an in-kernel key
with the data BLOB. The kernel module that registered the key-type (IE:
symmetric128 or something like that) verifies that the data is valid and
attaches it to a key data-structure.
Later, when you want to use the key for acrypto, cryptoloop, dm-crypt,
etc,
you would just pass the key-ID instead of a custom binary format, and
the
acrypto layer would just add a reference to the key in its own structure
and increment the refcount.
Cheers,
Kyle Moffett
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCM/CS/IT/U d- s++: a18 C++++>$ UB/L/X/*++++(+)>$ P+++(++++)>$
L++++(+++) E W++(+) N+++(++) o? K? w--- O? M++ V? PS+() PE+(-) Y+
PGP+++ t+(+++) 5 X R? tv-(--) b++++(++) DI+ D+ G e->++++$ h!*()>++$ r
!y?(-)
------END GEEK CODE BLOCK------
next prev parent reply other threads:[~2005-03-08 14:46 UTC|newest]
Thread overview: 84+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-07 20:37 Evgeniy Polyakov
2005-03-07 20:37 ` [??/many] list of files to be sent in a next couple of e-mails with small description Evgeniy Polyakov
2005-03-07 20:37 ` [??/many] acrypto benchmarks vs cryptoloop vs dm_crypt Evgeniy Polyakov
2005-03-07 20:37 ` [??/many] iok.c - simple example of the userspace acrypto usage [IOCTL] Evgeniy Polyakov
2005-03-07 20:37 ` [??/many] ucon_crypto.c - simple example of the userspace acrypto usage [DIRECT ACCESS] Evgeniy Polyakov
2005-03-07 20:37 ` [1/many] acrypto: Kconfig Evgeniy Polyakov
2005-03-07 20:37 ` [2/many] acrypto: Makefile Evgeniy Polyakov
2005-03-07 20:37 ` [3/many] acrypto: acrypto.h Evgeniy Polyakov
2005-03-07 20:37 ` [4/many] acrypto: async_provider.c Evgeniy Polyakov
2005-03-07 20:37 ` [5/many] acrypto: crypto_conn.c Evgeniy Polyakov
2005-03-07 20:37 ` [6/many] acrypto: crypto_conn.h Evgeniy Polyakov
2005-03-07 20:37 ` [7/many] acrypto: crypto_def.h Evgeniy Polyakov
2005-03-07 20:37 ` [8/many] acrypto: crypto_dev.c Evgeniy Polyakov
2005-03-07 20:37 ` [9/many] acrypto: crypto_lb.c Evgeniy Polyakov
2005-03-07 20:37 ` [10/many] acrypto: crypto_lb.h Evgeniy Polyakov
2005-03-07 20:37 ` [11/many] acrypto: crypto_main.c Evgeniy Polyakov
2005-03-07 20:37 ` [12/many] acrypto: crypto_route.h Evgeniy Polyakov
2005-03-07 20:37 ` [13/many] acrypto: crypto_stat.c Evgeniy Polyakov
2005-03-07 20:37 ` [14/many] acrypto: crypto_stat.h Evgeniy Polyakov
2005-03-07 20:37 ` [15/many] acrypto: crypto_user.c Evgeniy Polyakov
2005-03-07 20:37 ` [16/many] acrypto: crypto_user.h Evgeniy Polyakov
2005-03-07 20:37 ` [17/many] acrypto: crypto_user_direct.c Evgeniy Polyakov
2005-03-07 20:37 ` [18/many] acrypto: crypto_user_direct.h Evgeniy Polyakov
2005-03-07 20:37 ` [19/many] acrypto: crypto_user_ioctl.c Evgeniy Polyakov
2005-03-07 20:37 ` [20/many] acrypto: crypto_user_ioctl.h Evgeniy Polyakov
2005-03-07 20:37 ` [21/many] acrypto: simple_lb.c Evgeniy Polyakov
2005-03-07 20:37 ` [22/many] arch: alpha config Evgeniy Polyakov
2005-03-07 20:37 ` [23/many] arch: arm config Evgeniy Polyakov
2005-03-07 20:37 ` [24/many] arch: arm26 config Evgeniy Polyakov
2005-03-07 20:37 ` [25/many] arch: cris config Evgeniy Polyakov
2005-03-07 20:37 ` [26/many] arch: frv config Evgeniy Polyakov
2005-03-07 20:37 ` [27/many] arch: h8300 config Evgeniy Polyakov
2005-03-07 20:37 ` [28/many] arch: i386 config Evgeniy Polyakov
2005-03-07 20:37 ` [29/many] arch: ia64 config Evgeniy Polyakov
2005-03-07 20:37 ` [30/many] arch: m32r config Evgeniy Polyakov
2005-03-07 20:37 ` [31/many] arch: m68k config Evgeniy Polyakov
2005-03-07 20:37 ` [32/many] arch: m68knommu config Evgeniy Polyakov
2005-03-07 20:37 ` [33/many] arch: mips config Evgeniy Polyakov
2005-03-07 20:37 ` [34/many] arch: parisc config Evgeniy Polyakov
2005-03-07 20:37 ` [35/many] arch: ppc config Evgeniy Polyakov
2005-03-07 20:37 ` [36/many] arch: ppc64 config Evgeniy Polyakov
2005-03-07 20:37 ` [37/many] arch: s390 config Evgeniy Polyakov
2005-03-07 20:37 ` [38/many] arch: sh config Evgeniy Polyakov
2005-03-07 20:37 ` [39/many] arch: sh64 config Evgeniy Polyakov
2005-03-07 20:37 ` [40/many] arch: sparc config Evgeniy Polyakov
2005-03-07 20:37 ` [41/many] arch: sparc64 config Evgeniy Polyakov
2005-03-07 20:37 ` [42/many] arch: um config Evgeniy Polyakov
2005-03-07 20:37 ` [43/many] arch: v850 config Evgeniy Polyakov
2005-03-07 20:37 ` [44/many] arch: x86_64 config Evgeniy Polyakov
2005-03-07 20:37 ` [1/5] bd: Asynchronous block device Evgeniy Polyakov
2005-03-07 20:37 ` [2/5] bd: userspace utility to control asynchronous " Evgeniy Polyakov
2005-03-07 20:37 ` [4/5] bd: script for binding file and acrypto filters Evgeniy Polyakov
2005-03-07 20:37 ` [5/5] bd: script for unbinding any filters Evgeniy Polyakov
2005-03-08 15:16 ` [1/5] bd: Asynchronous block device Evgeniy Polyakov
2005-03-15 17:27 ` [16/many] acrypto: crypto_user.h Randy.Dunlap
2005-03-15 16:24 ` [11/many] acrypto: crypto_main.c Randy.Dunlap
2005-03-16 4:58 ` Evgeniy Polyakov
2005-03-08 18:02 ` [UPDATE PATCH 9/many] acrypto: crypto_lb.c Nishanth Aravamudan
2005-03-08 18:33 ` Evgeniy Polyakov
2005-03-10 19:18 ` [9/many] " Randy.Dunlap
2005-03-07 22:40 ` [8/many] acrypto: crypto_dev.c Nish Aravamudan
2005-03-07 23:14 ` Evgeniy Polyakov
2005-03-07 22:51 ` Nish Aravamudan
2005-03-07 23:27 ` Evgeniy Polyakov
2005-03-08 1:46 ` [UPDATE PATCH 8/many] " Nishanth Aravamudan
2005-03-08 9:40 ` Evgeniy Polyakov
2005-03-07 23:37 ` [8/many] " Randy.Dunlap
2005-03-08 0:05 ` Evgeniy Polyakov
2005-03-07 23:50 ` [3/many] acrypto: acrypto.h Randy.Dunlap
2005-03-08 0:34 ` Evgeniy Polyakov
2005-03-07 23:33 ` [1/many] acrypto: Kconfig Randy.Dunlap
2005-03-08 0:03 ` Evgeniy Polyakov
2005-03-07 21:13 ` [0/many] Acrypto - asynchronous crypto layer for linux kernel 2.6 Fruhwirth Clemens
2005-03-07 21:49 ` Evgeniy Polyakov
2005-03-08 13:24 ` Joshua Jackson
2005-03-10 10:27 ` Evgeniy Polyakov
2005-03-08 5:08 ` Kyle Moffett
2005-03-08 9:37 ` Evgeniy Polyakov
2005-03-08 12:22 ` Kyle Moffett
2005-03-08 13:07 ` Evgeniy Polyakov
2005-03-08 14:46 ` Kyle Moffett [this message]
2005-03-08 15:24 ` Evgeniy Polyakov
2005-03-10 12:42 ` Christophe Saout
2005-03-08 10:30 ` Herbert Xu
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=DB5F652C-8FE0-11D9-A2CF-000393ACC76E@mac.com \
--to=mrmacman_g4@mac.com \
--cc=akpm@osdl.org \
--cc=clemens@endorphin.org \
--cc=cryptoapi@lists.logix.cz \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=jmorris@redhat.com \
--cc=johnpol@2ka.mipt.ru \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®