Re: Make open ssh work with PKA on a Windows 2003 server

[Yohann Rebattu <y dot rebattu at yahoo dot fr>]

Hello again,
sorry to bother you, this this time, fallowing your instruction i could
start ssh daemon, i did try id and it seems to run fine with password
authentification, but as soon as i use the 'ssh-user-config' in order to
use the PKA, i can't login anymore (actualy i can but i'm diconnected
after 1 litle second), here is the end of ssh -vv
Administrateur@localhost after i use the ssh-user-config:

	Offering public key: /home/yohann/.ssh/id_rsa
debug2: we sent a publickey packet, wait for reply
debug1: Server accepts key: pkalg ssh-rsa blen 277
debug2: input_userauth_pk_ok: fp
8b:d6:51:9b:60:0b:e3:50:59:94:de:92:a4:83:4f:f9
debug1: read PEM private key done: type RSA
debug1: Authentication succeeded (publickey).
debug1: channel 0: new [client-session]
debug2: channel 0: send open
debug1: Entering interactive session.
debug2: callback start
debug2: client_session2_setup: id 0
debug2: channel 0: request pty-req confirm 0
debug1: Sending environment.
debug1: Sending env LANG = fr_FR.UTF-8
debug2: channel 0: request env confirm 0
debug2: channel 0: request shell confirm 0
debug2: fd 3 setting TCP_NODELAY
debug2: callback done
debug2: channel 0: open confirm rwindow 0 rmax 32768
debug2: channel 0: rcvd adjust 131072
debug2: channel 0: rcvd eof
debug2: channel 0: output open -> drain
debug2: channel 0: obuf empty
debug2: channel 0: close_write
debug2: channel 0: output drain -> closed
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug2: channel 0: rcvd close
debug2: channel 0: close_read
debug2: channel 0: input open -> closed
debug2: channel 0: almost dead
debug2: channel 0: gc: notify user
debug2: channel 0: gc: user detached
debug2: channel 0: send close
debug2: channel 0: is dead
debug2: channel 0: garbage collecting
debug1: channel 0: free: client-session, nchannels 1
Connection to medicat-partner.no-ip.org closed.


the funny thing is after i delete all id from /home/Administrateur/.ssh/
i can log again with password authentification.

so i did look for log but i couldn't find any AUTH.log in /var/log
nether SyslogFacility in /etc/sshd_config.
(i even try to write SyslogFacility=AUTH in /etc/sshd_config, but
nothing happen).

so do you know why the session closes right after it starts?

Thank you again, for your help

Le jeudi 15 février 2007 à 14:00 -0500, Larry Hall (Cygwin) a écrit :
> <http://www.cygwin.com/acronyms/#TOFU> - Reformatted
> 
> Yohann Rebattu wrote:
>  > thank you very much for answering me.
>  > i don't trust the other web site anymore about cygwin;
>  >
>  > i did read openssh.README and reinstall the whole thing
>  > the ssh-host-config didn't create sshd_server at the fisrt time, so
>  > since i've read the readme i ran cygrunsrv -R sshd
>  > and then run ssh-host-config again, this time it works and i got the
>  > proper user sshd_server but i got the error message about changing owner
>  > of /var/empty, /var/log/sshd.log
>  >
>  > so as explained in README file, i've tried to rerun ssh-host-config
>  > no error message this time.
>  > But once i run cygrunsrv -S sshd i get the message win32 error 1069
>  >
>  > So i had a look in the mailind list, i understood i had to change
>  > ownerchip of /var/empty and /var/log/sshd/log to SYSTEM:SYSTEM, but when
>  > i try to do it i get invalid user message.
>  >
>  > i'v tried to gave theses files to sshd or sshd_server (i don't know
>  > exactly wich one has to own the files) theses time i didn't get any
>  > error message, but still have error when runing the cygrunsrv -S sshd
>  > command.
>  >
>  > What shall i do now?
>  > thank you once again.
>  >
> 
> # net helpmsg 1069
> 
> The service did not start due to a login failure.
> 
> Sounds like sshd_service isn't allowed to log in.  Check its permissions.
> 


--
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/