ssh password-less cmds to Windows 2003 don't return any output
Larry Hall (Cygwin)
Wed Jun 21 17:50:00 GMT 2006
John McNulty wrote:
> On 21/06/06, Igor Peshansky <email@example.com> wrote:
>> Cygwin ssh (and basically all terminals except the Windows console) use
>> pipes to emulate ttys (so-called "ptys"). Some Windows applications
>> like these ptys and won't write data to them (and they will certainly not
>> detect them as a console, so any console-specific functions won't work
> Hmm .. this is where it gets even more interesting. If I run:
> $ ssh user@W2003 date
> Wed Jun 21 18:02:13 GMTDT 2006
> .. then I get a result. But other commands don't, e.g.
> $ ssh user@W2003 cat /etc/hosts
> $ ssh user@W2003 ls
What does 'ssh user@2003 cygcheck ls' say?
>> On Windows 2003, SYSTEM does not have the appropriate privileges to
>> user contexts, so ssh-host-config needs to create an account that does.
>> Read <http://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-switch> for
> Before running ssh-host-config I did:
> - Right click My Computer, Properties > Advanced > Environment Variables
> - Under System Variables, click New, add CYGWIN as the variable name,
> add ntsec as the variable value
> - Under System Variables, scroll down to Path, click Edit, add
> ;c:\cygwin\bin to the end of the string already in the field
> Then opened Cygwin on the desktop, ran ssh-host-config and entered:
> "Privilege Separation?" Yes
> "Create local user SSHd?" Yes
> "Install SSHd as a service?" Yes
> "CYGWIN = " enter ntsec
> Should I have done anything different there on W2003 ?
Depends on what you need. If you need to get output from non-Cygwin
executables, then you'll need to re-install the service with "nontsec"
instead. But this is notably less secure. There should be no need to
do this if you're simply dealing with Cygwin utilities though.
Larry Hall http://www.rfk.com
RFK Partners, Inc. (508) 893-9779 - RFK Office
838 Washington Street (508) 893-9889 - FAX
Holliston, MA 01746
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
More information about the Cygwin