Revoke a paired phone, and log who connected
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- typescript
调研方向
Start with docs/specs/remote-security-model.md, docs/specs/security.md, docs/specs/security-local.md, and docs/specs/security-remote.md, then trace BurrowAcl, BurrowService, BurrowRuntime, and the dor entry points named in the issue. The issue leaves the Relay revocation scope undecided and spans persisted ACL state, live sessions, interfaces, and auditing rules. Done means both Known gaps entries are removed, the guarantees table has revocation and access log rows with their pins, and the audited rules are documented.
由索引模型根据 Issue 内容生成。
描述
Two of the remote-control gaps on dormouse.sh/security are the ones a user of a paired phone feels first: nothing revokes a paired phone, and nothing records who connected. Both are about a user being able to see and control access to their own computer.
Revocation
Today BurrowAcl.revokeClient / revokePasskey have no callers and no relay frame carries a revocation, so revoking a phone means hand-editing Burrow state and restarting the Burrow (docs/specs/remote-security-model.md -> "Revocation propagation"). A lost or sold phone stays paired until the presence window lapses and, after that, until someone edits the ACL.
- A Settings → Remote control list of paired phones (name, paired date, last seen), each with Revoke, on both Burrows (Standalone and VS Code).
- Revoking takes effect on running sessions, not only on the next Burrow start:
BurrowServicecurrently handsBurrowRuntimeone ACL snapshot for its whole lifetime. - A matching
dorverb, so an agent or a script can list and revoke. - Whether the Relay pushing a revocation to a Burrow (from Pocket on another device, or from the Hosted account page) is in scope or a follow-up. The Burrow stays the only writer of its ACL.
Access log
The Burrow records approvals, and some rejections go to owner-local logs. Nothing answers "did anyone connect to my laptop last night" (docs/specs/security.md -> "Known gaps").
- An owner-local, append-only, bounded log of connects, attaches, denials (with the specific ACL miss, which stays off the wire), pairings, revocations, and one-time sessions: which phone, when, the path (direct or relayed), and how long.
- Visible beside the paired-phone list, and through
dor. - No terminal content, ever. It sits under the same persisted-state boundary as the ACL (
docs/specs/security-local.md-> "Persisted state").
Done means
Both Known gaps entries are gone from docs/specs/security.md, the guarantees table gains rows for revocation and the access log with their pins, and the audited rules land in docs/specs/security-remote.md.
- 主要语言
- TypeScript
- 星标
- 5
- 派生
- 1
- 平均合并
- 10 小时 51 分钟
- 30 天内合并 PR
- 507
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
diffplug/dormouse 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 86/100
diffplug/dormouse#912 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 4/5 1-2 天 新手友好度 25/100
diffplug/dormouse#1235 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 4/5 1-2 天 新手友好度 48/100
diffplug/dormouse#1234 · 1 条评论 ·
维护者通常 1 天内回复
-
security-audit-status
难度 5/5 一周以上 新手友好度 5/100
diffplug/dormouse#1137 · 42 条评论 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 18/100
diffplug/dormouse#1090 · 4 条评论 ·
维护者通常 1 天内回复
查看 diffplug/dormouse 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
kunchenguid/gh-axi#220 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
enhancement
难度 2/5 1-3 小时 新手友好度 79/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
prerender: wait for env-runner worker readiness before crawling可能已有人在做 @sarankumar1325 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复