From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Retrieving per-process environment block?
Date: Wed, 30 Nov 2016 11:06:00 -0000 [thread overview]
Message-ID: <20161130104724.GD14074@calimero.vinschen.de> (raw)
In-Reply-To: <98eb08bf-5012-fe14-b10c-241b427c4366@cs.umass.edu>
[-- Attachment #1: Type: text/plain, Size: 879 bytes --]
On Nov 29 09:28, Eliot Moss wrote:
> On 11/29/2016 8:26 AM, Erik Bray wrote:
> > I could do this, if each process kept a copy of its environment block
> > in shared memory, which would in turn have to be updated every time
> > the process's environment is updated. But I don't know what the
> > impact of that would be performance-wise.
>
> Sorry, no advice getting around this, but a thought about why it may have
> been hard -- it can be a security hole.
Using the mechanism outlined in my mail from 2 minutes ago, there's
no security problem. Opening the signal pipe is only allowed to
same user processes or administrative processes. Other will get a
/proc/$PID/environ content of "<defunct>"
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-11-30 10:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 18:05 Erik Bray
2016-11-17 18:11 ` Corinna Vinschen
2016-11-29 15:28 ` Erik Bray
2016-11-29 16:01 ` cyg Simple
2016-11-30 11:03 ` Corinna Vinschen
2016-11-29 16:35 ` Eliot Moss
2016-11-29 17:42 ` Erik Bray
2016-11-29 18:02 ` Andrey Repin
2016-11-30 4:28 ` Herbert Stocker
2016-11-30 10:43 ` Eliot Moss
2016-11-30 10:47 ` Peter Rosin
2016-11-30 10:47 ` Erik Bray
2016-11-30 12:29 ` Corinna Vinschen
2016-11-30 12:36 ` Corinna Vinschen
2016-11-30 11:36 ` Corinna Vinschen
2016-11-30 11:06 ` Corinna Vinschen [this message]
2016-11-30 10:48 ` Corinna Vinschen
2016-11-30 14:49 ` Erik Bray
2016-11-30 15:04 ` Corinna Vinschen
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=20161130104724.GD14074@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).