⚠️⚠️⚠️ Important: Update ICP License File for Authenticode Signing (before 26 May 2026) ⚠️⚠️⚠️
ISL Conference Proxy (ICP) now supports HSM-compliant remote Authenticode signing to meet updated industry requirements for code signing certificates.
Legacy (non-HSM-compliant) Authenticode configurations included in older license files will expire after 26 May 2026.
To ensure continued signing of Windows executables and avoid SmartScreen warnings, administrators must:
- Generate a new ICP license file from their ISL Online account.
- Upload the new license file to their ICP server.
For detailed instructions, please refer to the Update ISL Conference Proxy License manual.
🚀 New Features
Hardware Security Module compliant Authenticode
Due to changes in CA/Browser Forum code signing baseline requirements, support for HSM-compliant remote Authenticode was added to ISL Conference Proxy. See https://cabforum.org/working-groups/code-signing/requirements/ section 6.2.7 Private key storage on cryptographic module.
Remote Authenticode is enabled when an encrypted Base64 configuration blob is provided either in the license field “Microsoft Authenticode” or “Microsoft Authenticode v2”, or in the setting “Use authenticode packed parameters (BASE64)”.
For most deployments, no additional configuration is required. Environments operating in restricted networks may use an HTTP proxy or controlled network forwarding to allow communication with the remote signing service. Remote signing service is available at https://updates.islonline.com.
New HSM-compliant Authenticode configuration will be available in the new license files. Legacy (non-HSM-compliant) Authenticode configuration present in the old license files will expire after 26 May 2026.
2FA Passkey Support
Support for general Passkeys (platform and cross-platform via USB, Bluetooth, or NFC) as a 2FA method has been added to ICP login.
A new Passkey management dashboard is available at:
Security → 2-Step Verification → Passkey
The dashboard includes the following features:
- Create new passkey
The passkey registration flow has been redesigned into a modal interface, where the user selects the type of Passkey to create and provides its description.
Passkeys can now be registered using:- Platform authenticators (e.g. Windows Hello, browser password manager extensions, etc.)
- Cross-platform authenticators (e.g. security keys or mobile devices)
- List passkeys
A newwebapi2 security/login/tfa/passkey/list/1method is used to list a user’s registered passkeys. - Edit passkey
Passkey descriptions can be updated using the existingwebapi2 security/login/tfa/u2f/description/update/1method. - Set as default 2FA method
Passkeys can be set as the default 2FA login method using the existingwebapi2 security/login/tfa/method/default/set/1method. - Remove passkey
Passkeys can be deleted using the existingwebapi2 security/login/tfa/u2f/remove/1method.
As before, removing the last passkey is rejected if the user does not have an alternative 2FA login method configured. In this case, the user is prompted to disable 2FA before removing the final passkey.
To ensure compatibility, when a native application does not support Passkeys directly, users can use the “Log in with browser” option to complete 2FA authentication in their browser. This behavior is controlled by the new permission:
/conf → Security → “Allow ‘Log in with browser’ in native applications”
The browser login option is offered only when Passkeys are configured but not supported by the client.
Migrate security key authentication from U2F to WebAuthn
In previous versions, using the legacy U2F authentication standard as a 2FA method could fail in modern browsers due to deprecated U2F support.
Security key authentication has been migrated from the U2F API to the WebAuthn standard, ensuring compatibility with current browsers.
Existing security keys registered using U2F remain supported, and new registrations use WebAuthn when supported by the browser.
Increased password hashing strength with automatic upgrade on login
The default number of islhash1 hashing rounds has been increased from 10,000 to 210,000 to align with modern security recommendations.
In addition, existing user password hashes are now automatically upgraded upon successful login when stronger hashing parameters are available.
If the configured hashing scheme, number of rounds, or salt size exceeds the stored values, the password hash is transparently re-generated using the stronger settings. Password storage strength is only increased and never reduced.
OpenSSL was updated to 3.0.19.
OpenSSL has been upgraded to version 3.0.19.
Upgrade Go to version 1.24.13
Go has been upgraded to version 1.24.13.
Update to libxslt 1.1.45
libxslt has been upgraded to version 1.1.45.
🐞 Bug Fixes
macOS application icons issue
In previous versions, customized macOS application icons were not displayed correctly in Finder, Dock, and macOS permission settings (such as Accessibility and Screen & System Audio Recording).
This occurred because the image tool generated macOS icons only in PNG format, which caused compatibility issues with certain icon sizes.
The image tool has been updated to generate smaller macOS icon sizes in RGB + mask format where required. Customized icons now display correctly across macOS system interfaces.
Miniplayer touch movement issue
In previous versions, moving the miniplayer window using touch input was either not possible or resulted in very jittery movement.
The coordinate handling logic has been redesigned to ensure consistent behavior between mouse and touch input. The miniplayer can now be moved smoothly using touch gestures.
To improve usability on touch devices:
- The context menu is suppressed during drag operations to prevent it from appearing after a long press.
- Default touch gestures (such as page panning) are disabled on the control bar while dragging.
Meeting window remaining open after logout
In previous versions, the (WebView) meeting window inside the ISL Light application could remain open after the user logged out. The window closing logic has been improved, and the meeting window now closes properly on logout without requiring user intervention.
Audio issues when participants join or leave a meeting
In previous versions, users sometimes could not hear audio streams that were already active before they joined the meeting.
This issue was caused by upstream encoding parameters being re-evaluated when participants joined or left the meeting. The upstream behavior has been stabilized, and audio streams should now remain consistent when participants enter or leave the meeting.
Camera and microphone selector stuck in “Enumerating devices” state
In previous versions, the camera and microphone selector on the create meeting page could remain stuck in the “Enumerating devices…” state if media devices were unavailable or access was blocked.
This was caused by an error during device detection that prevented proper error handling. The issue has been resolved, and device selection now behaves correctly.
Spotlight camera stream resizing issue
In previous versions, the spotlight camera stream could be incorrectly resized and appear off screen. This issue has been resolved.
Other fixes and improvements
Bug fixes, security updates, missing translations, and other general improvements.









