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:

After adding the additional CHAP digest modes for BZ 1761940, MD5 CHAP authentiction to a Synology DiskStation target was reported to no longer function.

This is actually an issue with the authentication negotiation of the kernel iSCSI target on the Synology, but may be present in other targets based on older Linux kernels.  They reject any initiator authentication that offers to use a CHAP mode other than MD5, even if MD5 is offered as well.

We should have a way of configuring the advertised CHAP modes, which would allow disabling anything other than MD5 in order to remain compatible with these targets.

Version-Release number of selected component (if applicable):

iscsi-initiator-utils-6.2.0.878-0.gitd791ce0.el8

Additional info:

I don't have a target that does this, instead I'm looking at the known issue of the older kernel target and checking that the on-the-wire behavior of the initiator can be configured back to what we did before.

It looks like it may be possible to reproduce this with RHEL 7.1 as the target.

Verified with iscsi-initiator-utils-6.2.0.878-3.gitd791ce0.el8. Regression testing passed.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2020:1829