mirror of
https://github.com/freemkv/freemkv-keysources.git
synced 2026-10-07 18:13:11 +00:00
Matthew Jackson
e963104dcf
Every request to the key service carries base64 AACS key material in its body — the unit-key file, the MKB, content samples, the volume ID — and a bearer token in a header when one is configured. Over http:// all of that goes to any on-path observer, and the token is replayable. There is no plaintext deployment to preserve. The address guard already rejects loopback, RFC1918, ULA and link-local, so an http:// URL can only ever reach the public internet, which is the worst case for cleartext; a self-hosted keyserver on a LAN is impossible under that guard whatever its scheme. A non-https URL now skips the online source with a warning rather than transmitting, so a misconfiguration falls through to the local keydb and says why instead of leaking quietly.