recommend making config world readable rather than setting owner
There is no secret material that needs to be unreadable except to the daemon, but if there were, the current instructions never recommended setting a locked down mode. The daemon doesn't need write access either. Recommending chown rather than making the config world readable as is typical for bog standard system configs, is confusing and inconsistent with e.g. the in house AUR packaging. It also might be erroneously interpreted as a requirement, which is challenging for packaging systems that don't support distributing files/directories owned by non-root users.
This commit is contained in:

committed by
Kenny Levinsen

parent
e069f5ac4d
commit
f89d80a2f6
@@ -46,7 +46,7 @@ cp config.toml /etc/greetd/config.toml
|
|||||||
|
|
||||||
# Create the greeter user
|
# Create the greeter user
|
||||||
sudo useradd -M -G video greeter
|
sudo useradd -M -G video greeter
|
||||||
sudo chown -R greeter:greeter /etc/greetd/
|
sudo chmod -R go+r /etc/greetd/
|
||||||
|
|
||||||
# Look in the configuration file `/etc/greetd/config.toml` and edit as appropriate.
|
# Look in the configuration file `/etc/greetd/config.toml` and edit as appropriate.
|
||||||
# When done, enable and start greetd
|
# When done, enable and start greetd
|
||||||
|
Reference in New Issue
Block a user