SysAdmin
6bafa85231
Run #4284's diagnostic (iter36) confirmed xorriso ignores every date-setting command we throw at it for the node it just -updated: flag=0x0e → CREATION + MODIFICATION + ACCESS (short form) CREATION ✅ (set from source file btime via touch -d): 7e 05 08 00 2c 3a 00 (= SOURCE_DATE_EPOCH) MODIFICATION ❌ (still wall-clock): A=7e 05 08 01 02 2c 00 B=7e 05 08 01 12 33 00 ACCESS ❌ (still wall-clock): A=7e 05 08 01 02 2c 00 B=7e 05 08 01 12 32 00 Tested across iters 34-36: * `-alter_date_r all "=N" /` — only fixed CREATION (b) * `-alter_date all "=N" path` after -update — same * `-volume_date c m x f u s "=N"` — volume-level only * `touch -d "@N" "${new_sqfs}"` before — fixed CREATION via btime * various orderings, with/without `--` terminators None override xorriso's wall-clock stamping of MOD/ACCESS at -commit. Concede that fight and just patch the bytes after xorriso writes the ISO. We KNOW exactly what's wrong — the TF entry for /live/filesystem.squashfs has its CREATION slot correct (= 7-byte ISO9660 short-form encoding of SOURCE_DATE_EPOCH) but MODIFICATION and ACCESS still hold the post-process commit time. So copy the 7 CREATION bytes over the 7 MODIFICATION bytes and 7 ACCESS bytes. The patcher (embedded Python, since silvermetal-builder ships python3): * Finds every TF entry header (`54 46 1a 01 0e`) near the "filesystem.squashfs" NM tag (96-byte window — anchors both ends so we don't touch some other file's TF entry). * Copies CREATION (offset +5..+12) onto MODIFICATION (+12..+19) and ACCESS (+19..+26). * Skips entries already correct (so re-running is a no-op). * Reports how many entries were patched. This is surgical: only the entry we know is broken, and only when its MOD/ACCESS actually differ from the (known-correct) CREATION. If the next run still drifts, the diagnostic byte-offset will tell us where the residual leak is (almost certainly in some volume descriptor field we haven't covered yet — at which point we extend the patcher). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
SilverMetal
Privacy-hardened devices for users who want their privacy back — on whatever platform they have.
SilverMetal is SilverLABS' cross-platform privacy-hardening program. We don't believe in "one true OS" — we meet users on the platform they actually use, and give them the strongest hardening that platform physically allows. Honestly labelled, no marketing fluff.
Two product lines
The SilverMetal program ships two distinct product lines, named to make their scope obvious to buyers:
🔒 SilverMetal OS
We ship the operating system or ROM. Full kernel-level control, our verified-boot key, our update channel. Strongest possible hardening.
- SilverMetal OS — Linux (Debian/Kicksecure-based ISO) — Tier A
- SilverMetal OS — Pixel (GrapheneOS-fork ROM) — Tier B
- SilverMetal OS — Samsung (LineageOS-fork ROM, unlocked-bootloader models) — Tier C
- SilverMetal OS — Motorola (DivestOS/LineageOS-fork ROM) — Tier C
🛡️ SilverMetal Enhanced
We harden the OS your device already runs. Configuration profiles, hardening installers, the SilverLABS Application Stack. For users who can't or won't replace their OS.
- SilverMetal Enhanced — Windows (LTSC IoT installer + hardening + Stack) — Tier C
- SilverMetal Enhanced — macOS (signed config profile + setup script + Stack) — Tier C-D
- SilverMetal Enhanced — iOS (MDM profile + Stack) — Tier D
- SilverMetal Enhanced — Android (generic profile + Stack on existing Android) — Tier D
Tiers explained in docs/platform-matrix.md.
What every SilverMetal device gets
Both lines ship the SilverLABS Application Stack — a suite of cross-platform privacy apps that replace the cloud services your device normally talks to (Google, Apple, Microsoft):
| Component | Status | Purpose |
|---|---|---|
| SilverBrowser | v1 (Linux MVP) | De-Googled, telemetry-free, fingerprint-resistant browser |
| SilverVPN | Existing — see SilverLABS/SilverVPN |
Always-on, no-logs VPN with our own infrastructure |
| SilverSync | v1 (Linux MVP) | Private replacement for iCloud / Google Drive / OneDrive |
| SilverChat | Existing — SilverVPN.Client.Chat, Signal Protocol over VPN transport. Promoted from v1.1 to v1 |
E2EE messenger |
| SilverDuress | v1.1 | Duress password / panic-wipe / anti-coercion |
| SilverKeys | v1.1 | Zero-knowledge password + 2FA manager |
Two ways to get SilverMetal
Every flavour — OS or Enhanced — supports both buyer modes:
"I'm choosing a new device"
Buy a preflashed SilverMetal SKU. We've done all the work; it arrives ready.
"I already own a device and want to harden it"
Download the free SilverLABS Stack + the SilverMetal OS or Enhanced package for your platform. Apply it yourself. Same software, same hardening, no hardware lock-in.
Status
| Component | Status |
|---|---|
| Documentation + roadmap | Initial scaffold complete |
| SilverMetal OS — Linux v1 | Phase 1 — moving to milestone 1.1 (build pipeline) |
| SilverLABS Stack v1 (Browser + Sync) | Planning |
| SilverVPN | Existing product, integration into v1 ISO planned |
| SilverChat | Existing product (SilverVPN.Client.Chat); promoted to v1, integration into v1 ISO planned |
| Other OS/Enhanced flavours | Planning, post-Linux v1 |
See docs/roadmap.md for the milestone-driven plan.
Related repositories
| Repo | Relationship |
|---|---|
SilverLABS/SilverVPN |
The VPN component of the SilverLABS Stack — already in production. SilverMetal integrates it; does not re-implement it |
SilverLABS/SilverApple |
Deprecated. Earlier iOS-hardening prototype, superseded by SilverMetal Enhanced — iOS |
SilverLABS/SilverDROID |
Unrelated (SilverSHELL AppStore Android client). Name is similar but scope is different |
Documentation
docs/threat-model.md— who we defend against, who we don'tdocs/design-principles.md— privacy-by-default, verifiability, honestydocs/platform-matrix.md— full per-platform pros/consdocs/roadmap.md— milestones, ship order, scopedocs/trust-model.md— signing keys, reproducible builds, governance
License
Components carry their own licenses (most are GPL/MIT/Apache-derived from upstream forks). Original SilverLABS-authored glue code is AGPL-3.0-or-later. See LICENSE.
SilverLABS
SilverMetal is built by SilverLABS — privacy-first infrastructure and applications.