#3027 Unsupported RSA_ ciphers should be removed from the default ciphers list
Closed: fixed 5 years ago Opened 5 years ago by mharmsen.

When Dogtag server is running in FIPS mode with a HSM, the TLS negotiation with RSA_ ciphers is
failing with an error BAD_RECORD_MAC. Dogtag team decided to document those RSA_ ciphers as unsupported. The unsupported RSA_ ciphers should be removed from the default ciphers list.

Steps to Reproduce:

The TLS negotiation when contacting the Dogtag server is failing with an error 
“BAD_RECORD_MAC” for the following RSA_ ciphers.

* TLS_RSA_WITH_AES_128_CBC_SHA
* TLS_RSA_WITH_AES_256_CBC_SHA
* TLS_RSA_WITH_AES_128_CBC_SHA256
* TLS_RSA_WITH_AES_256_CBC_SHA256

After the investigation of the issue, the team decision is:
"We can basically say we don't support  RSA_ algorithms in FIPS mode with a HSM.
   - This may be fine because the RSA_ algorithms are deprecated in TLS 1.3 anyway
     (and currently not preferred in TLS 1.2)."

The above 4 ciphers should be removed from default supported sslRangeCiphers
in server.xml.

Metadata Update from @mharmsen:
- Custom field component adjusted to None
- Custom field feature adjusted to None
- Custom field origin adjusted to None
- Custom field proposedmilestone adjusted to None
- Custom field proposedpriority adjusted to None
- Custom field reviewer adjusted to None
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1578389
- Custom field type adjusted to None
- Custom field version adjusted to None

5 years ago

Reminder to add clarification in ciphers.info on why installation of EC CS system needs RSA ciphers.

Here is edewata's explanation for reference (which could be sorted out and put in ciphers.info):

During PKI server installation, pkispawn generates a temporary SSL server
certificate so pkispawn can call the configuration servlet via SSL (to generate
the permanent certs). The temp cert is created here:

https://github.com/dogtagpki/pki/blob/master/base/server/python/pki/server/deployment/scriptlets/configuration.py#L796

As shown in the code above, there are some pkispawn params that you can configure.

The DS is on the server side, but the cipher settings in server.xml will
affect the whole JVM, so it probably would affect how PKI server connects
to the DS too.

Metadata Update from @cfu:
- Issue assigned to cfu (was: mharmsen)

5 years ago

commit 8cbf8f743796aa2e958c52890de693b714730ddb (HEAD -> master, origin/master, origin/HEAD, ladycfu/ticket-3028-disable-TLS_RSA-ciphers-master, ticket-3028-disable-TLS_RSA-ciphers-master, ticket-3028-disable-TLS_RSA-ciphers)
Author: Christina Fu cfu@redhat.com
Date: Fri Aug 31 17:08:30 2018 -0700

Ticket3027 Disable TLS_RSA_* ciphers for HSM in FIPS mode

This patch disables the TLS_RSA_* ciphers by default because they do not work
with HSMs in FIPS mode.
ciphers.info is also updated to reflect the changes.

fixes https://pagure.io/dogtagpki/issue/3027

Change-Id: Id720b8697976bb344d6dd8e4471a1bb5403af172

Metadata Update from @cfu:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

5 years ago

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.6 (was: 10.5)

5 years ago

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.5.13 (was: 10.6)

5 years ago

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/3145

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Login to comment on this ticket.

Metadata