Unity's licensing system is disrupted by recent OpenSSL updates that deprecated SHA-1 signatures, which Unity Hub uses for license verification. Named User Licensing now uses SHA-256 for Personal, Industry, and Enterprise licenses, but legacy serial-activated licenses still rely on SHA-1. To fix this, run Unity Hub with the environment variable OPENSSL_ENABLE_SHA1_SIGNATURES=1. Unity officially supports only Ubuntu on Linux, not Fedora. ✨️
Cause:
Unity’s licensing system has been impacted by recent updates to OpenSSL and system security policies. Specifically, modern OpenSSL versions now deprecate SHA-1 signatures in favor of the SHA-256 standard. Unity Hub, which uses SHA-1 signatures for license verification, is incompatible with newer OpenSSL standards. As a result, license files using SHA-1 signatures cannot be parsed, preventing license activation and disrupting the licensing process.
Current Status: Named User Licensing (NUL) has transitioned to SHA-256 for:
- Unity Personal licenses
- Unity Industry licenses
- Unity Enterprise licenses
This issue applies only to serial-activated (legacy ULF) licenses.
Resolution:
To resolve the issue, run Unity Hub with an environment variable that enables SHA-1 signatures. Follow these steps:
- Make sure you're using the latest Unity Hub version.
- Sign in with your Unity account.
- Open a terminal.
- Run the following command:
OPENSSL_ENABLE_SHA1_SIGNATURES=1 unityhub
This command sets the environment variable OPENSSL_ENABLE_SHA1_SIGNATURES to 1, allowing the application to accept SHA-1 signatures.
If you continue to experience issues, ensure that the license file `/home/username/.config/unity3d/Unity/licenses/UnityEntitlementLicense.xml` exists, has the correct permissions, and is owned by the correct user.
Due to some compatibility issues, Unity does not officially support the Fedora distribution. The only Linux operating system that Unity supports is Ubuntu.
For more information, visit the resources below: