ipfs/kubo

Escape paths in `ipfs ls`

Open

#5,887 创建于 2019年1月2日

在 GitHub 查看
 (0 评论) (0 反应) (0 负责人)Go (13,906 star) (2,725 fork)batch import
help wanted

描述

Running ipfs object patch add-link QmUNLLsPACCz1vLxQVkXqqLX5R1X345qqfHbsf67hvA3Nn $(echo -e '\e[1;1H\e[44;37m\e[K\e[2;1HHI\e[34m_\e[37mTHERE!\e[3;1H\e[K\e[49;39m') QmUNLLsPACCz1vLxQVkXqqLX5R1X345qqfHbsf67hvA3Nn gets us a really fun hash - QmUKpty1aF3ak42WTnebPsGkYyq6A6g9Jt2fYpanwzk6tx.

ipfs ls on that hash will print HI THERE on a blue background.

We should detect \e (and other characters like space) and escape it in cli encoder

贡献者指南

技术栈
go
领域
clisecurity
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Go programmingunderstanding of terminal escape sequences
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
40
研究方向
The issue is about escaping escape sequences (like \e) in the CLI output of `ipfs ls`. The fix likely involves modifying the CLI encoder in the go ipfs codebase, possibly in the `core/commands/ls.go` or related files. Look for where the output string is formatted and ensure that characters like \e (0x1b) are escaped before printing. A maintainer may need to confirm the desired approach (e.g., using fmt.Sprintf or a sanitization function). No existing PRs or comments provide further direction.
Escape paths in `ipfs ls` · ipfs/kubo#5887 | Good First Issue