mirror of
https://github.com/fish-shell/fish-shell.git
synced 2024-12-19 21:43:41 +08:00
e01fc62d69
When we read bytes like \xfc that don't produce a Unicode code point, we encode them in a Unicode private use area. This encoding should be transparent to the user. We accidentally add it to uvar files as \uf6fc in this case. When reading it back, read_unquoted_escape() will fail at the "fish_reserved_codepoint(c)" check. This check is to avoid external input being misinterpreted as one of our in-band signalling characters like ANY_CHAR (for *). For encoded raw bytes, this check probably doesn't really matter in terms of security because the only thing we do with these bytes is convert them back to raw. So we could allow unescaping them at this point, thus supporting old uvar files. However that seems like the wrong direction. PUA encoding should never leak. So let's instead make sure to serialize it as \xfc instead of \f6fc going forward. Fixes #10313 |
||
|---|---|---|
| .. | ||
| abbrs.rs | ||
| common.rs | ||
| complete.rs | ||
| debounce.rs | ||
| editable_line.rs | ||
| encoding.rs | ||
| env_universal_common.rs | ||
| env.rs | ||
| expand.rs | ||
| fd_monitor.rs | ||
| highlight.rs | ||
| history.rs | ||
| input_common.rs | ||
| input.rs | ||
| key.rs | ||
| mod.rs | ||
| pager.rs | ||
| parse_util.rs | ||
| parser.rs | ||
| reader.rs | ||
| redirection.rs | ||
| screen.rs | ||
| std.rs | ||
| string_escape.rs | ||
| termsize.rs | ||
| threads.rs | ||
| tokenizer.rs | ||
| topic_monitor.rs | ||
| wgetopt.rs | ||