All of lore.kernel.org
 help / color / mirror / Atom feed
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: Sat, 28 Jan 2006 12:25:13 +0100	[thread overview]
Message-ID: <20060128112512.GB4348@hardeman.nu> (raw)
In-Reply-To: <20060127122856.GB32128@gondor.apana.org.au>

On Fri, Jan 27, 2006 at 11:28:56PM +1100, Herbert Xu wrote:
>On Fri, Jan 27, 2006 at 08:23:45AM +0100, David H?rdeman wrote:
>>On Fri, Jan 27, 2006 at 12:22:31PM +1100, Herbert Xu wrote:
>>>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).
>
>Right.  I mistook the name encrypt to mean generic asymmetric encryption.
>Now I see that it is simply an interface to the signature algorithm.
>This is fine by me.  However, wouldn't "sign" be a better name for it?
>

I don't know, the function which is performed upon the data is 
keytype-specific (i.e. with the dsa key the data is signed, with another 
key type it might be encrypted, etc). So perhaps the operation should be 
given a more generic name such as "crypto".

Re,
David

  reply	other threads:[~2006-01-28 11:25 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
2006-01-27 12:28       ` Herbert Xu
2006-01-28 11:25         ` David Härdeman [this message]
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=20060128112512.GB4348@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.