Repository navigation
Security fixes from the November audit, plus the notes and plugin work from #276.
Security
- Password hashing (#278). New hashes are PBKDF2-HMAC-SHA256 at 600,000 rounds. Earlier builds used PBKDF2-HMAC-SHA1 at 100,000 on every supported install. Existing hashes still verify and are replaced when their owner next signs in; nothing to migrate.
- Chunked uploads (#279). An in-flight upload can only be continued, completed or aborted by the person who began it. Previously any teammate with write access who held the upload id could complete it and become the owner of the result.
- Key rotation (#280).
telemachus-secrets rewrapnow rewrites every encrypted column. Thirteen were skipped, so on an instance withTMACH_ENCRYPT_CONTENTon, older jobs, workflow runs and translations stopped opening once the previous key was dropped.telemachus-secrets statusnow reports rows still under a previous key. - Configuration posture (#281). The sign-up funnel no longer signs its challenge with a secret from the public source when
TMACH_SECRETis unset. Boot warnings name what is actually at risk, the all-zeros evaluation key fromcompose.yamlis flagged, andGET /api/admin/statusreportstoken_pepper,secret_keyandstrict_startup. - The deployment guide and the secrets runbook say to set the encryption key before storing a live credential (#277).
Features and fixes (#276)
- Notes:
.orgexport and import,#+FILETAGS:as an org note's tag home, the links graph, and an unknownvisibilityis now refused instead of stored. - Workers: a stop hands the job back without spending an attempt; a cancelled job releases its slot at once.
- Plugins: a route may be declared public and may serve its own media type.
- Localization: a duplicated catalog key fails the gate; a locale is offered only when it is translated enough to answer in.
Upgrade notes
- If you rotated the encryption key on 0.11.0 or earlier with
TMACH_ENCRYPT_CONTENTon and have since dropped the previous key: setTMACH_SECRET_KEY_OLDto it again, upgrade, and re-runtelemachus-secrets rewrap. - If you run more than one replica and never set
TMACH_SECRET: set it. A sign-up challenge issued by one replica is otherwise refused by another. - A script that begins a chunked upload as one user and completes it as another now gets a 404.
TMACH_PBKDF2_ITERSnow defaults to600000; a value under100000is ignored.- A rotation on a content-encrypted instance rewrites every job, run, step and translation row, so it takes longer than before.
Follow-ups from the audit that are not in this release are tracked in #282.