Add 2 byte cipherID to JSON?

[mpd-dude]

While the json/server-side-tls-conf.json file is excellent for automated processing, it would be even more helpful to include the 2 byte cipherID for each ciphersuite.

Background: since there exist many different string representations (OpenSSL, IANA, ...) for the same ciphersuite, using the 2 byte cipherID would be the safest way for a match.

Would it be possible to add the cipherID in addition to the existing string representation in the JSON file? Thanks for considering.

[jvehent]

Yes, I think that would be a good idea. We'd need to do that in a backward compatible way, but we will have to rework the JSON format for TLS1.3 anyway, given the changes to the way ciphersuites are handled.

[april]

Just FYI, version 5.1 of the JSON guidelines will now include the IANA cipher string. I probably won't add support GnuTLS until some software comes along that requires it.

https://ssl-config.mozilla.org/server-side-tls/5.1.json