Re: [PATCH] set*uid() must not fail-and-return on OOM/rlimits

Ar Sul, 2006-08-20 am 10:52 +0300, ysgrifennodd Kari Hurtta:
> Perhaps stupid suggestion:
> 
> Should there be new signal for 'failure to drop privileges' ?
> ( perhaps SIGPRIV or is this name free )
> 
> By default signal terminates process.  

Programs are allowed (and now and then do) intentionally let a setuid
fail. A custom selinux or audit rule might be appropriate but that kind
of hackery is not.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: [PATCH] set*uid() must not fail-and-return on OOM/rlimits
  - From: Kari Hurtta <[email protected]>

References:
- [PATCH] set*uid() must not fail-and-return on OOM/rlimits
  - From: Solar Designer <[email protected]>
- Re: [PATCH] set*uid() must not fail-and-return on OOM/rlimits
  - From: Kari Hurtta <[email protected]>

Prev by Date: [PATCH 7/7] CPU controller V1 - (temporary) cpuset interface
Next by Date: Re: 2.6.18-rc4-mm1 - time moving at 3x speed, bisect finished
Previous by thread: Re: [PATCH] set*uid() must not fail-and-return on OOM/rlimits
Next by thread: Re: [PATCH] set*uid() must not fail-and-return on OOM/rlimits
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]