SV: [Opendnssec-develop] *blush* The experts agree. CKA_ID it is.

[Rickard Bondesson]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

> as I understand the implementations, the hex representation 
> shown in tools like pkcs11-tool (from OpenSC) is the hex 
> representation of the byte values.
> 
> so, 2EFAD382-4F44-475E-97CE-1CE3EB9283FE would be stored as a 16-byte
> array:
> { 2E FA D3 82 4F 44 47 5E 97 CE 1C E3 EB 92 83 FE }

If I store the same value in both CKA_LABEL and CKA_ID with pkcs11-tool, lets say 090310084749289287

Then pkcs11-tool will present this:

  label:      090310084749289287
  ID:         303930333130303834373439323839323837

They are represented by the same bytes in the token, but presented diffrently.

// Rickard
-----BEGIN PGP SIGNATURE-----
Version: 9.8.3 (Build 4028)
Charset: utf-8

wsBVAwUBScM/keCjgaNTdVjaAQgvtwf+LqUbKIEvVTz/S7wYTBRXsh0eHmpFH9wF
+Wp53/HHK6yiV2/536nj+AIdqmEu1MWrP2yn70WFT9Twr85QO+d6Y2uL/mST5lw1
DjgQpZgS0T4+I6oV8O3PknOS4JAd9pIhzwNlUGYZT6p5QzNZZeVKRUXXmE8uuW3K
BY63QP2cz9q+MHjIRoENxKNBWpHSc9+DmfUdYo4RL+TfOwRTRK2LCAx1rBfDdcAp
NLWsHyx325FAJ5aF789eGNEobVnWiRWEL2mdglg72uHjcrfoUANL1oC7sza47+o9
xuoHzxhu+1GJL3QiDC1wTv/rWHHYK9P4cNd9wKMvE0gRwVFRT1rDeg==
=dIaF
-----END PGP SIGNATURE-----