Search Issue Tracker
Active
Votes
29
Found in [Package]
3.10.0-beta.1
Issue ID
HUBX-1212
Regression
No
[Linux] Can't activate a license when using distributions which have deprecated SHA-1
Reproduction steps:
1. Install Unity Hub package following the steps from https://docs.unity3d.com/hub/manual/InstallHub.html
2. In Unity Hub, sign in to your account
3. Assign a free license or activate paid one
Expected results: A license is added to the Unity Hub and is visible in the list
Actual results: License is not added to the Unity Hub and is not visible in the list
Reproduced with: 3.9.1, 3.10.0-beta.1
Reproduced on: RHEL 9, Fedora 41
Not reproduced on: Windows 10, Ubuntu 22.04, Ubuntu 24.04, Ubuntu 24.10
Note: This is due to the Licensing client still relying on SHA-1 hashing, while it is deprecated, and will eventually be removed from all major distributions
Comments (9)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Clousck
Nov 09, 2025 20:18
I ran into the same issue on Fedora 43. The problem is indeed caused by the new crypto policies deprecating SHA-1, which breaks Unity Hub’s license activation process.
The fix for me was to switch the system’s crypto policy to LEGACY, which re-enables older algorithms (including SHA-1).
sudo update-crypto-policies --set LEGACY
sudo reboot
After rebooting, Unity Hub was able to activate the license normally.
Sindre-Skaare
Jan 08, 2025 00:19
Just ran into this as well after updating to Fedora 41.
The workaround suggested by Flagrama and BPS_86 solved the issue. Thanks a lot! You are lifesavers.
But the underlying issue is still needs to be fixed. As this took quite a bit of googling to find.
thelosev
Dec 16, 2024 13:22
+1 waiting for the issue to be resolved
Unity Hub 3.10.0 (e032492)
Switching crypto-policies doesn't work for me at all. So I can't use my Linux machine at all for Unity dev
BPS_86
Nov 04, 2024 18:54
edit typo: `update-crypto-policies --set DEFAULT:SHA1` and `update-crypto-policies --set DEFAULT` is the correct one
BPS_86
Nov 04, 2024 18:51
@FLAGRAMA don't use that if you only need it for unityhub, use `update-crypto-policies --set default:SHA1` instead.
If you don't mind the hassle, you can use `update-crypto-policies --set default:SHA1`, open unityhub, once opened type `update-crypto-policies --set default` again to return it to normal. This is for safety reason.
kik1n01
Nov 04, 2024 15:30
I installed Unity inside a Distrobox, How can I enable this: `sudo: update-crypto-policies: command not found` ?
flagrama
Nov 03, 2024 18:19
On Fedora specifically you can workaround this using the old crypto policy profile for Fedora 41 using `update-crypto-policies --set FEDORA40` and rebooting. This should use the old crypto policy that verifies SHA-1 hashes. It'll stick around for several more Fedora releases so there's probably a year or so before SHA-1 verification becomes completely impossible, and it'll probably get reset on any version upgrade, so having this issues fixed sooner rather than later is a must.
Marc_Enaweg
Nov 01, 2024 13:14
Complete showstopper as I am not able to work on any projects anymore. Any known workarounds till this is fixed?
BPS_86
Oct 30, 2024 22:43
Hope this will be fixed asap,