DNSControl
DNSControl is rewriting its record internals in public, one release candidate at a time
Comparison · Infra & APIs
Fission vs mod_auth_openidc
A side-by-side editorial comparison of Fission and mod_auth_openidc — release velocity, themes, recent moves, and the top alternatives to consider.
Fission vs mod_auth_openidc: at a glance
What is Fission?
Fission's release feed carries only RC tags, and none of them say what shipped
Every entry here is a release candidate — v1.22.0-rc1 and rc2, v1.23.0-rc1, v1.25.0-rc1 — with no final release appearing between them, and the version sequence skips 1.24 entirely. The bodies are whatever the tagging commit said, so what reaches this feed is a dependabot bump, a CLI tool-version refresh, a codegen sync explicitly labelled as having no functional change, and one entry that is nothing but links to an external release-highlights page. The actual release notes live on the project's documentation site, not here.
What is mod_auth_openidc?
mod_auth_openidc audited itself, found eight holes, and broke every session on the way out
The Apache OIDC module is in the middle of the most consequential ten days in this window: 2.4.20 on August 1 rebuilt session and cookie encryption around PBKDF2-HMAC-SHA256 key stretching and invalidated every existing session, 2.4.20.1 on August 9 disclosed eight security issues found in an internal audit, and 2.4.20.2 the next morning walked back part of the fallout. The audit findings are not peripheral — the most serious lets a client inject headers that a protected backend trusts as authenticated identity claims on paths the module answers without authenticating. The 2.4.19.x line before it had already shipped an out-of-bounds read and write in the state-cookie parser.
Fission vs mod_auth_openidc: editorial side-by-side
Fission
0.0INFRA · APIS
Fission's release feed carries only RC tags, and none of them say what shipped
◆ Current state
Every entry here is a release candidate — v1.22.0-rc1 and rc2, v1.23.0-rc1, v1.25.0-rc1 — with no final release appearing between them, and the version sequence skips 1.24 entirely. The bodies are whatever the tagging commit said, so what reaches this feed is a dependabot bump, a CLI tool-version refresh, a codegen sync explicitly labelled as having no functional change, and one entry that is nothing but links to an external release-highlights page. The actual release notes live on the project's documentation site, not here.
◆ Where it's heading
What can be read from these tags is infrastructure maintenance rather than product direction: Go dependency updates, helm and kind and skaffold and cosign version refreshes, and regenerated swagger and applyconfiguration files kept in sync with CEL and webhook validation comments in the core API types. That last one is the only entry hinting at anything structural — CEL-based validation on the API types implies declarative validation moving into the CRDs — but the commit itself changes only generated output.
◆ Prediction
This feed does not carry enough to predict product direction; until final releases or their notes appear here rather than only candidate tags, any read of where Fission is heading would be guesswork.
mod_auth_openidc
6.3INFRA · APIS
mod_auth_openidc audited itself, found eight holes, and broke every session on the way out
◆ Current state
The Apache OIDC module is in the middle of the most consequential ten days in this window: 2.4.20 on August 1 rebuilt session and cookie encryption around PBKDF2-HMAC-SHA256 key stretching and invalidated every existing session, 2.4.20.1 on August 9 disclosed eight security issues found in an internal audit, and 2.4.20.2 the next morning walked back part of the fallout. The audit findings are not peripheral — the most serious lets a client inject headers that a protected backend trusts as authenticated identity claims on paths the module answers without authenticating. The 2.4.19.x line before it had already shipped an out-of-bounds read and write in the state-cookie parser.
◆ Where it's heading
The project has shifted from feature work to hardening its own attack surface, and it is doing so on its own initiative rather than in response to external reports. That posture has a cost operators are absorbing directly: two backwards-incompatible session format changes in six months, both of which log every user out on upgrade. The 2.4.20.2 release also shows the hardening overshooting and being corrected — unconditional secret masking made debugging impossible, so an opt-in escape hatch was added with a startup warning attached, and a derived-object cache tier added only weeks earlier was removed outright.
◆ Prediction
Expect the 2.4.20.x line to keep absorbing follow-up fixes from the same audit, and any further hardening to arrive with an explicit opt-out after the masking reversal showed operators cannot troubleshoot a protocol exchange they cannot read.
Alternatives to Fission and mod_auth_openidc
Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Fission or mod_auth_openidc.
Kaniko
Kaniko's release feed stops dead in June 2024 after a patch that undid its own change
Antrea
Kubernetes CNI maintaining four release branches at once, mostly to carry CVE fixes back.
KeeWeb
KeePass-compatible password manager frozen mid-patch-run since 2021.
Nebula
Overlay network that rewrote its certificate format, then spent a year fixing what it exposed.
Prometheus Alertmanager
Alertmanager is dismantling its global state one contention bug at a time
See all Fission alternatives → · See all mod_auth_openidc alternatives →
Recent activity from Fission and mod_auth_openidc
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agomod_auth_openidcOIDCDebugMaskSecrets reopens debug logs, cache tier removed
- 1d agomod_auth_openidcInternal audit turns up eight security issues, including an identity-header bypass ⚡
- 10d agomod_auth_openidcPBKDF2 key stretching invalidates all existing sessions
- 1mo agomod_auth_openidcOut-of-bounds read and write fixed in the state-cookie parser
- 2mo agoFissionFission 1.25.0-rc1 tag carries only regenerated codegen output
- 2mo agomod_auth_openidcFixes core dumps under threaded MPM startup load
- 2mo agoFissionFission 1.23.0-rc1 tag carries a CI tool-version refresh
- 5mo agomod_auth_openidcFixes claims-based authorization regression in OAuth RS mode
- 7mo agoFissionv1.22.0-rc2
- 9mo agoFissionFission 1.22.0-rc1 tag carries a golang.org/x/net bump
Frequently asked questions
What is the difference between Fission and mod_auth_openidc?
They serve adjacent needs but don't currently overlap on shipped themes. mod_auth_openidc is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Fission better than mod_auth_openidc?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. mod_auth_openidc is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to Fission?
Top Fission alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Fission alternatives" section above for the current picks, or visit /alternatives/fission for the full list with editorial commentary on each.
What are the best alternatives to mod_auth_openidc?
Top mod_auth_openidc alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "mod_auth_openidc alternatives" section above for the current picks, or visit /alternatives/mod-auth-openidc for the full list with editorial commentary on each.