|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Subject: Re: Here's another glibc env. var.
From: Matthew Kirkwood (weejock
ferret.lmh.ox.ac.uk)Date: Thu May 25 2000 - 06:07:40 CDT
- Next message: Rafael J. Wysocki: "Re: Here's another glibc env. var."
- Previous message: Pavel Kankovsky: "Re: Here's another glibc env. var."
- In reply to: Pavel Kankovsky: "Re: Here's another glibc env. var."
- Next in thread: Chris Evans: "Re: Here's another glibc env. var."
- Next in thread: Rafael J. Wysocki: "Re: Here's another glibc env. var."
- Next in thread: harada
obunsha.co.jp: "Re: Here's another glibc env. var."
- Reply: Matthew Kirkwood: "Re: Here's another glibc env. var."
- Reply: Chris Evans: "Re: Here's another glibc env. var."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, 25 May 2000, Pavel Kankovsky wrote:
> > You're removing needed functionality to get around programming errors.
>
> No. I suggest to reduce functionality to discourage bad design.
> Complex security-hazard-prone code, including (but not limited to)
> user interface stuff, should be separated from code running with
> elevated privileges that should be really small, simple, and paranoid.
What about ping? Should that be split into client/server
portions?
Matthew.
- Next message: Rafael J. Wysocki: "Re: Here's another glibc env. var."
- Previous message: Pavel Kankovsky: "Re: Here's another glibc env. var."
- In reply to: Pavel Kankovsky: "Re: Here's another glibc env. var."
- Next in thread: Chris Evans: "Re: Here's another glibc env. var."
- Next in thread: Rafael J. Wysocki: "Re: Here's another glibc env. var."
- Next in thread: harada
obunsha.co.jp: "Re: Here's another glibc env. var."
- Reply: Matthew Kirkwood: "Re: Here's another glibc env. var."
- Reply: Chris Evans: "Re: Here's another glibc env. var."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]