Re: Returning Vendor Specific Attribute in radius reply
I am running 3.0.15 $ radiusd -v radiusd: FreeRADIUS Version 3.0.15, for host x86_64-alpine-linux-musl, built on Jul 18 2017 at 09:03:14 FreeRADIUS Version 3.0.15 Copyright (C) 1999-2017 The FreeRADIUS server project and contributors There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE You may redistribute copies of FreeRADIUS under the terms of the GNU General Public License For more information about these matters, see the file named COPYRIGHT -Najam -----Original Message----- From: Freeradius-Users [mailto:freeradius-users-bounces+najam.siddiqui=gemalto.com@lists.freeradius.org] On Behalf Of Alan DeKok Sent: Wednesday, August 23, 2017 6:27 AM To: FreeRadius users mailing list <freeradius-users@lists.freeradius.org> Subject: [+SPAM+]: Re: Returning Vendor Specific Attribute in radius reply On Aug 22, 2017, at 11:02 PM, Siddiqui Najam <Najam.Siddiqui@gemalto.com> wrote:
Hi Alan,
I did some debugging and code hits src/lib/value.c:585 and returns -1. This is confusing because we set the attribute name to Attr-26.
Then you're running an older version of the server. Please use 3.0.15, which has this issue fixed. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html ________________________________ This message and any attachments are intended solely for the addressees and may contain confidential information. Any unauthorized use or disclosure, either whole or partial, is prohibited. E-mails are susceptible to alteration. Our company shall not be liable for the message if altered, changed or falsified. If you are not the intended recipient of this message, please delete it and notify the sender. Although all reasonable efforts have been made to keep this transmission free from viruses, the sender will not be liable for damages caused by a transmitted virus.
On Aug 23, 2017, at 7:45 AM, Siddiqui Najam <Najam.Siddiqui@gemalto.com> wrote:
I am running 3.0.15
Hmm... OK. The issue then seems to be that rlm_python isn't using the same API as the other modules to create attributes. Can you do a test for me? Go to src/modules/rlm_python/rlm_python.c, and find this code: if (tmpl_from_attr_str(&dst, s1, REQUEST_CURRENT, PAIR_LIST_REPLY, false, false) <= 0) { ERROR("%s - Failed to find attribute %s:%s", funcname, list_name, s1); continue; } change the "false, false" to "true, false". Then re-build && re-install the server. If that works, I'll push a change. Otherwise, it will take more work to track it down and fix it. Alan DeKok.
participants (2)
-
Alan DeKok -
Siddiqui Najam