Re: [radsecproxy] Problem with some values of secret string ?

Wiethoff, Helge wrote on 09/10/2019 16:44:

Hi Christian,

I guess this was an this list a few weeks ago:

not exactly. If you reread you'll see we take into account the translation of  the  sequences "%hh" in the secret strings...

Christian

Fabian Mauchle wrote on 12/09/2019 15:54:

...

...

Hi Christian,

On 12.09.19, 15:34, "radsecproxy on behalf of Christian Claveleira"

<radsecproxy-bounces@lists.nordu.net on behalf of Christian.Claveleira@renater.fr> wrote:

...

  it seems the content of the secret string is interpreted when it

contains a "%" :

...

  when a client (or server) declaration contains
  secret   fht8CD%E7am

  it is interpreted as
  getgenericconfig: block client xxxx.yyyyy: secret = fht8CDçam

  One can see "%E7" is translated as the "ç" character.

This case is mentioned in the manpage radsecproxy.conf(5): If you want to write a % and not use this decoding, you may of course

write % in hex; i.e., %25.

...

Regards, Fabian

Regards Helge

---

radsecproxy mailing list radsecproxy@lists.nordu.net https://lists.nordu.net/listinfo/radsecproxy