Re: [GNU Crypto] EMSA-PKCS1-v1.5 and Diffie-Hellman key agreement

[Raif S. Naffah]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

hello Casey,

On Tue, 19 Aug 2003 12:26 am, Casey Marshall wrote:
> On Mon, Aug 18, 2003 at 07:16:37AM +1000, Raif S. Naffah wrote:
> > i finished implementing the above (EMSA-PKCS1-v1.5 as per rfc3447,
> > and Diffie-Hellman key agreement as per rfc-2631).
> >
> > i'd like to add at least one signature scheme (with appendix) for
> > use with DH keys; any preferences for such a scheme?
>
> Not sure what you mean. Pointer?

Diffie-Hellman, like RSA is just a key agreement that allows two parties 
to generate a shared key. EMSA-PSS and EMSA-PKCS1-v1.5 are signature 
schemes with appendix that use the RSA algorithm to generate and verify 
digital signatures.  which signature scheme do you need/prefer with 
Diffie-Hellman keys? or is just a DH algorithm for sharing a secret key 
enough for Jessie?


> Also, what do you think about contributing an EMSA-PKCS1-v1.5 based
> signature scheme to Classpath's provider? Without that RSA signature
> scheme (at least, I think that's the one; haven't looked at the docs
> in a while) X.509 certificates are limited to DSS signatures in
> vanilla Classpath. Which is bad.

sure why not.  Classpath is also welcome to use our implementations of 
SHA and MD5 which seem to be faster than their current ones.


cheers;
rsn
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Que du magnifique

iD8DBQE/QUOK+e1AKnsTRiERAwMvAJ9MITzPJlotmxrbfef14hRY/fM6rwCgytYG
CAnoz9L1vMDKzmqxRuuc6RY=
=OJv4
-----END PGP SIGNATURE-----