[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Hurdish applications for persistence
From: |
Alfred M\. Szmidt |
Subject: |
Re: Hurdish applications for persistence |
Date: |
Thu, 13 Oct 2005 15:57:35 +0200 |
Because we want POSIX, of course. However, in this case I would
suggest a different solution: Provide chroot, but let it fail
unless an environment variable or something is set
(I_KNOW_CHROOT_IS_NOT_SECURE_ON_THIS_PLATFORM = or so). That way,
it cannot be used by accident, but POSIX programs still wor= k.
I think you mean POSIX_ME_HARDER...
- Re: Chroot and "..", (continued)
- Re: Chroot and "..", Alfred M\. Szmidt, 2005/10/13
- Re: Chroot and "..", Jonathan S. Shapiro, 2005/10/13
- Re: Chroot and "..", Espen Skoglund, 2005/10/13
- Re: Chroot and "..", Jonathan S. Shapiro, 2005/10/13
- Re: Chroot and "..", Alfred M\. Szmidt, 2005/10/13
- Re: Hurdish applications for persistence, Bas Wijnen, 2005/10/13
- Re: Hurdish applications for persistence,
Alfred M\. Szmidt <=
- Re: Hurdish applications for persistence, Jonathan S. Shapiro, 2005/10/13
- Re: Hurdish applications for persistence, Bas Wijnen, 2005/10/14
- Re: Hurdish applications for persistence, Marcus Brinkmann, 2005/10/14
- Re: Hurdish applications for persistence, Jonathan S. Shapiro, 2005/10/14
- Re: Hurdish applications for persistence, Alfred M\. Szmidt, 2005/10/13
- Re: Hurdish applications for persistence, Jonathan S. Shapiro, 2005/10/12
- Re: Hurdish applications for persistence, Alfred M\. Szmidt, 2005/10/13
Re: Hurdish applications for persistence, Marcus Brinkmann, 2005/10/12