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:
freeradius shouldn't accept == operator in sql entries
Version-Release number of selected component (if applicable):
freeradius-2.1.12-4.el6_3
How reproducible:
always
Steps to Reproduce:
1.Setup mysql database, add tables for freeradius
2.Setup freeradius to use mysql
3.Add testuser to mysql database with == operator
'INSERT INTO radius.radcheck (UserName, Attribute, Op, Value) VALUES ('paptestuser', 'Cleartext-Password', '==', 'mypassword');'
4. Try to authenticate using radtest
radtest paptestuser mypassword localhost 0 testing123
Actual results:
rad_recv: Access-Accept packet
Expected results:
rad_recv: Access-Reject packet
Additional info:
I'm going to close this as WONTFIX because:
1) Changing the behaviour is not backwards compatible, we cannot break existing deployments with an update that changes fundamental behavior.
2) It would make our version of FreeRADIUS incompatible with the upstream version and versions of FreeRADIUS in other distributions (large institutions do run FR on different servers and they want to share configuration and databases between them)
3) FreeRADIUS 2.x is now legacy, it's been replaced by FreeRADIUS 3.x. FreeRADIUS 3.x tightens up the requirement for correct operator usage. This type of change is appropriate to occur only on a major version upgrade where other configuration also needs to be adjusted.
4) It's not actually causing any problems.
5) We could patch FreeRADIUS to emit a warning, but I see little point in spinning a new package and creating an errata just to emit a warning given the issues discussed above.
Description of problem: freeradius shouldn't accept == operator in sql entries Version-Release number of selected component (if applicable): freeradius-2.1.12-4.el6_3 How reproducible: always Steps to Reproduce: 1.Setup mysql database, add tables for freeradius 2.Setup freeradius to use mysql 3.Add testuser to mysql database with == operator 'INSERT INTO radius.radcheck (UserName, Attribute, Op, Value) VALUES ('paptestuser', 'Cleartext-Password', '==', 'mypassword');' 4. Try to authenticate using radtest radtest paptestuser mypassword localhost 0 testing123 Actual results: rad_recv: Access-Accept packet Expected results: rad_recv: Access-Reject packet Additional info: