Integration with Chromium-based browsers and Electron apps

Ouverte
#245 2 commentaires 1 réaction 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 2 jours

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
30/100
Type d'issue
Fonctionnalité
Clarté
À clarifier
Activité
Active
Stack technique
linux, rust

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
Rust
Étoiles
310
Forks
22
Merge moyen
1 j 15 h
PR mergées (30 j)
13

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de linux-credentials/credentialsd

Toutes les issues de linux-credentials/credentialsd

Issues similaires

Plus d'issues Rust

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.