1.7.0-51: Problem using ssh public/private key authentication

[Michael H.]

Hello,

When I am using cygwin 1.5 both the public/private key and the
keyboard authentication with ssh work without problems. On 1.7
keyboard authentication also works but public/private key
authentication produces following error on the machine which I use to
connect to the server (client is Linux - server is Windows XP SP3 /
Cygwin):

4 [main] -bash 3392 C:\cygwin\bin\bash.exe: *** fatal error - couldn't
dynamically determine load address for 'WSAGetLastError' (handle
0xFFFFFFFF), Win32 error 126
Connection to xx.xx.xx.xx closed.

Here are the steps to reproduce:

Installation:
- Packages to install (chosen packages):
-- openssh (5.2p1-3)

Afterwards following steps have been done in the bash:
$ ssh-host-config
...
*** Query: Should privilege separation be used? (yes/no) yes
...
*** Query: new local account 'sshd'? (yes/no) yes
...
*** Query: Do you want to install sshd as a service?
*** Query: (Say "no" if it is already installed as a service) (yes/no) yes
...
*** Query: Enter the value of CYGWIN for the daemon: []

I appended the content of id_dsa.pub (generated by ssh-keygen) of the
Linux machine to the authorized_keys file in ~/.ssh on the remote
Windows machine.

$ net start sshd

has been executed to start the service.
Afterwards I tried to connect to the remote machine via ssh and then
following error occured:

4 [main] -bash 3392 C:\cygwin\bin\bash.exe: *** fatal error - couldn't
dynamically determine load address for 'WSAGetLastError' (handle
0xFFFFFFFF), Win32 error 126
Connection to xx.xx.xx.xx closed.


Thanks for any help,

Michael


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

[Corinna Vinschen-2]

On Jul 16 12:20, Michael H. wrote:

> Hello,
>
> When I am using cygwin 1.5 both the public/private key and the
> keyboard authentication with ssh work without problems. On 1.7
> keyboard authentication also works but public/private key
> authentication produces following error on the machine which I use to
> connect to the server (client is Linux - server is Windows XP SP3 /
> Cygwin):
>
> 4 [main] -bash 3392 C:\cygwin\bin\bash.exe: *** fatal error - couldn't
> dynamically determine load address for 'WSAGetLastError' (handle
> 0xFFFFFFFF), Win32 error 126
> Connection to xx.xx.xx.xx closed.

Weird.  Works fine for me.  

  $ net helpmsg 126

  The specified module could not be found.

Some third party influence?  http://cygwin.com/acronyms/#BLODA ?


Corinna

--
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

[Michael H.]

Corinna Vinschen-2 wrote:

On Jul 16 12:20, Michael H. wrote:
> Hello,
>
> When I am using cygwin 1.5 both the public/private key and the
> keyboard authentication with ssh work without problems. On 1.7
> keyboard authentication also works but public/private key
> authentication produces following error on the machine which I use to
> connect to the server (client is Linux - server is Windows XP SP3 /
> Cygwin):
>
> 4 [main] -bash 3392 C:\cygwin\bin\bash.exe: *** fatal error - couldn't
> dynamically determine load address for 'WSAGetLastError' (handle
> 0xFFFFFFFF), Win32 error 126
> Connection to xx.xx.xx.xx closed.

Weird.  Works fine for me.  

  $ net helpmsg 126

  The specified module could not be found.

Some third party influence?  http://cygwin.com/acronyms/#BLODA ?


Corinna

--
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

I uninstalled Avira AntiVir -> same result as described above.

Afterwards I decided to format my HD and install Windows XP again (with SP 1 - I wanted to install it without SP 1 but the version contains SP 1 already). After installing the drivers I installed cygwin (only openssh and vim) without any other third party software -> unfortunately still the same result as described above.

I also tried it on another computer (also Win XP) and the same error occurs.

Is it possible that there is anything wrong in the steps I have done to setup the host (listed in my first post)?

Thanks for any help,
Michael

[Julio Costa]

Hi Michael,

On Thu, Jul 23, 2009 at 10:49, Michael H.<> wrote:

