28 Aug
2007
28 Aug
'07
8:24 a.m.
Hi, Alan DeKok wrote:
The only way to *really* fix the problem is to track the origin of data, and keep tainted / untainted flags.
Why not move the escaping that is done by librad_safeprint to the 'default escape function' (xlat_copy) when xlating? This would avoid the double escaping when a module supplied escape function is given to radius_xlat and keep the status quo otherwise. Enrik