Open bjmi opened 1 year ago
I have actually been thinking about this topic quite often in the past few weeks. The problem with hex strings is the multitude of possible formats:
09:65:2d:f2:73:e8:fb:bd:2c
9e 76 b4 db f9 42 e7 09
3234 3933 387A 3966 7361
0x
)0x01,0x02,0x03,0x04,0x05,0x06
And the format that you prefer is completely useless for me.
KSE is pretty inconsistent in this regard, it currently uses several of the listed formats. I want to unify the hex string representation and add configuration options for it.
It would be useful to have a quick way to get the hexadecimal serial number of a certificate. Therefore I copy the serial
0x9652DF273E8FBBD2CF17DD5A9D56719
from Certificate Details page, add colons, prepend a zero if necessary and lower case the final string manually to get the pretty formatted hexadecimal serial no.09:65:2d:f2:73:e8:fb:bd:2c:f1:7d:d5:a9:d5:67:19
.It would be great if the serial number field is already formatted. Or one could provide context menu entries Copy as is and Copy formatted.
Companies and public authorities expect the formatted variant in certificate related requests. E.g. OpenSSL prints Serial Number in that way too.