Integration with Chromium-based browsers and Electron apps
维护者通常 2 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 30/100
- Issue 类型
- 功能
- 描述清晰度
- 需要澄清
- 活跃度
- 活跃
- 技术栈
- linux, rust
- 领域
- api, authentication, desktop
调研方向
This issue is primarily a design discussion, so there is no clearly bounded change to implement. Start by reading the existing Chromium, Electron, and Firefox integration details, then inspect the portal frontend API and the xdg-desktop-portal fork referenced in the issue. Consult #184 and Freedom's tracking issue for decisions and expected interfaces; completion depends on documented answers and an agreed browser integration path.
由索引模型根据 Issue 内容生成。
描述
We're working on passkey support in Freedom, a browser built on Electron (MPL-2.0). On Linux it ships as .deb, AppImage and pacman packages, not as a Flatpak.
Electron on Linux uses Chromium's WebAuthn code without Chrome's UI. It has no PIN entry, no hybrid (QR) flow and no platform authenticator, so passkeys barely work. Firefox integration is tracked in #41 and Mozilla bug 1983767. We couldn't find a matching issue for Chromium-based browsers or Electron apps (#25 is about the web extension), so this is one.
We'd like to use the Credentials portal once it is ready, and we can test against pre-releases. Some questions:
- Unsandboxed browsers. Freedom isn't sandboxed. How will the portal identify an unsandboxed host app and decide whether it may pass any origin, as a browser has to? Is that what #184 will define? Would a .deb, AppImage or pacman browser have a route to the "browser" level there, or would it get a prompt per origin?
- Which interface. An Electron app can't change Chromium's WebAuthn code. The practical route is the one your web extension takes: wrap
navigator.credentialsin the page, and call the portal from the browser process, passing the origin the browser has determined for the frame (never one supplied by the page). Is that a supported way to use the portal? Since v0.3.0 the extension uses the portal frontend API; is that what a browser should target today, through your xdg-desktop-portal fork? - Stability. Is there a rough idea of when the API will be stable enough for a browser to ship against, even behind a setting?
Freedom's tracking issue, with test results and source references: https://github.com/solardev-xyz/freedom-browser/issues/733.
- 主要语言
- Rust
- 星标
- 310
- 派生
- 22
- 平均合并
- 1 天 15 小时
- 30 天内合并 PR
- 13
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
linux-credentials/credentialsd 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
linux-credentials/credentialsd#277 ·
维护者通常 2 天内回复
-
documentation good first issue help wanted
难度 2/5 半天 新手友好度 62/100
linux-credentials/credentialsd#87 · 2 条评论 ·
维护者通常 2 天内回复
-
`check_origin_from_privileged_client` drops browser signalling intermediate cross-origin iframes未关闭
难度 3/5 1-2 天 新手友好度 57/100
linux-credentials/credentialsd#276 ·
维护者通常 2 天内回复
-
难度 3/5 1-2 天 新手友好度 52/100
linux-credentials/credentialsd#275 · 3 条评论 ·
维护者通常 2 天内回复
-
Cancel request when client disconnects可能已有人在做 @kpanuragh 今天认领。 未关闭
难度 4/5 3-5 天 新手友好度 48/100
linux-credentials/credentialsd#274 ·
维护者通常 2 天内回复
查看 linux-credentials/credentialsd 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 65/100
-
needs triage
难度 2/5 1-3 小时 新手友好度 76/100
pbakaus/impeccable#1620 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
swc-project/swc-next-issues#533 ·
-
bug
难度 2/5 1-3 小时 新手友好度 77/100
nautechsystems/nautilus_trader#5718 ·
维护者通常 1 天内回复
-
`luvus --remote` cannot start on a host whose login shell is Nushell可能已有人在做 @schlich 今天认领。 未关闭status: needs triage
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 4 天内回复