V4.2.0
Latest
October 2026
More regulated, more secure
Built toward the security baseline of the EU Cyber Resilience Act — individual credentials, access the operator grants and can see, a documented recovery path, masked secrets, a firewall the operator can read, security updates that install on their own — around package installs from a URL, scans as jobs, an encrypted built-in HLS output, SRT link figures, forms that follow the operator's choice, the operator's own brand on the portal, and AM, FM and DAB+ radio reception. Proven in the field before publication: 55 units of one operator were upgraded remotely in one afternoon, thanks to the management API v2 and Kylone's support-access framework.
- Built toward the EU Cyber Resilience Act: the Act's security baseline, and ETSI EN 303 645 for single-board devices, as the yardstick — credentials individual to the unit, remote access the operator grants for a period and can revoke, no way into the unit without a login, secrets masked on every page, security updates that do not wait for a release. The licence agreement (v1.3) and the privacy page were revised with it.
- An administrator password of its own on every unit: the installer generates one, shows it once and has it typed back; firmware images for single-board devices use the device's hardware address from the label until the first login. The first login must replace it, every password set for someone else is a first-login password as well, and one policy applies everywhere. Existing units keep their passwords.
- Support access granted by the operator: the Remote Support section of System Settings holds the support connection switch and a grant, "Support Access (SSH)", for 24 hours, 3 or 7 days, or until revoked; support engineers work through that grant and nothing else, and every grant and revocation is logged and notified.
- SSH keys on a page: System › Users › SSH Access lists the shell keys with type, fingerprint and last use, adds a pasted key, removes one, switches password login off once a key is present, and can limit the service to one interface. New installs start with an empty list.
- Console recovery by the book: the physical console offers no session without a login and the boot loader password is random and held by nobody; recovery is a documented "Kylone Recovery" boot-menu entry with exactly three actions, each logged and notified — a new administrator password shown once, a temporary DHCP address for that boot, or the installer's firewall openings — after which the normal boot continues. It can be disabled in System Settings; then a reinstall is the only way back.
- Secrets stay masked: passphrases, passwords and keys on every page — SRT, RTSP, RTMP, BISS, SNMPv3, Sharing, set-top box Wi-Fi, client secrets, the API key — show masked with Show and Copy buttons; the management API answers them unchanged.
- A firewall the operator can read: System › Firewall › Policies lists what the firewall actually holds, every rule removable, and adds policies by action, source, protocol, port or service, optionally on one interface. The Firewall page computes the openings this unit needs from its licence, its switches and its sources, lists them present or missing with their reason and adds the missing ones on Add Missing or when a service is turned on. The Apply page says when one is missing. New installs open the web UI and SSH only.
- Security updates on their own: one switch installs the distribution's security updates once a day, kernel excluded, without a reboot, and reports every run by email.
- What a unit tells Kylone: licence activation and licence validation with branding, nothing else — no statistics, no logs, no credentials, independent of the remote support switch; a unit keeps working when it cannot reach Kylone. The "Send Usage Statistics" switch is gone because there is nothing to send.
- Install from a URL, update modules in place: under System › Tools the unit downloads a package itself, with live progress and an optional hash check — modules, module updates, system upgrades and OS updates alike; a partial package updates only the files it carries while the module's settings and data stay in place.
- Scans as jobs: the Configure Programs scan runs detached under the operation feed, one job per tuner input and concurrent across inputs, with its live log in the web UI and in the management API; blind-scan runs on different adapters execute at the same time.
- Delivery: the built-in HLS output has the AES-128 option with key store, key endpoint and rotation without restart; the delivery settings page separates the listeners from the stream outputs; every SRT socket reports its own round-trip time, loss, retransmissions, drops, bandwidth and buffer on the status page, in the metrics and in the MIB.
- Forms that follow your choice: record forms show only the fields that apply to what is selected and change with the selection, with no intermediate save; required checks apply to visible fields only, and the management API reports the rule behind every dependent field.
- Your brand on the portal: a unit managed by the central management can carry the operator's own company name, logo, favicon and links, set on the central for a distributor, a customer or a single unit; a unit without a brand looks exactly as before.
- Monitoring: the SNMP subtree answers from one resident process, a full walk in a fraction of a second, with the new KYLONE-MIB on unchanged object identifiers and new groups for the engine, the processing nodes, stand-ins, interfaces and storage; a host name per unit; bit error ratio and uncorrected blocks beside signal and carrier-to-noise where the card provides them; a Prometheus metrics endpoint.
- AM, FM and DAB+ radio: with the radio receiver card, stations are carried as channels like any other input — same status page, same audit, same delivery paths — with a Receivers page for the cards and a Stations page for what the scans found or a frequency added by hand.
- Housekeeping: "Apply" replaces "Commit" everywhere; long sidebar sections fold; every page has a short name, an explanatory title and a one-line definition in all three languages; the About page shows the provider, the version and the licensed features; product names follow the licence; scheduled stand-in scenarios and ad insertion are the Broadcast licence option, every product keeps the automatic backups; a lock-file fault that could freeze the status figures for days is fixed.
- Upgrading from v4.1.x: the upgrade keeps passwords and settings and brings the unit to the new baseline once — vendor access moves under Remote Support (where remote support is allowed, the maintainer's web access appears as a visible user named support on the Users page, to keep or remove), the console session gives way to the recovery entry, and the firewall openings are rewritten in the form the Firewall page understands. The firewall's running state is never changed by an upgrade.