>
>
> Corinna Vinschen-2 wrote:
>>
>> On Jul 16 12:20, Michael H. wrote:
>>> Hello,
>>>
>>> When I am using cygwin 1.5 both the public/private key and the
>>> keyboard authentication with ssh work without problems. On 1.7
>>> keyboard authentication also works but public/private key
>>> authentication produces following error on the machine which I use to
>>> connect to the server (client is Linux - server is Windows XP SP3 /
>>> Cygwin):
>>>
>>> 4 [main] -bash 3392 C:\cygwin\bin\bash.exe: *** fatal error - couldn't
>>> dynamically determine load address for 'WSAGetLastError' (handle
>>> 0xFFFFFFFF), Win32 error 126
>>> Connection to xx.xx.xx.xx closed.

I suspect of configuration / permissions problems...
Are you setting up some kind of chroot?
Also, is there any output on the /var/log/sshd.log file?

>>
>> Weird.  Works fine for me.

me too.

>
> Is it possible that there is anything wrong in the steps I have done to
> setup the host (listed in my first post)?
>

At the first sight, no. But it's not clear if you are using the
vanilla standard config files.
If you did some change, it could be important to share with us.

You can also try to run sshd "by-hand" to show us some verbose info:
cygrunsrv -E sshd
/usr/sbin/sshd -ddde

Then you can try to connect to your PC and see if the generated output
gives you any clue.
NOTE: It's possible that the problem doesn't show up in this debugging
mode. You will be running the sshd deamon as yourself, not as the
SYSTEM account.

___________
Julio Costa

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

[Michael H.]

Julio Costa wrote:

Hi Michael,

On Thu, Jul 23, 2009 at 10:49, Michael H.<> wrote:
>
>
> Corinna Vinschen-2 wrote:
>>
>> On Jul 16 12:20, Michael H. wrote:
>>> Hello,
>>>
>>> When I am using cygwin 1.5 both the public/private key and the
>>> keyboard authentication with ssh work without problems. On 1.7
>>> keyboard authentication also works but public/private key
>>> authentication produces following error on the machine which I use to
>>> connect to the server (client is Linux - server is Windows XP SP3 /
>>> Cygwin):
>>>
>>> 4 [main] -bash 3392 C:\cygwin\bin\bash.exe: *** fatal error - couldn't
>>> dynamically determine load address for 'WSAGetLastError' (handle
>>> 0xFFFFFFFF), Win32 error 126
>>> Connection to xx.xx.xx.xx closed.

I suspect of configuration / permissions problems...
Are you setting up some kind of chroot?
Also, is there any output on the /var/log/sshd.log file?

>>
>> Weird.  Works fine for me.

me too.

>
> Is it possible that there is anything wrong in the steps I have done to
> setup the host (listed in my first post)?
>

At the first sight, no. But it's not clear if you are using the
vanilla standard config files.
If you did some change, it could be important to share with us.

You can also try to run sshd "by-hand" to show us some verbose info:
cygrunsrv -E sshd
/usr/sbin/sshd -ddde

Then you can try to connect to your PC and see if the generated output
gives you any clue.
NOTE: It's possible that the problem doesn't show up in this debugging
mode. You will be running the sshd deamon as yourself, not as the
SYSTEM account.

___________
Julio Costa

Hi Julio,

The steps to reproduce have been done directly after installing Cygwin without any modifications. The logfile /var/log/sshd.log is empty even after the error has been printed on the Linux machine from which I connected to the Windows / Cygwin machine.

I executed the commands

$ cygrunsrv -E sshd
$ /usr/sbin/sshd -ddde

using my account (not by the SYSTEM account) and afterwards I connected from my Linux machine to the Windows / Cygwin machine without any problems! Like you assumed the problem didn't show up in this mode. When executing /usr/sbin/sshd using my account everything works fine but when executing it as service the error occurs.

Michael

[René Berber-2]

Michael H. wrote:

[snip]
> The steps to reproduce have been done directly after installing Cygwin
> without any modifications. The logfile /var/log/sshd.log is empty even after
> the error has been printed on the Linux machine from which I connected to
> the Windows / Cygwin machine.

The "system log" the manual refers to is not the one you are looking at,
its /var/log/messages and is only active if you installed and use syslog
(I prefer syslog-ng).

