Integration with Chromium-based browsers and Electron apps

オープン
#245 コメント 2 件 リアクション 1 件 担当者 0 名 GitHub で見る

メンテナーはふだん 2 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
30/100
issue の種類
機能追加
明瞭さ
説明が足りない
活発さ
活発
技術スタック
linux, rust

調査の方向性

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:

  1. 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?
  2. Which interface. An Electron app can't change Chromium's WebAuthn code. The practical route is the one your web extension takes: wrap navigator.credentials in 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?
  3. 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時間
マージ済み PR(30日)
13

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

linux-credentials/credentialsd のほかの issue

linux-credentials/credentialsd の issue をすべて見る

似ている issue

Rust の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。