delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/1997/11/29/02:13:06

From: garbanzo AT hooked DOT net (Alex)
Subject: Re: Simple chroot using chdrive
29 Nov 1997 02:13:06 -0800 :
Message-ID: <Pine.BSF.3.96.971128174339.787A-100000.cygnus.gnu-win32@zippy.dyn.ml.org>
References: <009BDFEC DOT 819A4A40 DOT 29138 AT ifk20 DOT mach DOT uni-karlsruhe DOT de>
Mime-Version: 1.0
To: dahms AT ifk20 DOT mach DOT uni-karlsruhe DOT de
Cc: gnu-win32 AT cygnus DOT com


On Sat, 29 Nov 1997 dahms AT ifk20 DOT mach DOT uni-karlsruhe DOT de wrote:

> Hi Alex, you wrote:
> 
> : While it may be a security issue, or flawed in many respects, this is how
> : Unix works.  If the goal of cygwin.dll is to emulate Unixish functions,
> : chdrive isn't what is being looked for.  Chroot() incidentally can only
> : be used by the super-user.
> 
> I agree with you! I meant to say it would be a security issue if
> half-heartedly implemented under gnuwin32. And I forgot it needs
> 'appropriate privileges', which brings me to the question of how to
> implement suid programs under gnuwin32 savely... Any ideas?

Not on Win95, but I think that it is already done, or shouldn't be too
hard to do on NT.  However using gnuwin32 for multi-user programs is
highly not recommended.

- alex

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019