This is the mail archive of the
cygwin@sources.redhat.com
mailing list for the Cygwin project.
Re: Openssh port to cygwin
- To: norbert dot bladt at usa dot net
- Subject: Re: Openssh port to cygwin
- From: Corinna Vinschen <vinschen at cygnus dot com>
- Date: Mon, 10 Jul 2000 14:45:22 +0200
- CC: cygwin at sourceware dot cygnus dot com
- References: <20000710113445.18876.qmail@nwcst313.netaddress.usa.net>
- Reply-To: cygwin <cygwin at sourceware dot cygnus dot com>
norbert.bladt@usa.net wrote:
>
> Hello everyone !
>
> Openssh on NT works very well, unless you are trying to
> use /winnt/system32/cmd instead of /bin/sh or
> unless you use real NT commands from the sh.
>
> In this case, no input / output redirection is possible,
> neither on UNIX nor - once logged in - on NT.
> Using "cygwin-enabled" GNU commands works fine, though.
>
> Now my questions are:
> Is this the intended behaviour ?
> If not what can be the reason or - with other words - do
> just I see this behaviour or is it the same for everybody else ?
>
> We really want to execute NT commands like "net use" or
> "net stop snmp", etc. from remote UNIX or NT host via ssh.
> Is this a bad idea and if yes, why ?
> Are there other WORKING solutions for that which are secure ?
I'm using nt commands via ssh without problems as far as they
are not GUI commands. CLI tools like `net' are working _mostly_
fine. Some commands like `sc' sometimes have dubious problems
with their output.
Try setting the environment variable CYGWIN so that it contains
`tty'. This might help.
Corinna
--
Corinna Vinschen
Cygwin Developer
Cygnus Solutions, a Red Hat company
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com