mrambossekandClaude Fable 5
cd187f9ef5
Two gaps found while answering where configuration lives. The confidential admin client needs a secret and there was nowhere to put one - I had added the issuer and both client ids but not the secret the admin login actually needs. It now reads from ECHOLOT_OIDC_CLIENT_SECRET, and preferably from ECHOLOT_OIDC_CLIENT_SECRET_FILE: a secret in the environment is readable by anything that can see /proc/<pid>/environ and lands in every dump of the unit's config, whereas a path is one file whose permissions an operator can reason about. (/etc/echolot-server.env was also 0644; now 0600 on fmr.) And the server now refuses to serve the admin UI in plaintext on a non-loopback address. The session cookie is a bearer credential for everything the server can do, and the OIDC authorization code arrives in a URL; in the clear, both belong to anyone on the path - and on a globally routable address that is the internet. A hard stop rather than a warning, because a warning in a log is not read by the person who most needs it, and because the safe answers are cheap: bind to loopback and tunnel, or supply a certificate. ECHOLOT_ADMIN_INSECURE=1 overrides it, so the decision is made rather than stumbled into. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Echolot
Free software for detecting and debugging local network issues from an Android phone — built for people who actually know what a neighbor table is.
Most "wifi analyzer" apps show you signal bars. Echolot aims at the layer where home and office networks actually break: duplicate DHCP servers, broken IPv6 RAs, MTU black holes, NAT64 weirdness, multicast that dies at the AP, DNS that answers differently than it should. It records what it observed, separates observation from interpretation, and exports the whole run so you can argue with it later.
Status: pre-release. The capability prober runs on real hardware; the production app and the probe server are not built yet.
Repository layout
docs/ design docs — the contract for everything below
echolot-prober/ capability prober: validates the no-root feasibility matrix on real devices
The Go probe server and the production app land here as siblings.
Design docs
The three specs are draft-complete and reviewed; treat them as the contract.
| Doc | What it defines |
|---|---|
| docs/feature-catalog-and-feasibility.md | Full feature list + the no-root feasibility matrix |
| docs/measurement-schema.md | Archived/exportable measurement JSON (observation vs finding, two-clock rule, anonymization) |
| docs/probe-protocol.md | Client↔server wire protocol (pinned TLS control plane, binary UDP data plane, STUN, canary DNS) |
| docs/build-status.md | Running log of decisions and next steps |
Privilege tiers
Every result records which tier produced it:
app— no root, no special setup. The bulk of the functionality.shizuku— ADB-shell privileges via wireless pairing, no root. Shipped in v1.root— future optional module.
Licensing
| Part | License | Why |
|---|---|---|
| All code (app, prober, server) | GPL-3.0-or-later | The value here is the platform-API research; copyleft keeps derivative apps free |
docs/ (the specs) |
CC-BY-4.0 | A wire protocol and a measurement format should be implementable by anyone, without license anxiety |
Full texts: LICENSE (GPLv3) and docs/LICENSE (CC BY 4.0).
Sources carry SPDX-License-Identifier headers.
If you want to build a compatible server or client, the protocol and schema docs are deliberately permissive — go ahead.
Building
See echolot-prober/README.md. Short version, from echolot-prober/:
echo "sdk.dir=/path/to/Android/sdk" > local.properties
./gradlew :app:assembleDebug