Hello all,

I've been working on getting AES-CCM available for negotiation over a TLS 
connection. I know that AES-CCM is available via the EVP interface, but I need 
it to be available as a TLS cipher suite so it can be negotiated with a client.

I started adding it as a new cipher suite, in a manner to how AES-GCM seems to 
be implemented, but I'm having trouble just getting it reported at an available 
cipher using the "openssl ciphers" command. I started thinking I was going down 
the wrong path, since CCM is already available via EVP.

Is my approach to add a new "AES128-CCM" cipher suite a reasonable one, or 
would it be better/quicker to just change the default mode of AES (and the 
related cipher suite ids) so that I can get a TLS-negotiated AES-CCM connection?

Regards,
Paul Muschick



Reply via email to