beta · 3 October 2026
Maran 1.0.0-beta.3: installs on thirteen distributions
Maran now installs to a working panel on thirteen distributions in both families, EL8 included, and a suspended login can no longer get working tokens.
Maran could not be installed on half the systems it claimed to support. Now it can. The supported matrix is Debian 12/13, Ubuntu 22.04/24.04/26.04 LTS, and RHEL, AlmaLinux, Rocky Linux and Oracle Linux 8/9/10, seventeen releases in both families. Thirteen of them are now installed from nothing to a working panel and checked through the panel's own health endpoint, not the installer's exit code: every Debian and Ubuntu release, AlmaLinux and Oracle Linux 8/9/10, and Rocky Linux 8/9. RHEL itself cannot be tested this way, because its images carry no nginx or PostgreSQL without a subscription. Rocky Linux 10 has no image in the harness yet. Both use the same code path as the rest of their family.
So much was broken because nobody had ever run the documented install path against a real init.
A fake systemctl cannot fail on a unit directive, a mount namespace or a binary that will not
execute, and every defect below is one of those. maran installer closes the gap with a fresh
server running real systemd as PID 1, on both families and both architectures.
What changed for operators
- AlmaLinux, Rocky and Oracle 8: the panel never started. The default PostgreSQL there is 10. The installer now requires 13 or newer and, on EL8, enables a newer module stream from the distribution's own AppStream, no third-party repository.
- Those same systems could not verify any release. The manifest signature used an OpenSSL option
that EL8's OpenSSL 1.1.1 lacks, and the installer wrongly blamed a compromised mirror. Releases are
now signed with ECDSA P-384 and verified with
openssl dgst, which every supported OpenSSL has. - Oracle Linux: the root daemon refused to start. The agent answered
unsupported distro: ol, andrhelwas missing from its list too. A structure check now keeps the installer's list and the agent's list identical. - Ubuntu 22.04, Debian 12 and EL8: the agent could not run. It linked against whatever glibc the release host had. It is now built inside an AlmaLinux 8 container, which has the oldest glibc in the matrix, and the release refuses to ship an agent that needs a newer one.
- An install could report success with the root daemon dead. Step 70 now waits for the agent's socket as well as the panel's, and fails with a specific error if it never appears.
- The agent died on a fresh host before running anything. Its unit required
/var/lib/maran-ftpsas a writable path before the installer had created it. The installer now creates it with the rest of the layout. - The installer now installs missing dependencies:
openssh-server,libicuand thehostnamebinary (absent on Oracle Linux 8, where the install died at exit 127). - EL8: MariaDB was installed and then refused. That MariaDB leaves root without a password. The installer still refuses a server that existed before the install, but it now secures one it created moments earlier.
Security
A suspended login could still obtain working access tokens. Refreshing a session only checked that the user existed, not that the login was still usable. If suspension was interrupted between writing the state and revoking the sessions, the suspended login kept live sessions, and each refresh turned one into a new token, indefinitely. That question now has a single definition on the domain entity, both paths that mint a token ask it, and a structure check rejects any future file that issues a token without asking.
Also in this release
- ARM64 is built and runs.
maran release build --arch bothproduces a manifest with all six artifacts, and the aarch64 agent and panel were verified by executing them on aarch64 with glibc 2.28. The firewall step cannot complete under emulation, so ARM64 is not yet claimed as verified end to end. - Dependency updates are now chosen by hand. Dependabot is off. Ten updates are taken and nine are refused, each with a reason: the .NET 10 line, TypeScript 7, and the coupled tonic/prost/askama releases. The cost is that security updates no longer arrive on their own.
- Internal: the polygon's 7381-line assertion script is split into twelve files. Its output is unchanged.
Installing
curl -sSL https://get.maran.innovayse.com | sudo bash