From: Peter Korsgaard <peter@korsgaard.com>
To: Ben Hutchings via buildroot <buildroot@buildroot.org>
Cc: oss-security@lists.openwall.com, Ben Hutchings <ben.hutchings@mind.be>
Subject: Re: [Buildroot] [PATCH] package/skeleton-init-sysv: Set sticky bit on /dev/shm
Date: Mon, 06 May 2024 23:04:01 +0200 [thread overview]
Message-ID: <87edaey7ni.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20240411152016.1185109-1-ben.hutchings@mind.be> (Ben Hutchings via buildroot's message of "Thu, 11 Apr 2024 17:20:16 +0200")
>>>>> "Ben" == Ben Hutchings via buildroot <buildroot@buildroot.org> writes:
> /dev/shm is a world-writable directory, like /tmp, and should also
> have the sticky bit set. Without this, any user can delete and
> replace another user's files in /dev/shm.
> This bug has been present since /dev/shm was added to the skeleton
> /etc/fstab, but appears to have been fixed for systems using systemd
> by commit 76fc9275f14e "system: separate sysv and systemd parts of the
> skeleton" which went into Buildroot 2017.08.
> Signed-off-by: Ben Hutchings <ben.hutchings@mind.be>
> Fixes: 22fde22e35f98f7830c2f8955465532328348cd1
Committed to 2024.02.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-05-06 21:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-11 15:20 [Buildroot] [PATCH] package/skeleton-init-sysv: Set sticky bit on /dev/shm Ben Hutchings via buildroot
2024-04-11 18:31 ` Yann E. MORIN
[not found] ` <ZhgCNMQXfxPXuqvs@cephalopod>
2024-05-06 10:24 ` [Buildroot] Buildroot: incorrect permissons " Ben Hutchings via buildroot
2024-05-06 18:32 ` Yann E. MORIN
2024-05-07 9:10 ` Peter Korsgaard
2024-05-06 21:04 ` Peter Korsgaard [this message]
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=87edaey7ni.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=ben.hutchings@mind.be \
--cc=buildroot@buildroot.org \
--cc=oss-security@lists.openwall.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.