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:
Customer is asking if we can upgrade the freeradius to version 2.1.12.
If not he is asking to backport the fix for "Fix %{string:...} expansion".
*** Version-Release number of selected component (if applicable):
freeradius-2.1.8-2
*** Actual results:
There is a bug in the RedHat's freeradius "Fix %{string:...} expansion".
*** Expected results:
Upgrade freeradius to 2.1.12 or include the fix for "Fix %{string:...} expansion" in the latest freeradius package.
*** Additional info
I checked the git sources of the latest available freeradius, but I can not find the part of the code which is fixing "Fix %{string:...} expansion" bug. I was also not able to find more information about it.
Maybe the right patch can be:
https://github.com/alandekok/freeradius-server/commit/6e68be18da1b32d8f536d10b3cb5b621dad8d28a
but I'm not sure...
Details are on the freeradius.org page, 2.1.12 version, search for: Fix %{string:...} expansion.
closing as a duplicate of bug #736878, rebase to 2.1.12
Since we're rebasing to 2.1.12 this should address the customers issue.
*** This bug has been marked as a duplicate of bug 736878 ***
*** Description of problem: Customer is asking if we can upgrade the freeradius to version 2.1.12. If not he is asking to backport the fix for "Fix %{string:...} expansion". *** Version-Release number of selected component (if applicable): freeradius-2.1.8-2 *** Actual results: There is a bug in the RedHat's freeradius "Fix %{string:...} expansion". *** Expected results: Upgrade freeradius to 2.1.12 or include the fix for "Fix %{string:...} expansion" in the latest freeradius package. *** Additional info I checked the git sources of the latest available freeradius, but I can not find the part of the code which is fixing "Fix %{string:...} expansion" bug. I was also not able to find more information about it. Maybe the right patch can be: https://github.com/alandekok/freeradius-server/commit/6e68be18da1b32d8f536d10b3cb5b621dad8d28a but I'm not sure... Details are on the freeradius.org page, 2.1.12 version, search for: Fix %{string:...} expansion.