MIME-Version: 1.0
References: <22948c2fba2f4882ac4646501fd6ef3f@tower-net.de> <cf311040-21f2-ad8b-4b9c-363f7ad0c9f5@jirutka.cz>
In-Reply-To: <cf311040-21f2-ad8b-4b9c-363f7ad0c9f5@jirutka.cz>
From: Konstantin Kulikov <k.kulikov2@gmail.com>
Date: Sun, 19 Jun 2022 21:50:17 +0300
Message-ID: <CAD+eXGRn8OsRHiKf9De6KVknh8DG6d4dX=hU4kQF0QSSOmZDQQ@mail.gmail.com>
Subject: Re: Security problem in how you manage users in package installations
To: Jakub Jirutka <jakub@jirutka.cz>
Cc: Markus Kolb <alpinelinux+develml@tower-net.de>, 
	Alpine Linux devel ML <~alpine/devel@lists.alpinelinux.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

>Note that this will most like break container installations, which do no
>run services. So you cannot rely on checkpath in an init script to
>created required directories.

Do people actually use alpine in this way?
That would be really surprising to me.
And I have heard no complaints about grafana for example.

>I don=E2=80=99t know how do you define proper logging implementation, but =
maybe you don=E2=80=99t know about `output_log` and `error_log` parameters.=
 You can use it to =E2=80=9Credirect=E2=80=9D stdout/stderr to syslog using=
 logger(1) command. See kresd.initd [1] for example.

If only error_logger worked with supervise-daemon.
Even then it does work enough for my small installation, but it is far
from ideal - for example everybody has write access to /dev/log or if
logger is killed service will stall or silently drop logs.
Configuration UI is also bad - you should be able to just set where
logs go right in conf.d.
And no error_log is not the answer, as it requires logfiles to be
owned by service and cannot rotate logs at all.