public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] glibc: pt_chown setuid going away by default
Date: Wed, 10 Apr 2013 15:32:40 -0400	[thread overview]
Message-ID: <201304101532.41246.vapier@gentoo.org> (raw)
In-Reply-To: <CAGfcS_kEU20FDycfp+pfzE7+wET3_UvdJ2=LW1PgG5ZorTnbjQ@mail.gmail.com>

[-- Attachment #1: Type: Text/Plain, Size: 1045 bytes --]

On Wednesday 10 April 2013 14:56:26 Rich Freeman wrote:
> On Wed, Apr 10, 2013 at 1:15 AM, Mike Frysinger <vapier@gentoo.org> wrote:
> > tl;dr: make sure your /dev/pts is mounted correctly w/gid=5 or bad things
> > will happen and it's (probably) all your fault
> 
> So, who is this directed to?

any dev who maintains systems that handle initial mounting, or knows of random 
edge cases in the tree that might run into this.  i can't exactly grep our 
entire code base looking for devpts mounters.

> If this is to anybody who uses Gentoo,
> then at best this should be a place to hash out the contents of the
> news item.  We don't expect Gentoo users to read -dev.

users will be informed of the problem when the ebuild fails and then can 
trivially resolve it at that point.  this should impact very few (if any) 
users, so i don't think a news item makes sense.

> Certainly the
> maintainers of anything that mounts /dev/pts
> (OpenRC/SystemD/baselayout?) should take heed.

the maintainers are reading -dev
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-04-10 19:31 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-10  5:15 [gentoo-dev] glibc: pt_chown setuid going away by default Mike Frysinger
2013-04-10 16:26 ` "Paweł Hajdan, Jr."
2013-04-10 18:56 ` Rich Freeman
2013-04-10 19:32   ` Mike Frysinger [this message]
2013-04-11  2:27     ` [gentoo-dev] " Duncan
2013-04-11 15:43     ` [gentoo-dev] " James Cloos
2013-04-11 16:49       ` Mike Frysinger
2013-04-12  2:19         ` [gentoo-dev] " Duncan
2013-04-12 20:05           ` Mike Frysinger
2013-04-12 19:41         ` [gentoo-dev] " James Cloos
2013-04-12 20:08           ` Mike Frysinger
2013-04-13 17:06             ` Jeroen Roovers
2013-04-14 23:02               ` James Cloos
2013-04-17 18:35               ` Mike Frysinger
2013-04-17 18:36                 ` Rich Freeman
2013-04-17 20:43                   ` [gentoo-dev] " Duncan
2013-04-20  6:55                 ` [gentoo-dev] " Sergei Trofimovich
2013-04-12  6:50 ` Maxim Kammerer
2013-04-12 16:22   ` Mike Frysinger
2013-04-12 17:20     ` Maxim Kammerer
2013-04-12 18:54       ` Mike Gilbert
2013-04-12 19:56       ` Mike Frysinger

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=201304101532.41246.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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
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