|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Subject: Re: glibc env. vars. (again)
From: Chris Evans (chris
ferret.lmh.ox.ac.uk)Date: Wed May 24 2000 - 16:15:40 CDT
- Next message: Matthew Kirkwood: "Re: glibc env. vars. (again)"
- Previous message: Alan Cox: "Re: glibc env. vars. (again)"
- In reply to: Matthew Kirkwood: "Re: glibc env. vars. (again)"
- Reply: Chris Evans: "Re: glibc env. vars. (again)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, 24 May 2000, Matthew Kirkwood wrote:
> So basically, it is possible to get any program which uses malloc,
> as most do, to write to fd 2 early on. Triggering it later will be
> harder, as you have to force the app to to a double free, or similar.
Any non-suid program... fd's 0,1,2 are set to /dev/null (I think) if
they're not used, and the program is privileged. This was introduced into
glibc-2.1 AFAIK
Still on the topic of env. vars. - does LD_PROFILE do anything useful??
Chris
- Next message: Matthew Kirkwood: "Re: glibc env. vars. (again)"
- Previous message: Alan Cox: "Re: glibc env. vars. (again)"
- In reply to: Matthew Kirkwood: "Re: glibc env. vars. (again)"
- Reply: Chris Evans: "Re: glibc env. vars. (again)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]