This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Build problem with most current cygwin?

On 4/11/2012 9:14 PM, wrote:
Several folk here use Cygwin with windows 7 enterprise as a tool to access linux servers. They have Cygwin with X installed and use a combination of terminal windows and X exports from the RH servers to manage items.

The most recent version of Cygwin, when upgraded, breaks in these uses. I have spent a little time isolating causes.

"most recent" is not a version number. Could you at least clarify from which version to which version did you upgrade ?

Ssh(1) on normal install does not get any config files.

$ cygcheck -l openssh |grep bin /usr/bin/slogin /usr/bin/ssh-keyscan.exe /usr/bin/ssh-user-config /usr/bin/sftp.exe /usr/bin/ssh-host-config /usr/bin/ssh-copy-id /usr/bin/ssh.exe /usr/bin/ssh-keygen.exe /usr/bin/ssh-add.exe /usr/bin/scp.exe /usr/bin/ssh-agent.exe /usr/sbin/sshd.exe /usr/sbin/sftp-server.exe /usr/sbin/ssh-keysign.exe /usr/sbin/ssh-pkcs11-helper.exe

When config files are placed at the usual suspect locations, ssh(1) ignores them.

cygrun-host-config -y

this file is not from cygwin

does build the config files, but it cannot complete because the required accounts cannot be created , not even by someone with admin access. It fails on permisssions.

alias ssh="ssh -2 -I ~/.ssh/id-rsa"

in .bashrc
does allow ssh to do password-less access to the servers but it breaks on

hg clone ssh://...

which is now totally non-functional.

The two offered downloads of Cygwin are now of greatly reduced utility because the way duties are arranged doesn't allow functioning of the agent or the id mechanism.

Everyone has been advised to hold without updating on Cygwin, and new machines are now being equipped with VMware player and RHEL6.


what about providing same data like Problem reports:

Usually the file in ~/.ssh should have a 600 permission,
otherwise ssh refuse to use them.
Wich permission do you see ?


-- Problem reports: FAQ: Documentation: Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]