You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@santuario.apache.org by bu...@apache.org on 2009/06/30 17:17:31 UTC

DO NOT REPLY [Bug 42239] ECDSA signature value interoperability patch.

https://issues.apache.org/bugzilla/show_bug.cgi?id=42239


coheigea <co...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #20118|0                           |1
        is obsolete|                            |
             Status|NEEDINFO                    |NEW
         AssignedTo|security-dev@xml.apache.org |coheigea@apache.org




--- Comment #17 from coheigea <co...@apache.org>  2009-06-30 08:17:27 PST ---
Created an attachment (id=23914)
 --> (https://issues.apache.org/bugzilla/attachment.cgi?id=23914)
A patch (zip file) for this issue


See the attached patch which we can apply to close this issue. It's a reworked
version of the previous attachment "20118 - JUnit tests for ECDSA". Instead of
explicitly using BouncyCastle API's to create an ECDSA keypair each time the
test is run, I used the code to write the keypair out to a keystore, and then
commented the BouncyCastle code out.

The test tries to load the BouncyCastle provider via reflection, if it fails
then the tests just return without an error, as to run the tests we need to
have BouncyCastle installed to provide ECDSA support.

The patch is a zip file consisting of the actual patch, and the keystore which
should be placed in data\org\apache\xml\security\samples\input.

Note that this patch also needs attachment number "20117 - patch for making
ECDSA aware of varaible keylengths" that is attached to this issue but was
never applied.

Sean, can you take a look at the license at the top of the ResourceResolver
implementation in the patch to make sure it's ok?

Colm.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.