KMIP-interop-tech

The QuintessenceLabs KMIP server is now online. Previously issued credentials are still valid. If you need new credentials, please contact me. Server IP Address is 150.203.48.10 Server TCP Port is 5696 Supported Test Cases are: 3.1.1 - Create / Destroy 3.1.2 - Register / Create / Get attributes / Destroy 3.1.3 - Create / Locate / Get / Destroy 3.1.4 - Dual client use-case, ID Placeholder linked Locate & Get batch 3.1.5 - Register / Destroy Secret Data 4.1 - Revoke scenario 5.1 - Get usage allocation scenario 6.1 - Import of a Third-party Key 7.1 - Unrecognized Message Extension with Criticality Indicator false 7.2 - Unrecognized Message Extension with Criticality Indicator true 8.1 - Create a Key Pair 8.2 - Register Both Halves of a Key Pair 9.1 - Create a Key, Re-key 9.2 - Existing Key Expired, Re-key with Same lifecycle 9.3 - Existing Key Compromised, Re-key with same lifecycle 9.4 - Create key, Re-key with new lifecycle 9.5 - Obtain Lease for Expired Key 11.1 - Credential, Operation Policy, Destroy Date 12.1 - Query, Maximum Response Size 12.2 - Query Vendor Extensions 13.1 - Asymmetric Register PKCS#1 13.3 - Create, Re-key Key Pair 13.4 - Register Key Pair, Certify and Re-certify Public Key 15.1 - Locate a Fresh Object from the Default Group 15.2 - Client-side Group Management 15.3 - Default Object Group Member 16.1 - Discover Versions 17.1 - Handling of Attributes and Attributes Index Values 18.1 - Digests of Symmetric Keys 18.2 - Digests of RSA Private Keys Notes ----- Test case 11.1. Get Attributes does not work on a destroyed object. (See section 4.21 - meta-data MAY be retained, not SHOULD be maintained.) Credentials for Fred and Barney from the test-case document have been configured. If you plan to use some other username/password, let me know so that we can set up the user. Test case 15.1 assumes the creation of new objects on the fly in the default group. Our server doesn't do that. If you want to run 15.1, send create requests to ensure the default group contains fresh objects. Our server supplies the attribute index even when it is 0. This is consistent with the standard and not an error. We may add support for additional test cases during week 2. I will let you know if/when this happens. Let me know if you have any questions or issues. Regards, John ----------------------------------------------------------------------- John Leiseboer QuintessenceLabs Pty Ltd Chief Technology Officer Suite 23, Physics Building #38 Phone: +61 7 5494 9291 (Qld) Science Road Phone: +61 2 6125 9498 (ACT) Australian National University Mobile: +61 409 487 510 Acton ACT 0200 Fax: +61 2 6125 7180 AUSTRALIA Email: jl@quintessencelabs.com www.quintessencelabs.com -----------------------------------------------------------------------

> Supported Test Cases are: ... > 13.4 - Register Key Pair, Certify and Re-certify Public Key Test case 13.4 is not supported by the Qlabs server. It should not have been included in the list I sent out previously. John ----------------------------------------------------------------------- John Leiseboer QuintessenceLabs Pty Ltd Chief Technology Officer Suite 23, Physics Building #38 Phone: +61 7 5494 9291 (Qld) Science Road Phone: +61 2 6125 9498 (ACT) Australian National University Mobile: +61 409 487 510 Acton ACT 0200 Fax: +61 2 6125 7180 AUSTRALIA Email: jl@quintessencelabs.com www.quintessencelabs.com -----------------------------------------------------------------------

On 19/07/2012 7:52 PM, John Leiseboer wrote: > Test case 13.4 is not supported by the Qlabs server. It should not > have been included in the list I sent out previously. Updated spreadsheet noting 13.4 as unsupported for QLabs. Thanks, Tim. Attachment: KMIPInteropResults-Jul2012-MASTER_v1.0b_Blank.xls Description: MS-Excel spreadsheet

Qlabs preliminary test results spread sheet is attached. Results have not been fully reviewed, and may change. Some unexpected results have been observed with some servers. After reviewing these internally, I'll get back to individuals if necessary to resolve issues. The latest master spread sheet has some errors regarding QuintessenceLabs server supported use cases. Below is the current set of UNSUPPORTED use cases: 3.2 10.1 11.2 13.2 13.4 14.2 Regards, John ----------------------------------------------------------------------- John Leiseboer QuintessenceLabs Pty Ltd Chief Technology Officer Suite 23, Physics Building #38 Phone: +61 7 5494 9291 (Qld) Science Road Phone: +61 2 6125 9498 (ACT) Australian National University Mobile: +61 409 487 510 Acton ACT 0200 Fax: +61 2 6125 7180 AUSTRALIA Email: jl@quintessencelabs.com www.quintessencelabs.com ----------------------------------------------------------------------- Attachment: KMIPInteropResults-Jul2012_v1.0a_QLABS-1.xls Description: KMIPInteropResults-Jul2012_v1.0a_QLABS-1.xls

Updated spreadsheet confirmed by JohnL as matching current QLabs server and client feature set. Tim. Attachment: KMIPInteropResults-Jul2012-MASTER_v1.0c_Blank.xls Description: MS-Excel spreadsheet

Attached is our current test status. This does not reflect the updated QL server from today as yet - so those items marked as not working there are most likely all addressed according to John's email. I'm wait on some additional results to re-confirm the status for some of the testing. Note: the interop call will be on again this week as usual 30 mins before the main TC call. The focus will be on the status of the interop testing so far. Thanks, Tim. Attachment: KMIPInteropResults-Jul2012-Cryptsoft-v1.xls Description: MS-Excel spreadsheet

Reminder: the interop call will be on again this week as usual 30 mins before the main TC call - i.e. approximately 8.5 hours from now. The focus will be on the status of the interop testing so far. Thanks, Tim.

I've been travelling and haven't yet completed gathering the summary results together so no interop call this week (sorry about the late notice). We can continue the discussion on templates via the email list and I'll get the results for the next meeting. The main call is of course on as usual (at it's new time) as per Bob Griffin's email. Thanks, Tim.

We have enabled TLSv1.2 support on the Cryptsoft interop server and confirmed interoperability between the Cryptsoft and IBM implementations that support TLSv1.2 (client implementations interoperating with the other vendor server implementation). All of TLSv1.0, TLSv1.1 and TLSv1.2 are supported. If anyone else has a TLSv1.2 implementation that you are able to test please let the respective vendors (Cryptsoft, IBM) know. Thanks, Tim.