public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Ross Burton <Ross.Burton@arm.com>
To: "rs@ti.com" <rs@ti.com>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
	"mathieu.dubois-briand@bootlin.com"
	<mathieu.dubois-briand@bootlin.com>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [oe-core][PATCH] libx11: create tmpfile dir for x11 domain socket
Date: Mon, 6 Oct 2025 10:38:12 +0000	[thread overview]
Message-ID: <CE558C16-AD4F-401B-9734-E57067101F56@arm.com> (raw)
In-Reply-To: <20251002003034.344992-1-rs@ti.com>

On 2 Oct 2025, at 01:30, rs@ti.com wrote:
> 
> From: Randolph Sapp <rs@ti.com>
> 
> Register a volatile directory entry for the x11 domain socket when not
> using systemd. This will make sure the directory is always created with
> the correct permissions. Systemd already provides their own tmpfile.d
> entry for the same behavior.
> 
> Currently some x11 related applications will create this directory if it
> doesn't already exist, but this is not true for everything. In addition,
> if the application in question isn't started as root, it's possible this
> directory can be owned by a non-root user. This isn't an issue by
> itself, but it can potentially lead to problems in a multi-user
> environment.

Feel like this should be in xserver (as the xserver is the one creating the sockets), not libx11.

Ross

  reply	other threads:[~2025-10-06 10:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-02  0:30 [oe-core][PATCH] libx11: create tmpfile dir for x11 domain socket rs
2025-10-06 10:38 ` Ross Burton [this message]
2025-10-06 17:21   ` Randolph Sapp

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CE558C16-AD4F-401B-9734-E57067101F56@arm.com \
    --to=ross.burton@arm.com \
    --cc=mathieu.dubois-briand@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=rs@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox