All essays
Blog Mayank Sanghvi January 15, 2025 2 min read 1.2K views 445 words

[Linux] Can't activate a license when using distributions which have deprecated SHA-1

[Linux] Can't activate a license when using distributions which have deprecated SHA-1 Package: Hub [user@machinename]$ sudo update-crypto-policies --show [sudo] password for user: DEFAULT [user@machinename]$ ^C [user@machinename]$ Oct 28, 2

#[Linux] Can't activate a license when using distributions which have deprecated SHA-1

Package: Hub

[user@machinename]$ sudo update-crypto-policies --show [sudo] password for user: DEFAULT [user@machinename]$ ^C [user@machinename]$

Oct 28, 2024

Reproduction steps: 1. Install Unity Hub package following the steps from [https://docs.unity3d.com/hub/manual/InstallHub.html|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 (8)

  1. 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.
  2. 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
  3. 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
  4. 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.
  5. kik1n01

    Nov 04, 2024 15:30

    I installed Unity inside a Distrobox, How can I enable this: `sudo: update-crypto-policies: command not found` ?
  6. 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.
  7. 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?
  8. BPS_86

    Oct 30, 2024 22:43

    Hope this will be fixed asap,
M
Mayank Sanghvi
Published January 15, 2025