Bug 787624 - Freeradius 2.1.12 or backporting the fix for "Fix %{string:...} expansion"
Summary: Freeradius 2.1.12 or backporting the fix for "Fix %{string:...} expansion"
Keywords:
Status: CLOSED DUPLICATE of bug 736878
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: freeradius
Version: 6.2
Hardware: x86_64
OS: All
medium
medium
Target Milestone: rc
: ---
Assignee: John Dennis
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On: 736878
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-06 11:04 UTC by Petr Ruzicka
Modified: 2018-11-28 21:14 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-28 20:30:16 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Petr Ruzicka 2012-02-06 11:04:45 UTC
*** 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.

Comment 2 John Dennis 2012-02-06 13:01:51 UTC
marking this as depends on bug #736878, which is the 2.12 rebase bug

Comment 4 John Dennis 2012-02-28 20:30:16 UTC
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 ***


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