> I executed the commands
>
> $ cygrunsrv -E sshd
> $ /usr/sbin/sshd -ddde

And there you are creating the problem... or another problem: the
service runs as a special user, when you run it yourself its running as
your user so, if it works, that means you have permissions set to run as
your user not the service user.  Did that made sense? or I managed to
make something simple into some obscure fact.

The usual fix for what I described is to run the service installation
again, it should complain about the permissions so you can fix them.
--
René Berber


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

[XYM]

Hello,

I have encountered same problem after upgrading to 1.7.x. First to say that I'm not so familiar with all of that.

I was running a ssh-server and connect with Putty to my server using a tunnel. Everything works fine till today. After upgrading to 1.7.x and trying to connect to my server I get the following message:


2 [main] -bash 3776 C:\CygWin\bin\bash.exe: *** fatal error - couldn't dynamically determine load address for 'WSAGetLastError' (handle 0xFFFFFFFF), Win32 error 126

Tried to set up new sshd but no change.

Any ideas?

Happy X-Mas. :)

[René Berber-2]

XYM wrote:

> I have encountered same problem after upgrading to 1.7.x. First to say that
> I'm not so familiar with all of that.
>
> I was running a ssh-server and connect with Putty to my server using a
> tunnel. Everything works fine till today. After upgrading to 1.7.x and
> trying to connect to my server I get the following message:
>
>
> 2 [main] -bash 3776 C:\CygWin\bin\bash.exe: *** fatal error - couldn't
> dynamically determine load address for 'WSAGetLastError' (handle
> 0xFFFFFFFF), Win32 error 126
>
> Tried to set up new sshd but no change.

The error above is a client side error, you re-installed the server
which is not the problem.

In fact is not even a client side error, is bash complaining after you
logged in, the error code means "The specified module could not be
found." so it looks like bash is not finding all its libraries... but I
could be wrong, never seen an error message like that.
--
René Berber


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

[XYM]

With files from my backup I have newly set up Cygwin with 1.5.x. Everythings ok. Then I updated it to 1.7.x, same error like before.

XYM

Happy X-Mas

René Berber-2 wrote:

XYM wrote:

> I have encountered same problem after upgrading to 1.7.x. First to say that
> I'm not so familiar with all of that.
>
> I was running a ssh-server and connect with Putty to my server using a
> tunnel. Everything works fine till today. After upgrading to 1.7.x and
> trying to connect to my server I get the following message:
>
>
> 2 [main] -bash 3776 C:\CygWin\bin\bash.exe: *** fatal error - couldn't
> dynamically determine load address for 'WSAGetLastError' (handle
> 0xFFFFFFFF), Win32 error 126
>
> Tried to set up new sshd but no change.

The error above is a client side error, you re-installed the server
which is not the problem.

In fact is not even a client side error, is bash complaining after you
logged in, the error code means "The specified module could not be
found." so it looks like bash is not finding all its libraries... but I
could be wrong, never seen an error message like that.
--
René Berber


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

[THW Mark]

XYM wrote:

I was running a ssh-server and connect with Putty to my server using a tunnel. Everything works fine till today. After upgrading to 1.7.x and trying to connect to my server I get the following message:

2 [main] -bash 3776 C:\CygWin\bin\bash.exe: *** fatal error - couldn't dynamically determine load address for 'WSAGetLastError' (handle 0xFFFFFFFF), Win32 error 126

I am having the exact same issue. I installed cygwin with very basic configuration (added ssh, rsync and vim).

The odd thing about this is: when user/password prompt is enabled and entered manually, it logs in without any problems. The error comes up when the public key authentication is used. Unfortunately, for my application, I really need the key auth.

It seems to be a recent problem, there are very little google results about this issue...

Happy X-mas!

Mark

[XYM]

I've done some tests. Normally my passwordauthentification is set to no cause I only want to allow access with key. Now I've set to yes. Login with user/pass works here, too. With key no chance.

XYM

THW Mark wrote:

XYM wrote:

I was running a ssh-server and connect with Putty to my server using a tunnel. Everything works fine till today. After upgrading to 1.7.x and trying to connect to my server I get the following message:

