Well, I assume that the standard will become available in future. As part of my research I want to make it to run in parallel, for cbc mode only the decryption can be run in parallel, but for ctr both encryption and decryption. I am thinking to use a benchmarking tool like httperf, since it uses openssl library, then I should be able to customize the standard for both client and the server. Does this make sense to you?
Dr. Stephen Henson wrote: > > On Thu, Aug 04, 2011, wrote: > >> Hi, >> I want to make apache to use aes cipher for encryption in ctr mode (by >> default it is cbc mode). Cipher mode for aes is not specified in the >> cipher >> list. I know the mode is not being chosen in the "hello" process, but do >> you >> know when client and the server settle on the cipher mode they are about >> to >> use? If I know that I can hard code the settings to make apache use the >> ctr >> mode. > > Since no standards exist which use AES and CTR mode you can't actually do > this > without violating the standards ciphersuites or introducing a non-standard > experimental ciphersuite. > > So the question is why do you want to do that? > > Steve. > -- > Dr Stephen N. Henson. OpenSSL project core developer. > Commercial tech support now available see: http://www.openssl.org > ______________________________________________________________________ > OpenSSL Project http://www.openssl.org > Development Mailing List openssl-dev@openssl.org > Automated List Manager majord...@openssl.org > > -- View this message in context: http://old.nabble.com/SSL-cipher-mode-tp32201345p32206338.html Sent from the OpenSSL - Dev mailing list archive at Nabble.com. ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
