I think you are misunderstanding me, radtest for example does not do any escaping prior to sending data to radclient; so this input breaks it: # radtest rany aaaa\\ 127.0.0.1:1812 0 testing123 (0) Error parsing "stdin": Expected end of line or comma I'm trying to handle inputs like these so that radclient could handle someone having a `\` in the username/password. The issue is not shell escaping. On 5/7/23 15:58, Alan DeKok wrote:
On May 7, 2023, at 11:24 AM, rany <rany2@riseup.net> wrote:
Thank you, so I believe that radclient would just take care of this after escaping it. radclient takes the data after the shell has done escaping or unescaping.
However I was trying to understand the rules of escaping exactly, what are they? As I said, the shell does this. Not radclient. See the shell documentation for shell escaping rules.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html