Changes to Relution Shield, the VPN gateway with access checks by Relution, for each released version.https://hub.relution.io/en/docs/product-info/changelog-addons/shield/2026-11-09T16:59:44+01:00Relution GmbHhttps://hub.relution.io/en/docs/product-info/changelog-addons/shield/#version-26312026-11-04T00:00:00+01:00<div class="mt-4"> <p><strong>Updates</strong></p> <ul> <li>Connections without EAP or XAuth authentication are rejected. The device ID is determined exclusively from the EAP identity and no longer from the IKE identity. The example configurations for iOS and Android Enterprise use EAP and are not affected</li> <li>Device IDs are checked against a fixed format before the access check (4 to 64 characters, letters, digits, <code>-</code> and <code>_</code>); other IDs are rejected</li> <li>New environment variable <code>ACCESS_CHECK_FAIL_OPEN</code> (default <code>true</code>) defines whether devices with a valid certificate are accepted when their status cannot be determined. It replaces <code>RELUTION_SERVER_NOT_REACHABLE_ALLOW_DEVICE</code>; the previous name is still evaluated as long as <code>ACCESS_CHECK_FAIL_OPEN</code> is not set</li> <li>New environment variable <code>DEVICE_COMPLIANCE_DIR</code> for the directory inside the container in which the compliance status is cached (default <code>/opt/strongswan/compliance</code>)</li> <li>Control characters are removed from the peer identities before they are written to the log</li> <li>Security improvements and hardening</li> </ul> </div> <div class="mt-4"> <p><strong>Fixes</strong></p> <ul> <li>A response from the Relution server that cannot be evaluated, such as a proxy error page, is treated like an unreachable server and follows the <code>ACCESS_CHECK_FAIL_OPEN</code> setting</li> <li>If the compliance status cannot be cached, the result returned by the Relution server still applies</li> </ul> </div> <p>Version 26.3.0 was not released on Docker Hub; its changes are included in 26.3.1.</p>https://hub.relution.io/en/docs/product-info/changelog-addons/shield/#version-26202026-09-08T00:00:00+02:00<div class="mt-4"> <p><strong>Updates</strong></p> <ul> <li>The environment variables <code>RELUTION_SERVER_NOT_REACHABLE_ALLOW_DEVICE</code> and <code>DEVICE_STATE_CACHE_DURATION_MINUTES</code> are passed to the access check and take effect as of this version [REL-12795]</li> <li>Update to strongSwan 6.1.0</li> </ul> </div>https://hub.relution.io/en/docs/product-info/changelog-addons/shield/#version-26102026-06-09T00:00:00+02:00<div class="mt-4"> <p><strong>Updates</strong></p> <ul> <li>Update to strongSwan 6.0.7</li> </ul> </div>https://hub.relution.io/en/docs/product-info/changelog-addons/shield/#version-26002026-03-23T00:00:00+01:00<div class="mt-4"> <p><strong>Updates</strong></p> <ul> <li>The version number follows the scheme of the Relution versions</li> <li>Update to strongSwan 6.0.5</li> </ul> </div>https://hub.relution.io/en/docs/product-info/changelog-addons/shield/#version-2032025-12-22T00:00:00+01:00<div class="mt-4"> <p><strong>Updates</strong></p> <ul> <li>Diagnostic tools (<code>binutils</code>) in the image for analyzing crash reports</li> <li>Custom modifications to the strongSwan source code removed; the image uses strongSwan unmodified</li> </ul> </div>https://hub.relution.io/en/docs/product-info/changelog-addons/shield/#version-2022025-11-04T00:00:00+01:00<div class="mt-4"> <p><strong>Updates</strong></p> <ul> <li>Update to strongSwan 6.0.3</li> </ul> </div>https://hub.relution.io/en/docs/product-info/changelog-addons/shield/#version-2012025-07-28T00:00:00+02:00<div class="mt-4"> <p><strong>Updates</strong></p> <ul> <li>Update to strongSwan 6.0.2</li> </ul> </div>https://hub.relution.io/en/docs/product-info/changelog-addons/shield/#version-202025-06-04T00:00:00+02:00<div class="mt-4"> <p><strong>New</strong></p> <ul> <li>Configuration via <code>swanctl.conf</code> with the <code>charon</code> daemon instead of the previous <code>ipsec.conf</code> [REL-7961]</li> <li>Environment variable <code>RELUTION_ACCESS_CHECK_SCOPE</code> for access checks across all organizations (<code>global</code>) [REL-8252]</li> </ul> </div> <div class="mt-4"> <p><strong>Updates</strong></p> <ul> <li>Update to strongSwan 6.0.1 and Ubuntu 24.04 [REL-8251]</li> <li>Consistent names for the environment variables: <code>REST_API_ACCESS_TOKEN</code> is now <code>RELUTION_REST_API_ACCESS_TOKEN</code>, <code>HEALTHCHECK_ID</code> is now <code>RELUTION_HEALTHCHECK_ID</code> [REL-8252]</li> <li>Docker tag <code>2-latest</code> instead of <code>latest</code></li> </ul> </div> <p>The procedure for switching from version 1.x is described in <a href="https://hub.relution.io/en/docs/installation/installation/relution-shield/#update-1-2">Upgrade from 1.x to 2.x →</a>.</p>