Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs Date: Fri, 25 Jun 2004 14:32:55 -0400 (EDT) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: "Pierre A. Humblet" cc: cygwin AT cygwin DOT com Subject: Re: Setting up cygwin so other users can run processes on my computer In-Reply-To: <20040625180603.GA969685@Worldnet> Message-ID: References: <20040625180603 DOT GA969685 AT Worldnet> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Scanned-By: MIMEDefang 2.39 On Fri, 25 Jun 2004, Pierre A. Humblet wrote: > On Fri, Jun 25, 2004 at 02:00:43PM -0400, Igor Pechtchanski wrote: > > On Fri, 25 Jun 2004, DePriest, Jason R. wrote: > > > > > Rajiv Chopra wrote: > > > > What I would like to do is enable another colleague to run processes > > > > on my computer. Is it possible to set up Cygwin such that he can > > > > telnet to my machine and run a process? > > > > > > > > Thanks in advance > > > > > > > > Rajiv > > > > > > I would suggest installing openssh from http://www.cygwin.com/setup.exe. > > > > > > After that you can run the ssh-host-config script to install it as a > > > service. > > > > > > After making sure the other guy's user ID is in your /etc/passwd file, > > > you can have him log on your system locally and get to a bash prompt to > > > initialize his environment. Then have him run ssh-user-config to get > > > the ssh stuff for his user account created. > > > > > > After that, he should be able to ssh into your system and do what he > > > needs to do. > > > > > > -Jason > > > > You might also want to mention that the relevant mounts should be system > > mounts, not user ones (i.e., install for "All Users", not "Just Me")... > > Would a generous soul volunteer to add that to ssh-host-config? > At the same time make sure that /etc/passwd and group are readable by the > daemon, or by everybody, and that id -u isn't 400 and id -g not 401 (mkgroup). > Just emit a big WARNING if there is a problem. > THANKS^1000 > > Pierre Just to get this into the archives: ssh-host-config can certainly emit a warning on non-system mounts, but having separate set of user mounts for the SYSTEM user will also work just fine... In fact, that'd make it possible to have a whole different /etc/passwd (and /etc/group) file readable only to SYSTEM (via a user mount). Ugly, but workable... :-( I'm by no means advocating the above setup, but I could think of some situations where it might be useful (and it has come up a few times on this list). Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "I have since come to realize that being between your mentor and his route to the bathroom is a major career booster." -- Patrick Naughton -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/