X-Spam-Check-By: sourceware.org Date: Wed, 21 Dec 2005 10:18:02 -0500 (EST) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: Ed Brady cc: cygwin AT cygwin DOT com Subject: Re: SSH problem after upgrade In-Reply-To: <43A95599.2010409@ebrady.net> Message-ID: References: <43A7855E DOT 7090002 AT ebrady DOT net> <43A95599 DOT 2010409 AT ebrady DOT net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: 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 On Wed, 21 Dec 2005, Ed Brady wrote: > > Ed Brady wrote: > > > > > After upgrading to the latest release of cygwin, I am continually > > > receiving the error message. > > > > > > socket: Operation not permitted > > > ssh: connect to host port 22: Operation not permitted > > > > > > I have had Cygwin installed on this computer for over three years > > > and have used ssh reguarly without any problems until this recent > > > upgrade. > > > > > > Also, I can copy ssh.exe to my home directory and for some strange > > > reason this seems to work. I have searched all over for an answer > > > to this problem with no avail. > > > Any help appreciated > > Thinking that the firewall might be an issue, I tried disabling it, but > with no luck. > The one peculiar behavior I see here is that this only seems to happen > whenever the files reside in /usr/bin. If I make a copy of them and put > them into my home dir the problem goes away. > Additionally, if I make a copy of the files, and let them REMAIN in the > /usr/bin dir, the problem still exists. Does it help if you leave the files in /usr/bin, but explicitly specify the path to the program (e.g., /home/Ed/telnet.exe)? > Some additional notes: > #1 - Copying the program to a different name under the SAME directory > (/usr/bin) does not cause the problem to go away, creating symlinks > does not help either. This means the problem is somehow related to > something specific to the attributes of /usr/bin itself. > #2 - Considering the three programs found (ssh, ftp, telnet), there is a > high probability that the root cause is related to how the "socket" or > related api cmds are being invoked or differences in how it is being > called when the application resides in the home directory versusus > /usr/bin. > #3 - I have yet to find a complete list, but I am betting that this > behavior will exist on all applications trying to open a priviledged > port. Sounds like a permission issue. What does "ls -ld /usr/bin" show? This may be a red herring, but try the following command: chmod a+x / /bin /lib /usr /etc If this helps, your trouble may be with traverse checking... Also, can you post the permissions on the original files and the copies in your home directory (both "ls -l" and "getfacl")? HTH, 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! "Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte." "But no -- you are no fool; you call yourself a fool, there's proof enough in that!" -- Rostand, "Cyrano de Bergerac" -- 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/