You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Version 1.5.10 of Spring boot prevents the app from starting as a service when using launch.script because $run_user does not have the permissions to write in log_file at startup.
Since version 1.5.10, the ownership of LOG_FILENAME is not transferred to the application user.
We understand that those measures were required by CVE-2018-1196 , but the transfer of ownership should be done when the log file is created by the launch script.
The text was updated successfully, but these errors were encountered:
Version 1.5.10 of Spring boot prevents the app from starting as a service when using launch.script because
$run_user
does not have the permissions to write in log_file at startup.This has to do with #11397
The removal of
chown "$run_user" "$log_file"
and the fact that the log file is created with root rights in
check_permissions()
causes the app to fail to start.
Content below has been redacted to protect sensitive information.
Content of application installation dir :
in myapp.conf (extract)
Example starting application service as root :
Content of LOG_FOLDER
Please note that
myapp-stdout-2018-02-07-11-54-03.log
is owned by root and not writable by the application user (myuser).When
LOG_FILENAME
does not exist, it is created by root in the launch script (check_permission function):touch "$log_file" &> /dev/null || { echoRed "Operation not permitted (cannot access log file)"; return 4; }
Since version 1.5.10, the ownership of
LOG_FILENAME
is not transferred to the application user.We understand that those measures were required by CVE-2018-1196 , but the transfer of ownership should be done when the log file is created by the launch script.
The text was updated successfully, but these errors were encountered: