Biswatosh wrote: > my aim is to print CKA_IDs when we run certutil -K. > And also, I want certutuil to take CKA_ID as input to delete a key. > I want to do this way: > certutil -K should give some thing like this > 1a340caa2a1a54a1aa2b > 9c040baa1b1b94a1ca22 > 32a40faaafcac4a11a22 > ... > ... > > And, when I want to delete a key using it's CKA_ID, I give > certutil -(deleteoption) 9c040baa1b1b94a1ca22.
> I want the user to simply > copy-paste the hexa equivalent/(or any printable form like in decimal > or in octal of the CKA_ID and give that as input to certutil. > That's why I wrote two functions, and both of these functions use > SECItem and mpi data structures together. > So, when you say that I should put one in nss/cmd/lib, can it access > mpi functions from there? Or, is it that I should not attempt any such > function where both of these(mpi and SECItems are used)? IMO, the display and input of CKA_IDs doesn't need to support any radix other than 16. And no MPI functions are needed to convert a string of bytes into ASCII encoded hexadecimal, or vice versa. -- Nelson B _______________________________________________ dev-tech-crypto mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-crypto
