keybase / keybase/client

Keybase on Windows in S Mode

Open
#28,316 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
9.2k
Forks
1.3k
Avg merge
12h 58m
Merged PRs (30d)
56

Description

**Describe the bug**
New Windows systems are distributed in [S mode](https://learn.microsoft.com/en-us/windows-hardware/design/device-experiences/oem-10s-security), only running binary code that is signed. Third party applications can be published on the Microsoft Store or as web apps. It's not clear how to run Keybase under these conditions as downloadable installers do not launch.
 
**To Reproduce**
1. Use a Windows system in S mode, such as a new cheap Windows laptop.
2. Try to install Keybase by downloading the installer.
3. See a popup that Windows in S mode will only run applications from the Microsoft Store.

**Expected behavior**
Disabling S mode disables integrity verification of the entire system and cannot be undone. There should be some way to use Keybase on Windows in S mode, whether this is a web application or availability in the [Microsoft Store](https://learn.microsoft.com/en-us/windows/apps/publish/), or even some supported virtualized environment of some sort.

**Screenshots**
![Image](https://github.com/user-attachments/assets/4aafbf3c-0f77-418b-ab23-b6df4581cddf)

**Additional numbers**
The number 345567

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue names no files, tests, or entry points. First determine whether Microsoft Store distribution, a web app, or a virtualized environment is in scope, then define a supported Windows S mode path and a verification procedure.

Written by the indexing model from the issue text.

Assessment

Domain
desktop-dev, operating-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.