From: "David Härdeman" <david@2gen.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-kernel@vger.kernel.org, dhowells@redhat.com,
keyrings@linux-nfs.org
Subject: Re: [PATCH 00/04] Add DSA key type
Date: Fri, 27 Jan 2006 08:23:45 +0100 [thread overview]
Message-ID: <20060127072345.GB4082@hardeman.nu> (raw)
In-Reply-To: <E1F2IJr-0007Gu-00@gondolin.me.apana.org.au>
On Fri, Jan 27, 2006 at 12:22:31PM +1100, Herbert Xu wrote:
>David H?rdeman <david@2gen.com> wrote:
>>
>> 3) Changes the keyctl syscall to accept six arguments (is it valid to do so?)
>> and adds encryption as one of the supported ops for in-kernel keys.
>
>The asymmetric encryption support should be done inside the crypto/
>framework rather than as an extension to the key management system.
It is done inside the crypto/ framework. crypto/dsa.c implements the DSA
signing as a hash crypto algorithm (since a DSA signature is two 160-bit
integers, the result has a fixed size).
The above patch just adds the syscall to tell the in-kernel system that
you wish to encrypt/sign something with a given key. In the case that
the type of the given key is a DSA key, security/keys/dsa_key.c uses the
dsa crypto alg from crypto/dsa.c to satisfy that request.
Regards,
David
next prev parent reply other threads:[~2006-01-27 7:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060123173208.GA23964@2gen.com>
2006-01-23 20:42 ` [PATCH 00/04] Add DSA key type David Härdeman
2006-01-23 20:56 ` David Härdeman
2006-01-24 10:39 ` David Howells
2006-01-27 1:22 ` Herbert Xu
2006-01-27 7:23 ` David Härdeman [this message]
2006-01-27 12:28 ` Herbert Xu
2006-01-28 11:25 ` David Härdeman
2006-01-26 21:58 David Härdeman
2006-01-27 1:10 ` Herbert Xu
2006-01-27 7:18 ` David Härdeman
2006-01-27 20:11 ` David Howells
2006-01-27 23:22 ` 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=20060127072345.GB4082@hardeman.nu \
--to=david@2gen.com \
--cc=dhowells@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=keyrings@linux-nfs.org \
--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;
as well as URLs for NNTP newsgroup(s).