Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#50771 - enable these cipher suites also for {www,bugs,sources}.archlinux.org
Attached to Project:
Arch Linux
Opened by . (donotfuckingdisabletheaccount) - Wednesday, 14 September 2016, 07:13 GMT
Last edited by Florian Pritz (bluewind) - Sunday, 18 September 2016, 13:49 GMT
Opened by . (donotfuckingdisabletheaccount) - Wednesday, 14 September 2016, 07:13 GMT
Last edited by Florian Pritz (bluewind) - Sunday, 18 September 2016, 13:49 GMT
|
DetailsTLS v1.2 cipher suites
TLS_RSA_WITH_AES_128_GCM_SHA256 TLS_RSA_WITH_AES_256_GCM_SHA384 |
This task depends upon
Comment by Daniel M. Capella (polyzen) -
Wednesday, 14 September 2016, 12:53 GMT
You're going to have to give more details than that.
Comment by . (donotfuckingdisabletheaccount) -
Thursday, 15 September 2016, 00:14 GMT
the system administrator(s) must modify the configuration of the web servers to enable the usage of those TLS v1.2 cipher suites
Comment by Florian Pritz (bluewind) -
Sunday, 18 September 2016, 08:08 GMT
So why exactly should I add this cipher? I'm pretty sure it does not provide PFS since there is no DH handshake in there and AFAIK GCM only provides authentication.