Bug #3174
closedserver.socket-group and server.socket-user seems not work as expected
Description
Dear colleagues,
server.socket-group
and server.socket-user
don't work as I expect.
My config at /etc/lighttpd/lighttpd.conf
:
server.modules = ( "mod_indexfile", "mod_access", "mod_alias", "mod_redirect", ) server.document-root = "/var/www/html" server.upload-dirs = ( "/var/cache/lighttpd/uploads" ) server.errorlog = "/var/log/lighttpd/error.log" server.pid-file = "/run/lighttpd.pid" server.username = "www-data" server.groupname = "www-data" server.port = 80 # features #https://redmine.lighttpd.net/projects/lighttpd/wiki/Server_feature-flagsDetails server.feature-flags += ("server.h2proto" => "enable") server.feature-flags += ("server.h2c" => "enable") server.feature-flags += ("server.graceful-shutdown-timeout" => 5) #server.feature-flags += ("server.graceful-restart-bg" => "enable") # strict parsing and normalization of URL for consistency and security # https://redmine.lighttpd.net/projects/lighttpd/wiki/Server_http-parseoptsDetails # (might need to explicitly set "url-path-2f-decode" = "disable" # if a specific application is encoding URLs inside url-path) server.http-parseopts = ( "header-strict" => "enable",# default "host-strict" => "enable",# default "host-normalize" => "enable",# default "url-normalize-unreserved"=> "enable",# recommended highly "url-normalize-required" => "enable",# recommended "url-ctrls-reject" => "enable",# recommended "url-path-2f-decode" => "enable",# recommended highly (unless breaks app) #"url-path-2f-reject" => "enable", "url-path-dotseg-remove" => "enable",# recommended highly (unless breaks app) #"url-path-dotseg-reject" => "enable", #"url-query-20-plus" => "enable",# consistency in query string ) index-file.names = ( "index.php", "index.html" ) url.access-deny = ( "~", ".inc" ) static-file.exclude-extensions = ( ".php", ".pl", ".fcgi" ) # default listening port for IPv6 falls back to the IPv4 port include_shell "/usr/share/lighttpd/use-ipv6.pl " + server.port include_shell "/usr/share/lighttpd/create-mime.conf.pl" include "/etc/lighttpd/conf-enabled/*.conf" #server.compat-module-load = "disable" server.modules += ( "mod_dirlisting", "mod_staticfile", ) server.chroot = "/testserver" server.name = "testserver" server.tag = "foo" server.bind = "/var/run/lighty.sock" server.socket-perms = "0770" server.socket-user = "www-data" server.socker-group = "debian-tor"
The socket after every reboot is like this:
srwxrwx--- 1 root root 0 ноя 21 12:07 /var/run/lighty.sock
What I expect:
srwxrwx--- 1 www-data debian-tor 0 ноя 21 12:07 /var/run/lighty.sock
OS: Ubuntu 22.04.1 LTS
Lighttpd: 1.4.63
Maybe I do something wrong? Could you help me with that?
Updated by gstrauss over 1 year ago
- Status changed from New to Invalid
- Priority changed from Normal to Low
- Target version deleted (
1.4.xx)
User questions belong in the Forums.
This is the lighttpd bug tracker for bugs in lighttpd, not user question and not user support.
Most questions, like yours, are not bugs in lighttpd, but rather misconfiguration and failure to read documentation.
There are no such configuration directives in lighttpd, and you also misspelled "server.socker-" (sic)
server.socket-user = "www-data"
server.socker-group = "debian-tor"
Updated by Anonymous over 1 year ago
gstrauss wrote in #note-1:
User questions belong in the Forums.
This is the lighttpd bug tracker for bugs in lighttpd, not user question and not user support.
Most questions, like yours, are not bugs in lighttpd, but rather misconfiguration and failure to read documentation.
There are no such configuration directives in lighttpd, and you also misspelled "server.socker-" (sic)
server.socket-user = "www-data"
server.socker-group = "debian-tor"
I'm sorry, I actually misunderstood this issue in the google search: https://redmine.lighttpd.net/issues/3018.
Also available in: Atom