2 [main] -bash 3776 C:\CygWin\bin\bash.exe: *** fatal error - couldn't dynamically determine load address for 'WSAGetLastError' (handle 0xFFFFFFFF), Win32 error 126

I am having the exact same issue. I installed cygwin with very basic configuration (added ssh, rsync and vim).

The odd thing about this is: when user/password prompt is enabled and entered manually, it logs in without any problems. The error comes up when the public key authentication is used. Unfortunately, for my application, I really need the key auth.

It seems to be a recent problem, there are very little google results about this issue...

Happy X-mas!

Mark

[THW Mark]

i've also tried overwriting my cygwin with the 'legacy' version but it doesnt seem to make any difference.

there are some other threads in the forum talking about this, but i have found no solution so far...

[THW Mark]

René Berber-2 wrote:

Michael H. wrote:

> $ cygrunsrv -E sshd
> $ /usr/sbin/sshd -ddde

And there you are creating the problem... or another problem: the
service runs as a special user, when you run it yourself its running as
your user so, if it works, that means you have permissions set to run as
your user not the service user.  Did that made sense? or I managed to
make something simple into some obscure fact.

I can confirm that running sshd as a local user indeed works. (for a one time connection). So, the solution must be with access rights to one or more files. Suggestions are very welcome here..

[THW Mark]

XYM wrote:

I've done some tests. Normally my passwordauthentification is set to no cause I only want to allow access with key. Now I've set to yes. Login with user/pass works here, too. With key no chance.

XYM

i think i found a solution/workaround!

- I had a useraccount 'user' with password in windows that is the same user that logs in over ssh
- i stopped the windows service
- in cygwin, i deleted the folder /var/empty
- then, i recreated the folder /var/empty (default access rights)
- in the services panel, open properties for the ssh service
- change the account in the second tab to "user" with the password included
- start the service

the service now starts, can use the /var/empty folder with the right permissions and allows ssh connection! i'm a happy man, time for turkey! :P

[XYM]

Thank you.

I've tried like described. Works.

But I think that it should be possible to run the service as local system, maybe someone has a solution for this.

XYM

THW Mark wrote:

XYM wrote:

I've done some tests. Normally my passwordauthentification is set to no cause I only want to allow access with key. Now I've set to yes. Login with user/pass works here, too. With key no chance.

XYM

i think i found a solution/workaround!

- I had a useraccount 'user' with password in windows that is the same user that logs in over ssh
- i stopped the windows service
- in cygwin, i deleted the folder /var/empty
- then, i recreated the folder /var/empty (default access rights)
- in the services panel, open properties for the ssh service
- change the account in the second tab to "user" with the password included
- start the service

the service now starts, can use the /var/empty folder with the right permissions and allows ssh connection! i'm a happy man, time for turkey! :P

[Larry Hall (Cygwin)]

On 12/24/2009 07:55 AM, THW Mark wrote:

>
>
> René Berber-2 wrote:
>>
>> Michael H. wrote:
>>
>>> $ cygrunsrv -E sshd
>>> $ /usr/sbin/sshd -ddde
>>
>> And there you are creating the problem... or another problem: the
>> service runs as a special user, when you run it yourself its running as
>> your user so, if it works, that means you have permissions set to run as
>> your user not the service user.  Did that made sense? or I managed to
>> make something simple into some obscure fact.
>>
>
> I can confirm that running sshd as a local user indeed works. (for a one
> time connection). So, the solution must be with access rights to one or more
> files. Suggestions are very welcome here..

In order to get this working, you'll need to undo what you have done.  You can
either:

   1. Audit ssh-host-config and ssh-user-config to reset all the permissions
and
      state back to the default.

   2. Remove Cygwin and reinstall, running ssh-host-config and ssh-user-config
      once "openssh" has been installed and after reading /usr/share/doc/Cygwin/
      openssh*.  If that doesn't work, then before fiddling, read and follow
the
      problem reporting guidelines found at the link below to report the issue
      here.  Then someone here may be able to help you track down the
      problem.

      <http://cygwin.com/problems.html>

--
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      [phone] - RFK Office
216 Dalton Rd.                          [phone] - FAX
Holliston, MA 01746

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple