Hi, On Thu, Apr 16, 2020 at 10:41 PM tincanteksup <tincantek...@gmail.com> wrote: > > Missing the point completely. > > *Why* does openvpn expect a decimal value for something which is clearly > intended to be and is at source Hex.
What the the ideal format should be is arguable, but the "source" is not in hex. Serial number is an "INTEGER" with no more than 20 octets and may be, say, DER encoded in the certificate. Decimal, hex etc are just string representations used for display. With hex there are multiple formats out there, like upper case, lower case, optionally separated by space or :, with a leading 0x etc. "openssl x509 -serial ..." prints it as hex in upper case with no spaces, "openssl x509 -text .." has it in decimal with hex in parenthesis if the number is small (< 4 bytes?), otherwise as a lower case hex string with bytes separated by ":". And, there is no guarantee that these will not change in future. I'm not saying decimal string is better. The representation is unambiguous as a set of digits with no spaces and no leading zeros. But it may not be easy for an end user to get the decimal value. If we consider supporting hex, we'll first need to agree on the format. Selva _______________________________________________ Openvpn-users mailing list Openvpn-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-users
