Search Issue Tracker
Fixed
Fixed in 3.14.0-beta.1
Votes
1
Found in [Package]
3.9.0-beta.1
Issue ID
HUBX-1169
Regression
No
[Linux] Hub installs Unity Licensing Client as owned by root with all permissions
Reproduction steps:
1. Install Unity Hub with the steps listed in https://docs.unity3d.com/hub/manual/InstallHub.html#install-hub-linux
2. Open the terminal and run “find /opt -xdev -type f -uid 0 -perm 777” which will list all files owned by the root user with all permissions
Expected results: The Unity Hub installer does not create files with this permission set for the root user
Actual results: “/opt/unityhub/UnityLicensingClient_V1/Unity.Licensing.Client” is listed as owned by root with 777 permissions
Reproduced with: 3.8.0, 3.9.0-beta.1
Reproduced on: Ubuntu 22.04
Not reproduced on: No other environment tested
Comments (3)
-
csmathilt
Dec 10, 2024 17:58
Sorry for spam posting, but I have removed UnityHub from my environment, so I haven't verified if the LicensingClient needs to have r-x perms for users.
-
csmathilt
Dec 10, 2024 17:31
For any administrators affected, the simplest way to preserve functionality is simply to remove permissions.
find /opt -xdev -type f -uid 0 -perm 777 -exec chmod go-rwx {} \;For those shipping this software, the right way to do so is by creating a service account (perhaps called "unityd" and assigning its configuration files to it.
-
csmathilt
Dec 10, 2024 17:17
This is still the case with 3.10.0
I'm somewhat unsurprised.
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
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
Resolution Note (fix version 3.14.0-beta.1):
The issue was fixed.