public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alon Bar-Lev <alon.barlev@gmail.com>
To: David Wagner <daw@cs.berkeley.edu>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Question] LinuxThreads, setuid - Is there user mode hook?
Date: Sat, 24 Dec 2005 18:18:00 +0200	[thread overview]
Message-ID: <43AD74B8.3040006@gmail.com> (raw)
In-Reply-To: <200512231927.jBNJR2uG019083@taverner.CS.Berkeley.EDU>

David Wagner wrote:
> Sorry, I don't know how to tell.  Perhaps you can document your
> library as 'not to be used with setuid/setgid programs'?  It seems
> surprising that a library would create multiple threads without warning
> the programmer that such a thing could happen (behind their back).

Hello,

Not every standard plug-in interface provides this ability. 
So I must use threads behind their back... And I need to 
deal with this last edge condition of the setuid.

Best Regards,
Alon Bar-Lev.

       reply	other threads:[~2005-12-24 16:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200512231927.jBNJR2uG019083@taverner.CS.Berkeley.EDU>
2005-12-24 16:18 ` Alon Bar-Lev [this message]
     [not found] <5mRSA-6ss-15@gated-at.bofh.it>
     [not found] ` <5n1S5-9P-21@gated-at.bofh.it>
     [not found]   ` <5n1S5-9P-19@gated-at.bofh.it>
     [not found]     ` <5nt1F-5aZ-1@gated-at.bofh.it>
2005-12-27  2:33       ` [Question] LinuxThreads, setuid - Is there user mode hook? Robert Hancock
     [not found] <200512222312.jBMNCj96018554@taverner.CS.Berkeley.EDU>
2005-12-23  9:51 ` Alon Bar-Lev
2005-12-23 19:08   ` Lee Revell
2005-12-23 20:21     ` Daniel Jacobowitz
2005-12-23 20:36       ` Lee Revell
2005-12-23 20:33         ` Daniel Jacobowitz
2005-12-24 16:16           ` Alon Bar-Lev
2005-12-25  1:31           ` Luke-Jr
2005-12-25  8:05             ` Alon Bar-Lev
2005-12-22 15:47 Alon Bar-Lev

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=43AD74B8.3040006@gmail.com \
    --to=alon.barlev@gmail.com \
    --cc=daw@cs.berkeley.edu \
    --cc=linux-kernel@vger.kernel.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