| Re: [chrony-users] Regarding socket permissions |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] Regarding socket permissions
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Tue, 14 Mar 2023 08:43:28 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1678779817; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=zrFiz3fp3bDgpXgYprEBbUcmpPSDVVN9aJDABEZaJk8=; b=bWmUVOrYLQlhB80Un9Ol47iUPkL3zhyJwEjgei1V/WiG2C1pDa19jOTZFND+Y6ns/wNWOv zZqne6nxopZvnu7/y5CrkbZIVwVdc+5Dot2BD8pfKcoQyUNAY5w7PZPWMGck5tXRspuTle 6FlV4NXp7MiW/QYhVsuunjh8VyzqlU8=
On Tue, Mar 14, 2023 at 09:23:05AM +0100, Morten Nissov wrote:
> I suppose that's it then, the permissions aren't changed therefore access
> will be restricted since it's owned by root. Do you think there's any
> workaround? Or any interest from others to set the sock with the same 666
> permissions, i.e. such that I could PR this?
Adding an option to set world-writable permissions on the socket
doesn't sound like a good idea to me. How does your application get
access to the serial port?
Applications like gpsd and ntp-refclock normally start with root
privileges, open all devices and sockets they will need, and then
switch to an unprivileged user.
--
Miroslav Lichvar
--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.