[radsecproxy] Rather severe bug in 1.8.0 : secret field content erroneously interpreted

Hi,

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.

Result :  clients and/or servers who use a secret containing substring "%hh" are rejected !

I suspect the function unhex() in gconfig.c to be the culprit...

Christian