# Is there an original source linking Qualys report codes to codes in nginx configuration? **URL:** \ **Category:** NGINX\ **Created:** [June 28, 2016, 5:23am UTC](https://www.ruby-forum.com/t/is-there-an-original-source-linking-qualys-report-codes-to-codes-in-nginx-configuration/244859 "2016-06-28T05:23:13Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Sadaf\_N](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/858c86/32.png) [@Sadaf\_N](https://www.ruby-forum.com/u/Sadaf_N)\ **Post date:** [June 28, 2016, 5:23am UTC](https://www.ruby-forum.com/t/is-there-an-original-source-linking-qualys-report-codes-to-codes-in-nginx-configuration/244859/1 "2016-06-28T05:23:13Z")
[http://security.stackexchange.com/questions/128513/is-there-an-original-informaton-source-linking-output-of-qualys-ssl-report-to-se#](http://security.stackexchange.com/questions/128513/is-there-an-original-informaton-source-linking-output-of-qualys-ssl-report-to-se#) The online tool at Qualys for testing webserver SSL configurations, [SSL Server Test (Powered by Qualys SSL Labs)](https://www.ssllabs.com/ssltest/index.html), produces a list of codes like TLS\_ECDHE\_RSA\_WITH\_AES\_256\_GCM\_SHA384, TLS\_RSA\_WITH\_CAMELLIA\_256\_CBC\_SHA etc. There are a lot of howtos on the net, but none of them show how to relate the actual string codes to those in the webservers. It is easy enough to use them but there is no knowning how they arrive at those settings in particular. Is there some kind of table relating the Qualys codes with the actual codes used in nginx configurations? – Frank C. ======================= [http://devblog.brahmancreations.com](http://devblog.brahmancreations.com) ---
**Author:** ![vfcforums](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/v/85e7bf/32.png) [@vfcforums](https://www.ruby-forum.com/u/vfcforums)\ **Post date:** [June 28, 2016, 5:30am UTC](https://www.ruby-forum.com/t/is-there-an-original-source-linking-qualys-report-codes-to-codes-in-nginx-configuration/244859/2 "2016-06-28T05:30:49Z")
The codes used in the nginx configuration are from openssl. There is a list to convert the names in the manual available here: [https://www.openssl.org/docs/manmaster/apps/ciphers.html](https://www.openssl.org/docs/manmaster/apps/ciphers.html) Am 28.06.2016 05:22 schrieb “vfclists .” [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid): ---
**Author:** ![vfcforums](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/v/85e7bf/32.png) [@vfcforums](https://www.ruby-forum.com/u/vfcforums)\ **Post date:** [June 28, 2016, 10:58am UTC](https://www.ruby-forum.com/t/is-there-an-original-source-linking-qualys-report-codes-to-codes-in-nginx-configuration/244859/3 "2016-06-28T10:58:31Z")
nginx deals with an underlying library to manage TLS-ciphered content. The webserver merely sends configuration data to it on startup/reload and uses this library to do the actual (en/de)ciphering job. The one officially supported is OpenSSL, for which cipher strings and cipher suites are listed in its ‘ciphers’ module manual (man ciphers - best - or [https://www.openssl.org/docs/manmaster/apps/ciphers.html](https://www.openssl.org/docs/manmaster/apps/ciphers.html) - worst). You should use then to feed the ssl\_ciphers [http://nginx.org/en/docs/http/ngx\_http\_ssl\_module.html#ssl\_ciphers](http://nginx.org/en/docs/http/ngx_http_ssl_module.html#ssl_ciphers) directive. What is accepted ultimately depends on the version of OpenSSL (or any other TLS library) your version of nginx is linked with. * * * _B. R._ ---
**Author:** ![vfcforums](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/v/85e7bf/32.png) [@vfcforums](https://www.ruby-forum.com/u/vfcforums)\ **Post date:** [June 28, 2016, 5:45pm UTC](https://www.ruby-forum.com/t/is-there-an-original-source-linking-qualys-report-codes-to-codes-in-nginx-configuration/244859/4 "2016-06-28T17:45:05Z")
There is a correspondence table on the Mozilla Server Side TLS wiki: > **[Client Challenge](https://wiki.mozilla.org/Security/Server_Side_TLS#Cipher_names_correspondence_table)** Regards, On Tue, Jun 28, 2016 at 6:22 AM vfclists . [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > use them but there is no knowning how they arrive at those settings in > [http://devblog.brahmancreations.com](http://devblog.brahmancreations.com) > > * * * > > nginx mailing list > [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) > [mailman.nginx.org archive](http://mailman.nginx.org/mailman/listinfo/nginx) – Alan Orth [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) > **[English Bulgaria | Life in the Balkans… in English!](https://englishbulgaria.net)** > **[Hujambo! | Living and Working in Nairobi, Kenya](https://alaninkenya.org)** > **[Mjanja Tech | Ujanja Ni Uhai (Hustling Is Life)](https://mjanja.ch)**