Re: Filter Access-Challenge Attributes

[Ben Wiechman]

Thanks

On Fri, Oct 30, 2009 at 6:42 AM, Alan DeKok wrote:

> Ben Wiechman wrote:
> > Is the following stub for filtering Access-Challenge attributes from
> > sites-available/default for future use?
>
>  There are some typos that are fix in the git "stable" branch.
>
>  Alan DeKok.
>
> -
> List info/subscribe/unsubscribe? See
> http://www.freeradius.org/list/users.html
>
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Re: Filter Access-Challenge Attributes

[Alan DeKok]

Ben Wiechman wrote:
> Is the following stub for filtering Access-Challenge attributes from
> sites-available/default for future use?

  There are some typos that are fix in the git "stable" branch.

  Alan DeKok.

-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Filter Access-Challenge Attributes

[Ben Wiechman]

Is the following stub for filtering Access-Challenge attributes from
sites-available/default for future use?

#   Auth-Type eap {
#   eap {
#   handled = 1
#   }
#   if (handled && (Response-Packet-Type == Access-Challenge)) {
#   attr_filter.access_challenge.post_auth
#   handled  # override the "updated" code from
attr_filter
#   }
#   }

Uncommenting the lines causes the server to fail to start because that
instance of the attr_filter module isn't defined. However subsequent testing
(and a quick dive into the code) show that attr_filter isn't supported in
the authenticate section. Should this stub simply be ignored at this point
or am I missing something?

Ben
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html