ALT Linux Team development discussions
 help / color / mirror / Atom feed
From: "Dmitry V. Levin" <ldv@altlinux.org>
To: ALT Devel discussion list <devel@lists.altlinux.org>
Subject: Re: [devel] /dev/shm
Date: Wed, 28 Aug 2019 16:54:43 +0300
Message-ID: <20190828135443.GC27391@altlinux.org> (raw)
In-Reply-To: <20190828090428.GA23631@altlinux.org>

[-- Attachment #1: Type: text/plain, Size: 1288 bytes --]

On Wed, Aug 28, 2019 at 12:04:28PM +0300, Dmitry V. Levin wrote:
> On Wed, Aug 28, 2019 at 11:27:39AM +0300, Levin Stanislav wrote:
> > Здравствуйте!
> > 
> > Вчерашняя пересборка показала вероятное изменение на сборочных машинах
> > x86_64 и i586,
> > 
> > а именно возможность обращения "на запись" пользователю "builder" к
> > "/dev/shm"
> > 
> > ( без указания в сборочных зависимостях "/dev/shm" ).
> > 
> > Для x86_64 и i586:
> > 
> > + id
> > uid=523(builder) gid=523(builder) groups=523(builder)
> > + ls -ld /dev/shm
> > drwxr-xr-x 2 root root 40 Aug 27 19:02 /dev/shm
> > 
> > Для ppc64le и aarch64:
> > 
> > + id
> > uid=523(builder) gid=523(builder) groups=523(builder)
> > + ls -ld /dev/shm
> > drwxrwxrwt 2 caller rooter 40 Aug 27 19:01 /dev/shm
> > 
> > При добавлении к BR "/dev/shm" ожидания оправдываются:
> > 
> > + id
> > uid=517(builder) gid=517(builder) groups=517(builder)
> > + ls -ld /dev/shm
> > drwxrwxrwt 2 root root 40 Aug 28 07:00 /dev/shm
> 
> Да, всё это так.

С другой стороны, /dev/shm до сих пор был фактически доступен по
умолчанию, поскольку создавался hasher'ом автоматически с правами 01777,
начиная с версии 1.3.23 (т.е.уже более 7 лет).

Видимо, убирать /dev/shm сейчас будет уже неправильно.


-- 
ldv

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

  parent reply	other threads:[~2019-08-28 13:54 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-28  8:27 ` [devel] Fwd: [cyber] I: Sisyphus-20190827 x86_64 beehive_status: +34 -5 (105) Levin Stanislav
2019-08-28  9:04   ` [devel] /dev/shm Dmitry V. Levin
2019-08-28  9:55     ` Dmitry V. Levin
2019-08-28  9:58       ` Anton Farygin
2019-08-28 10:03       ` Валерий Иноземцев
2019-08-28 10:13         ` Dmitry V. Levin
2019-08-28 10:57           ` Dmitry V. Levin
2019-08-29  0:56             ` Alexey Shabalin
2019-08-28 13:54     ` Dmitry V. Levin [this message]
2019-08-28 14:33       ` Alexey Gladkov
2019-08-28 15:02         ` Dmitry V. Levin
2019-08-28 15:11           ` Alexey Gladkov
2019-08-28 15:23             ` Dmitry V. Levin
2019-08-28 18:08               ` Alexey Gladkov
2019-08-28 18:11                 ` Anton Farygin
2019-08-28 18:24                   ` Dmitry V. Levin
2019-08-28 18:45                     ` Anton Farygin
2019-08-28 18:50                       ` Anton Farygin
2019-08-28 18:59                         ` Dmitry V. Levin
2019-08-29 21:08                           ` Dmitry V. Levin
2019-08-28 18:15                 ` Dmitry V. Levin
2019-08-28 19:50                   ` Alexey Gladkov
2019-08-28 20:53                     ` Dmitry V. Levin
2019-08-28 21:46                       ` Alexey Gladkov
2019-08-28 22:52                         ` Dmitry V. Levin
2019-08-29 13:58                           ` Andrey Savchenko
2019-08-29 19:24                             ` Dmitry V. Levin
2019-08-29 19:36                               ` Anton Farygin
2019-08-29 23:39                         ` Leonid Krivoshein
2019-08-30  0:27                           ` Dmitry V. Levin
2019-08-30  4:30                             ` Leonid Krivoshein
2019-08-28 16:31         ` Stanislav Levin

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=20190828135443.GC27391@altlinux.org \
    --to=ldv@altlinux.org \
    --cc=devel@lists.altlinux.org \
    /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

ALT Linux Team development discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/devel/0 devel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 devel devel/ http://lore.altlinux.org/devel \
		devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru
	public-inbox-index devel

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.devel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git