This is the mail archive of the
mailing list for the Cygwin project.
Re: michael's openssh for windows
- From: Igor Pechtchanski <pechtcha at cs dot nyu dot edu>
- To: jwaterbrook <jwaterbrook at keyww dot com>
- Cc: cygwin at cygwin dot com
- Date: Mon, 11 Aug 2003 19:58:51 -0400 (EDT)
- Subject: Re: michael's openssh for windows
- Reply-to: cygwin at cygwin dot com
The thread starting at <http://cygwin.com/ml/cygwin/2003-07/msg01379.html>
might be of help.
On Mon, 11 Aug 2003, jwaterbrook wrote:
> I haven't seemed to get very far with this,
> I was hoping someone might be able to point a blind man in the right
> direction :)
> Waterbrook, Johnny wrote:
> > I'd prefer not to start a new thread, but I've been searching for the
> > past few hours with no luck.
> > I needed a fast way to set up sftp on a winXP box, so I did a little
> > google search and found lexa.mckenna.edu/sshwindows/ had a clean and
> > easy way of doing this.
> > I changed the regestry setting "/home" to a different drive, and the
> > passwd file's entry form :/home/USERNAME: to :/home: so when my "auts
> > ex-uncle" wants to login to my sftp server, they can't browse my windows
> > directory structure.
> > However, when my "aunts ex-uncle" realizes he can also ssh into the box,
> > I don't want him running "windows" commands such as cmd, nbtstat, dir
> > etc. I just want to "limit" him to what is available in /bin I guess.
> > Am I going about this wrong? Is there a cygwin/openssh implemenation
> > that "stands alone" from windows so I could set up a sftp server much
> > like a normal ftp server?
> > Thanks in advance,
> > Johnny
|\ _,,,---,,_ firstname.lastname@example.org
ZZZzz /,`.-'`' -. ;-;;,_ email@example.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