SPICE transport issues about openuds HOT 4 CLOSED

Thanks for your detailed report.

Point 1 is not only the workaround, it's also the solution :). The problem is that on the upgrade process to 3.0 security model (separated data from script, and signed scripts), probably there was some confussion in there, and it was using the incorrect template script.

Point 2 is also the solution. On 2.x there was an string insertion, so the \\n passed to \n (i mean, that the \n on destination was a "code string" "\\n", that once interpreted will become "\n"), but now on 3.0 onwards, this is provided as data, so it needs to be \n. (no conversion is needed here, because the value will not be interpreted by an script, just used)

Thanks for both solutions, if you can check it now, i'll appreciate it ;-)

from openuds.

Hi,
I've already tested this fixes, spice direct transport works fine. I was hoping you can add them to the code :)

from openuds.

sorry, i didn't explain correctly.
The fixes you proposed are already added to the base code (done it when you reported it ;-) ), and i was wondering if you can test the fixes in the code, (that must match yours). :)

from openuds.

Did the test with fixes in the code - the problem is solved. Thanks! :)

from openuds.