ObliviOS

Home / FAQ

Questions people ask first

My answers to the questions people ask first, taken from the decision log and the threat model.

What does “source only” mean?

ObliviOS publishes source, records and a bill of materials, and nothing else. There is no build, no image and no update service, and no device is supported.

Can I install it?

Not yet. There is no image to flash. A device counts as supported only with verified upstream device source, current firmware and driver coverage, a monthly update path, signed images and updates, locked-bootloader verification, recovery validation, and evidence for emergency and radio functions. A booting image alone is not support.

Is ObliviOS a fork of GrapheneOS?

It is a distribution based on GrapheneOS, with its own identity, signing, updates, release process and support policy. The manifest repository pins revisions copied byte for byte from a GrapheneOS manifest tag, and the platform repository holds patch packages on top of them.

It is not an official GrapheneOS product, and it is not affiliated with or endorsed by the GrapheneOS project.

Is it more private or more secure than GrapheneOS?

I do not claim that. It preserves the hardening it inherits by default and adds features above it. The threat model states what it does not claim to defeat: a fully compromised hardware root of trust, unknown vulnerabilities, or network-level denial of service.

A weakness that already exists in GrapheneOS or AOSP is better reported to those projects. Tell me as well if my patches make it worse.

Does it need an account, or send telemetry?

No. These are constraints I do not trade away: no ObliviOS account, no mandatory telemetry, no advertising identifier and no cloud dependency. Normal use of the phone does not depend on AI.

Does Compartments hide my identity?

No. It makes apps unable to recognise the phone or to link to one another. The network address, the phone model, the installed apps and what you type stay visible, and the page for each app says so.

Why is Tor not the default for every app?

Because it was measured. Ten megabytes took 6.6 to 89 times as long as Direct, and a request started 11 to 18 times later. I refused that slowdown as a default. You can set any app to Tor, to your own WireGuard profile, or leave it on Direct.

What does Duress Unlock not defeat?

A sufficiently informed adversary who already suspects ObliviOS has the feature could demand proof that the shown profile is the only one, or examine the OS image offline for the code path. Timing differences between a wrong PIN, a decoy PIN and the real PIN are a residual risk. Publishing the source tells such an adversary the feature exists.

Which devices will be supported?

None is supported today. Two phones run ObliviOS builds: the Pixel 10a (stallion) that I use every day, and the Pixel 7a (lynx) that I develop on. The Pixel 10a is the phone I intend to publish images for. The devices page says what supported means.

Will there be images?

Not yet. If real interest in ObliviOS shows, I want to publish images for the Pixel 10a. I have set no date and I promise nothing: the five gates of a public beta on the status page have to be met first.

Which sites and accounts are yours?

Only oblivios.org, oblivios.dev and the four repositories on github.com/Beau4201 are mine. Do not trust any other site, app, account or package that uses the name ObliviOS. The contact page lists the four repositories.

Why do older records use other names?

The project was named AegisOS, SovereignOS and FreeholdOS before ObliviOS. The rename is decision 224. The decision log and the other records keep the names that were in use when they were written.

How do I report a security problem?

Open an issue, or email me if you would rather the problem is not public before it is fixed. Encrypting the email is optional. The security page has the address, the key and what to expect. You get a first reply from me within 3 days.