The documented snapshot is commit ea3554b5167f6780a8be77f1715f90ed02005665. Its configure.ac declares 2.4.0-kh22. The official release named icecast-2.4.0-kh22 was published on 4 July 2023; the pinned master commit is from 21 November 2023. Those are distinct provenance records, not interchangeable downloads.
Inventory the running system
Record executable origin, source commit or package revision, compiler options, libraries, service identity, configuration and public URLs. Record source protocols, listener authentication, wildcard priorities, relay origins, fallback media and any custom XSLT. Save a restricted backup and a known working binary before changing the service.
NEWS describes changes through kh22, including relay and connection handling. Read it as a change record, not proof that every named fix is in an unidentified package. Match the artifact to the source record.
Compare interfaces explicitly
| Boundary | KH snapshot contract | Migration question |
|---|---|---|
| Mount rules | Exact names, patterns and priority | Does the intended rule still win? |
| Authentication | Classic htpasswd/URL options | Does failure still deny admission? |
| Relays | Local mount and several host candidates | Are priority and retry semantics preserved? |
| TLS | Socket ssl and certificate paths | Are build support and certificate chain correct? |
| Administration | Registered KH command names | Does automation parse the actual response? |
| File paths | KH alias dest | Are public and private roots still separated? |
Do not replace KH configuration with regular Icecast 2.5 XML wholesale. Syntax, authentication roles, upstream definitions, TLS and directory settings diverge. Conversely, preserving an old XML file unchanged does not prove a new KH build accepts every option.
Stage, observe and keep rollback possible
Build an isolated candidate on different ports and paths, with no directory announcements. Exercise one source, a listener, deliberate disconnect, every relay/fallback route and authentication failure. Compare logs and statistical meanings. Record the exact binary and XML used for each result.
Only then plan a service window and matching rollback. Existing connections, authentication state and external clients need explicit observation. The editorial source comparison here is complete for the cited material; build and runtime acceptance remain separate checks and must not be inferred from this article.