Actions
Bug #23551
closedBroken handling of non-printable characters in techniques
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No
Description
Currently, when the input yml
technique contains a escaped non-printable character like \b
, it gets rendered into the output files, and in particular the generated metdata.xml
is invalid (non-printable characters are forbidden in XML 1.0 and must be escaped in XML 1.1).
id: "test"
name: "Test"
version: "0.1"
items:
- method: command_execution
params:
command: "my command \b is here"
The \b
is interpreted as backspace char in output files.
We need to:
- Check the behavior in 7.3
- Prevent our XML output from including forbidden chars. Check with upstream
quick_xml
lib which should not accept it. - Implement a simple fix for RC 2
Actions