Opened 3 years ago
Closed 3 years ago
#2491 closed defect (fixed)
rasdaman logs should not be world-readable
| Reported by: | Dimitar Misev | Owned by: | Bang Pham Huu |
|---|---|---|---|
| Priority: | critical | Milestone: | 10.0 |
| Component: | rasserver | Version: | 9.8 |
| Keywords: | Cc: | Peter Baumann | |
| Complexity: | Medium |
Description
The rasdaman logs should be changed to be with -rw-rw—— permissions, currently they are -rw-rw-r— (world readable).
Change History (5)
comment:1 by , 3 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
comment:2 by , 3 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
comment:3 by , 3 years ago
| Owner: | changed from to |
|---|---|
| Status: | reopened → assigned |
comment:4 by , 3 years ago
| Priority: | major → critical |
|---|
comment:5 by , 3 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
It seems tricky to change the permissions of petascope.log from petascope with log4j. The best way is to change the permissions of the /opt/rasdaman/log dir to 660 instead; the tomcat log dir is already like this. I did this in start_rasdaman.sh and the installer.
Note:
See TracTickets
for help on using tickets.
this should also be the case for petascope.log and secore.log