Forum Discussion
Travis_Collavo_
Jan 19, 2010Historic F5 Account
Cipher Strings
Hello,
I'm looking to see how LTM orders ciphers if you use the @SPEED option in your cipher string. If I use the openssl command to sort on @STRENGTH then I get a list that is as follows:
openssl ciphers 'ALL:@STRENGTH'
ADH-AES256-SHA:DHE-RSA-AES256-SHA:DHE-DSS-AES256-SHA:AES256-SHA:EDH-RSA-DES-CBC3-SHA:EDH-DSS-DES-CBC3-SHA:DES-CBC3-SHA:ADH-DES-CBC3-SHA:DES-CBC3-MD5:ADH-AES128-SHA:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA:AES128-SHA:RC4-SHA:RC4-MD5:ADH-RC4-MD5:RC2-CBC-MD5:RC4-MD5:EDH-RSA-DES-CBC-SHA:EDH-DSS-DES-CBC-SHA:DES-CBC-SHA:ADH-DES-CBC-SHA:DES-CBC-MD5:EXP-EDH-RSA-DES-CBC-SHA:EXP-EDH-DSS-DES-CBC-SHA:EXP-DES-CBC-SHA:EXP-RC2-CBC-MD5:EXP-RC4-MD5:EXP-ADH-DES-CBC-SHA:EXP-ADH-RC4-MD5:EXP-RC2-CBC-MD5:EXP-RC4-MD5
The @SPEED option produces an error, although this option is mentioned in the LTM config guide.
Does anyone know what the ciphers presented by LTM will be if you use the 'ALL:@SPEED' option in a clientSSL profile?
Thanks in advance,
Travis
- Travis_Collavo_Historic F5 AccountOK I think I derived the answer based on a TMM command:
- Travis_Collavo_Historic F5 AccountThanks Aaron.
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects