2012 7:12 PM
To: openssl-users@openssl.org
Subject: Re: Making AES-CCM available as a TLS-negotiated cipher suite
Hi Paul,
On Wed, Apr 18, 2012 at 2:01 PM, Muschick, Paul wrote:
> So, it’s ironic that only after I post to the mailing list, I solve my
> first problem. For visitors from the
Hi Paul,
On Wed, Apr 18, 2012 at 2:01 PM, Muschick, Paul wrote:
> So, it’s ironic that only after I post to the mailing list, I solve my first
> problem. For visitors from the future, to fully add a new cipher suite, you
> can’t forget to add your cipher’s EVP_CIPHER* accessor function (generated
On Wed, Apr 18, 2012, Muschick, Paul wrote:
> So, it's ironic that only after I post to the mailing list, I solve my first
> problem. For visitors from the future, to fully add a new cipher suite, you
> can't forget to add your cipher's EVP_CIPHER* accessor function (generated by
> the BLOCK_CI
enSSL already supports?
Thanks in advance for any help.
Paul
From: owner-openssl-us...@openssl.org [mailto:owner-openssl-us...@openssl.org]
On Behalf Of Muschick, Paul
Sent: Tuesday, April 17, 2012 11:34 AM
To: openssl-users@openssl.org
Subject: Making AES-CCM available as a TLS-negotiated cip
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 man
