Fedora developers have filed a change proposal that could transform how administrators and enthusiasts set up Atomic Desktop variants. The plan targets Fedora Linux 45. It focuses on secure web-based remote installations for images such as Silverblue and Kinoite.
Bruno Ciconelle, the proposal owner from Red Hat, outlined the details in the Fedora Project Wiki. Users would boot the target system with a specific kernel parameter. Then they complete the entire OS setup from a web browser on a separate machine. No VNC or RDP clients required. Short. Direct. And a notable shift from past practices.
The mechanism relies on the Anaconda WebUI, which has seen steady refinement. Earlier previews appeared in Fedora Magazine back in June. That article detailed a proof-of-concept using a GitHub pull request with hardcoded PINs and no TLS. But the current proposal hardens everything for production use. It adds pin-based authentication by default. It enforces HTTPS with self-signed certificates generated by Cockpit. And it isolates the Cockpit configuration under /etc/anaconda/cockpit/ so nothing leaks into the final installed system.
Boot with inst.webui.remote and optionally inst.webui.remote.password=YOURPIN. The installer shows the machine’s IP address on the local console. Point any browser to https://
Consider lightweight ARM single-board computers. Raspberry Pi devices come to mind. They carry limited CPU and memory. Running a full desktop session or browser locally steals cycles the installer could use. Offload the interface to another device. The target only runs a lightweight cockpit-ws process. Performance improves. Resource consumption drops. Practical gains emerge for edge deployments or headless servers that still need a guided graphical setup.
Security Takes Center Stage in the Design
Previous remote options carried risks. VNC often ran unencrypted. Passwords faced tight length limits. The new system defaults to secure behavior. HTTPS encrypts traffic. PIN authentication follows the pattern set by inst.rdp. An opt-out flag inst.webui.remote.noauth exists for trusted networks or development. Without the boot parameter, nothing changes. Remote access stays disabled. The proposal stresses this opt-in nature repeatedly. It won’t affect standard installs or live images.
Testing instructions appear straightforward. Download a Fedora 45 Atomic Desktop ISO. Add the kernel options at boot. Note the IP. Connect from another system. Verify reconnection after closing tabs or browsers. Additional cases cover missing passwords — the console prompts — and the no-auth variant. Community members can poke at the feature across a full release cycle before it expands. That deliberate pace reduces surprises.
Phoronix covered the proposal hours after it surfaced. Michael Larabel’s piece on July 23, 2026, highlighted the tech-preview status and FESCo approval requirement. It pointed back to the wiki for full planning and noted benefits across all Atomic Desktop images. Read the Phoronix report here. The article also referenced prior Anaconda WebUI progress reported by the same outlet in 2025.
Feedback on the discussion thread at Fedora’s forum raised useful ideas. mDNS discovery could advertise the installer as fedora-installer.local. That would help users find headless machines without hunting DHCP assignments. The suggestion sits outside this change’s scope but aligns with broader modernization efforts. A minimal network-only boot ISO also drew interest. Such a variant would default to remote mode and avoid shipping a local browser. Those enhancements may arrive later.
The proposal sits scoped tightly. Changes live in the anaconda and anaconda-webui packages. No modifications to image building pipelines. No impact on upgrades or existing configurations. If implementation lags, the feature simply remains in its current development state. Normal GTK-based or local installs continue untouched. Contingency proves simple because the code activates only on explicit request.
Longer term, this work benefits more than Atomic Desktops. Any future boot image that adopts the WebUI — Fedora Server remains on GTK for now — would inherit remote support automatically. The installer team maintains anaconda-webui with a dependency on the Cockpit project. No blockers appear in the dependencies section. An epic ticket tracks the broader remote installation initiative.
Release notes summarize the addition cleanly. Fedora 45 introduces secure remote installation support for Atomic Desktop images. Add the boot options. Connect via browser. The feature stays opt-in and labeled tech preview. Installations that skip the parameter see zero difference. Clean separation preserves stability.
Industry observers note the timing. Fedora has pushed Atomic variants as a forward-looking choice for desktop users who want immutable systems, easy rollbacks, and container-focused workflows. Silverblue, Kinoite, and their siblings already ship with OSTree, Flatpak, and toolbox. Making installation less painful removes one friction point. Especially for users on non-traditional hardware or those managing fleets of devices.
Recent coverage stayed light. A story on Mallory.ai from two days ago recapped the kernel parameter, HTTPS transport, and PIN authentication without adding new technical depth. Mallory’s summary appears here. No major new developments surfaced on X in the past week beyond Phoronix sharing its own article. The conversation remains centered inside Fedora’s own channels.
Yet the implications stretch. System administrators who deploy Fedora in virtual machines or bare-metal servers could script initial boots with the parameter and manage setup from a central console. Developers testing on varied client devices gain flexibility. Even home users uncomfortable with command-line boot edits might appreciate the browser experience once they try it. The responsive design and copy-paste capability lower the barrier.
Critics could argue self-signed certificates still produce browser warnings. Users must accept them. Future iterations might explore better discovery or certificate trust mechanisms. Pin management could evolve. Those details fall into the community testing phase the proposal explicitly invites. One release cycle of real-world feedback should surface the rough edges.
So the proposal stands as measured progress. It builds directly on years of Anaconda WebUI investment. It addresses real pain points with ARM hardware and remote scenarios. And it does so without destabilizing the familiar installation paths millions already use. If FESCo approves the change in coming weeks, Fedora 45 will ship with this capability in tech preview. Administrators and tinkerers will gain a new tool. One that feels modern. One that works from almost any device with a browser. Expect hands-on experimentation once the first rawhide builds include the updated packages.
WebProNews is an iEntry Publication