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.
Bug 2220877 - ipahealthcheck.ds.config displays CRITICAL message in STIG enviornment.
Summary: ipahealthcheck.ds.config displays CRITICAL message in STIG enviornment.
Keywords:
Status: CLOSED DUPLICATE of bug 2220890
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: 389-ds-base
Version: 8.9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: LDAP Maintainers
QA Contact: LDAP QA Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-06 11:59 UTC by Sudhir Menon
Modified: 2023-07-06 13:24 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-07-06 13:24:38 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-161680 0 None None None 2023-07-06 12:00:49 UTC

Description Sudhir Menon 2023-07-06 11:59:20 UTC
Description of problem: ipahealthcheck.ds.config displays CRITICAL message in STIG enviornment. 

Version-Release number of selected component (if applicable):
ipa-server-4.9.12-2.module+el8.9.0+18921+013c0de2.x86_64
389-ds-base-1.4.3.36-1.module+el8.9.0+19111+92b42fe2.x86_64
How reproducible:
Always

Steps to Reproduce:
1. Install IPA on STIG env.
2. ipa-healthcheck', '--output-type', 'json', '--failures-only'

Actual results:
RUN ['ipa-healthcheck', '--output-type', 'json', '--failures-only']
[
  {
    "source": "ipahealthcheck.ds.config",
    "check": "ConfigCheck",
    "result": "CRITICAL",
    "uuid": "29681a74-6e3c-47ef-84bd-2129992ae74f",
    "when": "20230704084231Z",
    "duration": "0.053042",
    "kw": {
      "key": "DSCLE0002",
      "items": [
        "cn=config"
      ],  
      "msg": "Password storage schemes in Directory Server define how passwords are hashed via a\none-way mathematical function for storage. Knowing the hash it is difficult to gain\nthe input, but knowing the input you can easily compare the hash.\n\nMany hashes are well known for cryptograhpic verification properties, but are\ndesigned to be *fast* to validate. This is the opposite of what we desire for password\nstorage. In the unlikely event of a disclosure, you want hashes to be *difficult* to\nverify, as this adds a cost of work to an attacker.\n\nIn Directory Server, we offer one hash suitable for this (PBKDF2-SHA512) and one hash\nfor \"legacy\" support (SSHA512).\n\nYour configuration does not use these for password storage or the root password storage\nscheme.\n" 
    }   
  }
]
DEBUG    Exit code: 1
      
Expected results:
Fix the critical message

Additional info:

Comment 1 Sudhir Menon 2023-07-06 12:25:33 UTC
Jul  6 07:45:20 master systemd[1]: Starting 389 Directory Server TESTRELM-TEST....
Jul  6 07:45:20 master ns-slapd[16077]: [06/Jul/2023:07:45:20.567905482 -0400] - INFO - slapd_system_isFIPS - system in FIPS mode
Jul  6 07:45:20 master ns-slapd[16077]: [06/Jul/2023:07:45:20.589608014 -0400] - INFO - slapd_system_isFIPS - system in FIPS mode
Jul  6 07:45:20 master ns-slapd[16077]: [06/Jul/2023:07:45:20.705685860 -0400] - INFO - slapd_system_isFIPS - system in FIPS mode
Jul  6 07:45:20 master ns-slapd[16077]: [06/Jul/2023:07:45:20.709367733 -0400] - WARN - slapd_do_all_nss_ssl_init - ERROR: TLS is not enabled, and the machine is in FIPS mode. Some functionality won't work correctly (for example, users with PBKDF2_SHA256 password scheme won't be able to log in). It's highly advisable to enable TLS on this instance.

Comment 2 mreynolds 2023-07-06 13:24:38 UTC
Closing as a duplicate of: https://bugzilla.redhat.com/show_bug.cgi?id=2220890

*** This bug has been marked as a duplicate of bug 2220890 ***


Note You need to log in before you can comment on or make changes to this bug.