Skip to content

Document Windows Hello limitation and passkey workarounds - #4

Merged
andrioid merged 3 commits into
mainfrom
issue-3-passkey-registration-windows-hello-is-no
Nov 3, 2026
Merged

andrioid merged 3 commits into
mainfrom
issue-3-passkey-registration-windows-hello-is-no

Conversation

@andrioid

@andrioid andrioid commented Nov 3, 2026

Copy link
Copy Markdown
Owner

Documents why Windows Hello isn't offered on Windows Chrome/Edge (ublproxy is ES256-only; Chromium requires RS256 for Hello) and the registration workarounds. Records the decision not to add RS256 support in DECISIONS.md.

Refs #3 (closed as won't fix).

ublproxy only supports ES256 passkeys. Chromium on Windows only offers
Windows Hello when RS256 is also accepted, so Windows Chrome/Edge users
need a phone, security key, password manager, or Firefox to register.

Refs #3
ubuntu-latest restricts unprivileged user namespaces via AppArmor, so
Puppeteer's Chrome fails to launch with 'No usable sandbox'. Pass a
puppeteer config with --no-sandbox; we only render our own .mmd files.
The committed SVGs could never match a CI render: Chrome measures
monospace text with the machine's font and bakes the sizes into the
SVG, so identical .mmd sources render differently on macOS and Ubuntu.

- Gitignore web/arch-*.svg and render them in pages.yml before upload
- CI diagrams job now only checks that every .mmd renders
- Pin @mermaid-js/mermaid-cli to 12.2.0 in mise.toml, ci.yml, pages.yml
- Update mermaid-diagram skill and DECISIONS.md
@andrioid
andrioid merged commit 981232e into main Nov 3, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant