Developer's Guide
 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Macros Groups Pages
it may not contain all the symbols used by this software If you run into undefined symbol please let us know and we can provide you a build that will be compatible with your specific as well as not allowing the setting of crypto algorithm or length on the response This is now fixed Added some basic examples on how to use KSL in C Adding KMIP attribute support to parser and message generator This is just part of the KMIP additions In KMIP the way attributes are encoded are completely different from x protocol versions This update deals with the change mostly invisible from the application Also added new KMIP only attribute support Worked around a Linux linker bug that was not properly detecting dependencies and leaving out symbols as a result Added some basic examples on how to use KSL in C Adding KMIP support in the also supporting the Byte String extension Credential used by the Db2 KMIP client To finish off KMIP support Query Response JNI now supports the server returning an array of Validation Information Fixed an issue where the Cryptographic Parameters attribute always appeared to be in client requests of which it was defined as possible An additional field was added to the Crypto Params structure to indicate if the attribute was present or not The JNI was fixed not to create the corresponding Java object if the attribute was not present Message Extension fields are available to the user for Create KMIP operation The VendorExtension structure is just available in TTLV messages This will be added to all operations in the next release Application Specific Information attribute is not supported in the and the Offset field for ReKey and ReKeyPair is now set to if not provided by the client request message Crytographic and Cryptgraphic algorithm where not properly included in the Get response message for a wrapped key This has been fixed Issue with properly parsing KMIP XML and JSON message whenever an ISO8601 timestamp string was used Parse failed incorrectly Version Responses can now be that is do not list a set of protocol versions supported This is the proper response to a client Discover Versions request of an unsupported version To support general error responses an Error Response does not need to provided a valid KMIP operation Fixed an issue where single batch items always needed to have a Unique Batch Id This is not what the KMIP spec defines For requests with only a single batch item that batch item does not need a batch id and so its response will not have a batch id Fixed a bug where the type field for the attributes Alternative Name

Definition at line 35 of file readme.txt.