Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
When chrony upstream tests are executed via TC#520626 - /CoreOS/chrony/Sanity/upstream-testsuite [1] in FIPS mode then 'nts' test case fails (other tests pass) as follows:
Testing NTP authentication with NTS:
network with 1*1 servers and 1 clients:
non-default settings:
client_conf= nosystemcert ntstrustedcerts /dev/null ntstrustedcerts tmp/server1.crt ntstrustedcerts /dev/null logdir tmp log rawmeasurements
client_server_options=minpoll 6 maxpoll 6 nts
dns=1
max_sync_time=400
server_conf= ntsserverkey tmp/server1.key ntsservercert tmp/server1.crt ntsprocesses 0 ntsrotate 66 ntsdumpdir tmp
starting node 1: OK
starting node 2: OK
running simulation: OK
checking chronyd exit:
node 1: BAD
node 2: OK
FAIL
It only happens in FIPS mode.
[1] http://pkgs.devel.redhat.com/cgit/tests/chrony/tree/Sanity/upstream-testsuite
Version-Release number of selected component (if applicable):
chrony-4.1-1.el8
How reproducible:
* Always when FIPS mode is enabled
* Never when FIPS mode is disabled
Steps to Reproduce:
1. Enable FIPS mode (fips-mode-setup --enabled && reboot)
2. Install test dependecies (recommend section in main.fmf)
3. Run aforementioned test (bash runtest.sh).
Actual results:
nts fails
Expected results:
all tests pass
NTS uses AES-SIV-CMAC, which does not seem to be allowed by gnutls in FIPS mode. gnutls_aead_cipher_init() returns with an error (An algorithm that is not enabled was negotiated.).
I'm not sure if that is expected or not, but I don't think it's a chrony issue. Reassigning to gnutls.
Ondrej, would it be possible to check after adding:
tls-enabled-cipher = AES-128-SIV
tls-enabled-cipher = AES-256-SIV
in the crypto-policies configuration for GnuTLS in FIPS mode?
Oh, sorry; scratch that. I was confused and didn't realize this was a RHEL-8 issue, where we use priority string rather than the config format.
Let me look into it further.
Description of problem: When chrony upstream tests are executed via TC#520626 - /CoreOS/chrony/Sanity/upstream-testsuite [1] in FIPS mode then 'nts' test case fails (other tests pass) as follows: Testing NTP authentication with NTS: network with 1*1 servers and 1 clients: non-default settings: client_conf= nosystemcert ntstrustedcerts /dev/null ntstrustedcerts tmp/server1.crt ntstrustedcerts /dev/null logdir tmp log rawmeasurements client_server_options=minpoll 6 maxpoll 6 nts dns=1 max_sync_time=400 server_conf= ntsserverkey tmp/server1.key ntsservercert tmp/server1.crt ntsprocesses 0 ntsrotate 66 ntsdumpdir tmp starting node 1: OK starting node 2: OK running simulation: OK checking chronyd exit: node 1: BAD node 2: OK FAIL It only happens in FIPS mode. [1] http://pkgs.devel.redhat.com/cgit/tests/chrony/tree/Sanity/upstream-testsuite Version-Release number of selected component (if applicable): chrony-4.1-1.el8 How reproducible: * Always when FIPS mode is enabled * Never when FIPS mode is disabled Steps to Reproduce: 1. Enable FIPS mode (fips-mode-setup --enabled && reboot) 2. Install test dependecies (recommend section in main.fmf) 3. Run aforementioned test (bash runtest.sh). Actual results: nts fails Expected results: all tests pass