special characters in passwords + FR + ldap
Natalia Escalera
nescalera at gmail.com
Sat Mar 11 04:54:09 CET 2006
Hello,
Do you have any suggestion of how to fix the problem?
Thanks,
Natalia.
On 3/9/06, Natalia Escalera <nescalera at gmail.com> wrote:
> Hello,
>
> > how did you patch?
>
> What I did is that I took the rlm_ldap.c from FR 1.1.0 and replaced
> the content of the function ldap_pairget with the code shown on
> http://bugs.freeradius.org/showattachment.cgi?attach_id=112. Then I
> execute the './configure' and 'make' commands
>
> Natalia.
>
> On 3/9/06, A.L.M.Buxey at lboro.ac.uk <A.L.M.Buxey at lboro.ac.uk> wrote:
> > Hi,
> >
> > > I attached a copy of the file rlm_ldap.c of radius 1.1.0
> >
> > yes, your patched version is clearly borked - as you can see from
> > this snippet.
> >
> > > int vals_count;
> > > int vals_idx;
> > > char *ptr;
> > > char *value;
> > > TLDAP_RADIUS *element;
> > > LRAD_TOKEN token;
> > > LRAD_TOKEN token, operator;
> > > int is_generic_attribute;
> > > char value[256];
> > > char buf[MAX_STRING_LEN];
> > > VALUE_PAIR *pairlist = NULL;
> > > VALUE_PAIR *newpair = NULL;
> > > char do_xlat = FALSE;
> >
> > LRAD_TOKEN has dual definitions. it should look similar to:
> >
> > char **vals;
> > int vals_count;
> > int vals_idx;
> > char *ptr;
> > char *value;
> > TLDAP_RADIUS *element;
> > LRAD_TOKEN token, operator;
> > int is_generic_attribute;
> > char buf[MAX_STRING_LEN];
> > VALUE_PAIR *pairlist = NULL;
> > VALUE_PAIR *newpair = NULL;
> > char do_xlat = FALSE;
> >
> > how did you patch? I notice that the patch is no longer clean against the
> > 1.1.x CVS code...which means that more headaches will occur. someone with
> > the drive/desire needs to modify the patch for the more recent source
> >
> > alan
> > -
> > List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
> >
>
More information about the Freeradius-Users
mailing list