Todo List

Member DSIGSignature::getKeyInfoList ()

The KeyInfo process is very primitive. An interface needs to be created to allow application developers to install an object into the Signature that the Signature can call on to translate KeyInfo lists into a Key.

Returns:

A pointer to the DSIGKeyInfoList object held by the DSIGSignature

Member XENCCipherReference::appendBase64Transform ()=0

Move to DSIGTransformList rather than re-implement in both DSIGReference and XENCCipherReference

Member XENCCipherReference::appendXPathTransform (const char *expr)=0

Move to DSIGTransformList rather than re-implement in both DSIGReference and XENCCipherReference

Member XENCCipherReference::appendXPathFilterTransform (void)=0

Move to DSIGTransformList rather than re-implement in both DSIGReference and XENCCipherReference

Member XENCCipherReference::appendXSLTransform (XERCES_CPP_NAMESPACE_QUALIFIER DOMNode *stylesheet)=0

Move to DSIGTransformList rather than re-implement in both DSIGReference and XENCCipherReference

Member XENCCipherReference::appendCanonicalizationTransform (canonicalizationMethod cm)=0

Move to DSIGTransformList rather than re-implement in both DSIGReference and XENCCipherReference

Class XSECCryptoHash

bring the interface here in-line with that provided for XSECCryptoBase64 - really should have only one way of calling these kinds of objects.

Member XSECProvider::releaseSignature (DSIGSignature *toRelease)

The DSIGSignature objects are fairly bulky in terms of creation and deletion. There should be a capability to store "released" objects in a re-use stack. At the moment the Provider class simply deletes the objects.

See also:

DSIGSignature::createBlankSignature

Class XSECURIResolverGenericUnix

Implement a "pluggable" URI resolver that allows developers to plug in different classes for different schemes

Class XSECURIResolverGenericWin32

Re-implement using the Windows Internet API

Member CRYPTO_MAX_HASH_SIZE

This should really come from each of the providers and should be implemented as a function call to *CryptoProvider

Group wincapicrypto

Need to allow the various classes to over-ride the PROV objects to allow specific private key instances rather than one instance across the library instance.

Group crypto

Add an ability to better handle "optional" functions. The library should make a call to the provider to see whether an optional function (e.g. extract key from X509) has been provided.

---