micropython / micropython/micropython-lib
Why are these pairing parameters in aioble.security module private?
未关闭
还没有人认领这个 Issue。
- 主要语言
- Python
- 星标
- 2.9k
- 派生
- 1.1k
- 平均合并
- 7 天 6 小时
- 30 天内合并 PR
- 3
描述
The aioble security module defines several very important constants needed for pairing such as
_IRQ_ENCRYPTION_UPDATE = const(28)
_IRQ_GET_SECRET = const(29)
_IRQ_SET_SECRET = const(30)
_IRQ_PASSKEY_ACTION = const(31)
_IO_CAPABILITY_DISPLAY_ONLY = const(0)
_IO_CAPABILITY_DISPLAY_YESNO = const(1)
_IO_CAPABILITY_KEYBOARD_ONLY = const(2)
_IO_CAPABILITY_NO_INPUT_OUTPUT = const(3)
_IO_CAPABILITY_KEYBOARD_DISPLAY = const(4)
_PASSKEY_ACTION_INPUT = const(2)
_PASSKEY_ACTION_DISP = const(3)
_PASSKEY_ACTION_NUMCMP = const(4)
I don't understand why they are private. These same constants are needed in any pairing request invoked by the application which means the application must redefine them. I think I can still use them though linters will complain and that would violate policy. Can't they be made public or did I miss something (my search did not find any public set of such constants).
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
首先定位 aioble.security 模块,并检查其 pairing 常量当前是如何被引用的。确定这些值在公开命名和兼容性方面的要求,然后验证应用程序可以导入已公开的常量而无需重新定义它们,并确认相关检查均已通过。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- python
- 领域
- embedded-iot, security
- Issue 类型
- 功能
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 活跃度
- 停滞
- 描述清晰度
- 基本清楚
- 新手友好度
- 35/100