<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[FOG 1.6.0 Officially released!!!]]></title><description><![CDATA[<p dir="auto">FOG 1.6.0 is released. It is on the <code>stable</code> branch and reports version <code>1.6.0</code>.</p>
<p dir="auto">This is the first release of the 1.6 line, and it replaces 1.5. The upgrade from 1.5 to 1.6 is one-way: it changes the database schema, and there is no down-migration. <strong>Back up before you upgrade.</strong></p>
<p dir="auto">Thank you to everyone who tested the 21 release candidates. Thank you also to everyone who reported a problem, on the forums or on GitHub, and to everyone who sent a pull request. Each report and each fix helped make 1.6.0 what it is.</p>
<p dir="auto"><strong>Highlights</strong></p>
<ul>
<li><strong>Role-based access control is part of core.</strong> Roles and their permissions are built in. You no longer install a plugin before permissions exist.</li>
<li><strong>Sites are part of core.</strong> Multi-site scoping is built in. The upgrade moves the <code>site</code> plugin’s data into the core <code>sites</code> table.</li>
<li><strong>Groups grant snapins, printers and modules.</strong> A host that joins a group later gets the grant, and a host that leaves loses it.</li>
<li><strong>Mass edit on the host list.</strong> It replaces the group page’s one-time push. Each field has its own No change, Set on all, or Clear on all choice.</li>
<li><strong>LDAP and OIDC sign-in are built-in identity providers.</strong> Directory groups map to FOG roles, so an external user no longer gets full admin by default.</li>
<li><strong>API Bearer tokens.</strong> Create one on a user’s API tab and send it as <code>Authorization: Bearer &lt;token&gt;</code>. Each token has its own label and on/off switch, and you can rotate it without touching your other integrations. FOG stores only a hash and shows the token once. The old <code>fog-api-token</code> plus <code>fog-user-token</code> pair still works, but a Bearer token is simpler to use and to maintain. Use it for new integrations.</li>
<li><strong>An audit trail.</strong> FOG records who changed what, and shows it as an activity view.</li>
<li><strong>A retention policy.</strong> A retention daemon removes log and audit records older than the number of days you set. The default keeps everything.</li>
<li><strong>The database enforces its relationships.</strong> Real foreign keys now cover every core relationship that can carry one. The upgrade cleans up orphan rows first and logs each cleanup.</li>
<li><strong>Plugins are installable artifacts.</strong> A plugin has its own install, update and removal, and it survives a FOG upgrade.</li>
<li><strong>Secure Boot enrollment is a task type.</strong> You schedule and track it like any other task.</li>
</ul>
<p dir="auto"><strong>Plugins removed in 1.6</strong></p>
<p dir="auto">These 1.5 plugins are removed. Do not copy them into a 1.6 server.</p>
<ul>
<li><code>accesscontrol</code>: removed. Core role-based access control does its job. The upgrade removes its registration.</li>
<li><code>site</code>: removed. Core sites do its job. The upgrade copies its data into core and drops its tables only when the row counts match.</li>
<li><code>persistentgroups</code>: removed, with its database trigger. Core group grants do its job. Installing it again would re-create the trigger.</li>
<li><code>fileintegrity</code> and <code>hoststatus</code>: not carried into 1.6. No replacement ships.</li>
</ul>
<p dir="auto">Every 1.5 plugin needs a 1.6 build to load. The 1.6 plugins are in <a href="https://github.com/FOGProject/fog-plugins" target="_blank" rel="noopener noreferrer nofollow ugc">https://github.com/FOGProject/fog-plugins</a> .</p>
<p dir="auto"><strong>FOS 1.6.0 (kernel and init)</strong></p>
<ul>
<li>Linux kernel 6.18.59 (LTS), Buildroot 2026.02.1. FOS verifies TLS when it talks to the server.</li>
<li>x64 and x86 boot an initramfs, not an ext2 initrd. The file names stay <code>init.xz</code> and <code>init_32.xz</code>.
<ul>
<li><strong>Warning: a customized init can no longer be loop-mounted.</strong> Add your files as an overlay cpio appended to <code>init.xz</code>: <a href="https://docs.fogproject.org/en/latest/kb/how-tos/customize-the-fos-init/" target="_blank" rel="noopener noreferrer nofollow ugc">https://docs.fogproject.org/en/latest/kb/how-tos/customize-the-fos-init/</a> . A post-init script needs no rebuild: <a href="https://docs.fogproject.org/en/latest/kb/how-tos/post-init-scripts/" target="_blank" rel="noopener noreferrer nofollow ugc">https://docs.fogproject.org/en/latest/kb/how-tos/post-init-scripts/</a></li>
</ul>
</li>
<li><code>master</code> installs FOS release <code>1.6.0</code>. <code>stable</code> and <code>dev-branch</code> installs download the Latest FOS release.</li>
</ul>
<p dir="auto"><strong>What happens to your branch and update channel</strong></p>
<ul>
<li><code>stable</code> (<code>--channel stable</code>) now carries 1.6.0, then the monthly 1.6.0.N releases.</li>
<li><code>dev-branch</code> (<code>--channel patches</code>) now carries the 1.6 patches.</li>
<li><code>rc-1.6.0</code> (<code>--channel rc</code>) and <code>working-1.6</code> (<code>--channel beta</code>) are retired. Move to <code>--channel stable</code>.</li>
<li>No branch was force-pushed. A 1.5 git checkout reaches 1.6 with an ordinary <code>git pull</code>.</li>
</ul>
<p dir="auto"><strong>Before you upgrade</strong></p>
<ul>
<li><strong>Known issue:</strong> the upgrade from 1.5 fails at the schema update if the database holds multicast sessions (<code>Truncated incorrect INTEGER value: ''</code>). Do not upgrade a 1.5 server until 1.6.0.1 is released.</li>
<li>Back up your database and <code>/opt/fog/.fogsettings</code>.</li>
<li>Read the release notes: <a href="https://github.com/FOGProject/fogproject/blob/stable/docs/release/1.6.0-release-notes.md" target="_blank" rel="noopener noreferrer nofollow ugc">https://github.com/FOGProject/fogproject/blob/stable/docs/release/1.6.0-release-notes.md</a></li>
<li>1.6 removes Display Manager, Directory Cleaner, User Cleanup, Client Updater, Green FOG and the persistentgroups plugin. Their data is dropped.</li>
<li>PHP 7.4 or later is required. Plugins built for 1.5 do not load.</li>
</ul>
<p dir="auto"><strong>Install or update (as root)</strong></p>
<ul>
<li>A 1.5 server installed from git: run <code>bin/updatefog.sh --channel stable</code> from the checkout.</li>
<li>A 1.6 beta or RC server: run <code>bin/updatefog.sh --channel stable</code>.</li>
<li>A new server, or a 1.5 server installed from a tarball:<br />
<code>curl -fsSL https://raw.githubusercontent.com/FOGProject/fogproject/stable/bin/bootstrap.sh | bash -s -- --channel stable</code></li>
</ul>
<p dir="auto">If an upgrade fails, <code>bin/revertfog.sh</code> in the 1.6 checkout restores the pre-upgrade backup. Run it with <code>--list</code>, then <code>--dry-run</code>, first.</p>
<p dir="auto"><strong>1.5 support</strong></p>
<p dir="auto">1.5 is end of life. The last 1.5 release is <code>1.5.10.2534</code>. It gets no further fixes, security fixes included. Every 1.5 tag stays in the repository. Details: <a href="https://github.com/FOGProject/fogproject/blob/stable/docs/release/1.5-support-statement.md" target="_blank" rel="noopener noreferrer nofollow ugc">https://github.com/FOGProject/fogproject/blob/stable/docs/release/1.5-support-statement.md</a></p>
<p dir="auto"><strong>Report problems</strong></p>
<p dir="auto">Open an issue at <a href="https://github.com/FOGProject/fogproject/issues" target="_blank" rel="noopener noreferrer nofollow ugc">https://github.com/FOGProject/fogproject/issues</a>. Include your FOG version, your OS, and the installer log from <code>bin/error_logs/</code>. Report a security problem through “Report a vulnerability” on the same repository, not in a public issue.</p>
]]></description><link>http://forums.fogproject.org/topic/18298/fog-1-6-0-officially-released</link><generator>RSS for Node</generator><lastBuildDate>Mon, 02 Nov 2026 15:41:03 GMT</lastBuildDate><atom:link href="http://forums.fogproject.org/topic/18298.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 02 Nov 2026 13:57:39 GMT</pubDate><ttl>60</ttl></channel></rss>