Main Page   Modules   Class Hierarchy   Compound List   File List   Compound Members   File Members   Related Pages  

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.

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.

Group crypto
Add an ability to 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.

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

Generated on Sat Jan 11 20:35:32 2003 for XML-Security-C by doxygen1.2.15