Integration with Chromium-based browsers and Electron apps

Aperta
#245 2 commenti 1 reazione 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
30/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
linux, rust

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
Rust
Stelle
310
Fork
22
Merge medio
1g 15h
PR unite (30g)
13

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di linux-credentials/credentialsd

Tutte le issue di linux-credentials/credentialsd

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.