Hatch Windows installer creates properties files with limited read access
Bug #1860187 reported by
Bill Erickson
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Committed
|
Medium
|
Unassigned |
Bug Description
Hatch 0.3.2
In Windows, the hatch.properties and logging.properties files installed in C:\Program Files\Hatch (x86)\ have strict read permissions allowing only the installing user and admin accounts to read the files. The installer should be modified to create properties files that are readable by all users.
If Hatch cannot read the hatch.properties file, it will fall back to storing data in the $HOME\.evergreen directory for the logged in user instead of the C:\ProgramData\
Changed in evergreen: | |
assignee: | nobody → Kyle Huckins (khuckins) |
Changed in evergreen: | |
assignee: | nobody → Bill Erickson (berick) |
Changed in evergreen: | |
milestone: | none → 3.6.1 |
Changed in evergreen: | |
milestone: | 3.6.1 → none |
tags: | added: signedoff |
To post a comment you must log in.
I've pushed a branch here, making use of AccessControl to ensure the .properties files have Read+Execute permissions granted to users that aren't the installing user or Administration: /git.evergreen- ils.org/ ?p=working/ Hatch.git; a=shortlog; h=refs/ heads/user/ khuckins/ lp1860187- global- read-on- properties
https:/