Hello, please could you help me to resolve the issue below.
1. Windows 7 Starter
2. A user "admin" with an empty password is present on the system.
1. Install Copssh_5.1.0_x86_Free_Installer.exe with all default settings.
2. Run Copssh Control Panel and add the user "admin" to Copssh with all default settings.
3. In the Copssh Control Panel add keys for the user "admin". Use an empty passphrase for generating the keys.
4. Copy the private key to another machine and convert it with puttygen.exe for use with putty.
5. Connect from another machine using the private key from Step 4.
The connection to Copssh closes unexpectedly.
Client side log:
C:\Users\tester\soft\putty>plink -i id_rsa.ppk -v firstname.lastname@example.org ls
Looking up host "192.168.56.101"
Connecting to 192.168.56.101 port 22
Server version: SSH-2.0-OpenSSH_6.8
Using SSH protocol version 2
We claim version: SSH-2.0-PuTTY_Release_0.63
Network error: Software caused connection abort
FATAL ERROR: Network error: Software caused connection abort
Server side log (log level set to DEBUG3 for more details):
2015.08.04 07:32:03 - debug1: do_cleanup
2015.08.04 07:32:03 - error: mm_request_receive: socket closed
2015.08.04 07:32:03 - debug3: mm_request_receive entering
2015.08.04 07:32:03 - debug1: monitor_read_log: child log fd closed
2015.08.04 07:32:03 - debug1: do_cleanup [preauth]
2015.08.04 07:32:03 - fatal: setresuid 1002: Permission denied [preauth]
2015.08.04 07:32:03 - error: setreuid 1002: Permission denied [preauth]
2015.08.04 07:32:03 - debug1: permanently_set_uid: 1002/545 [preauth]
2015.08.04 07:32:03 - debug3: privsep user:group 1002:545 [preauth]
2015.08.04 07:32:03 - debug3: preauth child monitor started
2015.08.04 07:32:03 - debug2: Network child is on pid 3540
2015.08.04 07:32:03 - debug2: fd 3 setting O_NONBLOCK
2015.08.04 07:32:03 - debug1: Local version string SSH-2.0-OpenSSH_6.8
2015.08.04 07:32:03 - debug1: Enabling compatibility mode for protocol 2.0
2015.08.04 07:32:03 - debug1: no match: PuTTY_Release_0.63
2015.08.04 07:32:03 - debug1: Client protocol version 2.0; client software version PuTTY_Release_0.63
2015.08.04 07:32:03 - Connection from 192.168.56.1 port 54870 on 192.168.56.101 port 22
2015.08.04 07:32:03 - debug1: inetd sockets after dupping: 3, 3
2015.08.04 07:32:03 - debug3: send_rexec_state: done
2015.08.04 07:32:03 - debug3: ssh_msg_send: type 0
2015.08.04 07:32:03 - debug3: send_rexec_state: entering fd = 8 config len 375
2015.08.04 07:32:03 - debug1: rexec start in 5 out 5 newsock 5 pipe 7 sock 8
2015.08.04 07:32:03 - debug1: Forked child 3452.
2015.08.04 07:32:03 - debug1: fd 5 clearing O_NONBLOCK
I use Windows 7 Starter only for testing, the real ssh server will work on Windows 7 Professional 64-bit but the error presented above is reproducable also on Windows 7 Professional. I have also tried to disable UAC before installing copssh as suggested elsewhere but the result is the same. So how to setup the authetification by keys in Copssh 5.1.0?
Try to make a fake configuration change via server tab to trigger a service restart. Some system fules might not be updated timely.
I've actually done this in the original post because after the installation of Copssh I did the first try to connect, then changed the log level which caused a restart of the service, then did the second try. If you know what system files I should specifically check and what I should check please tell me. Or explain in more detail what you mean by making a fake configuration.
Any other suggestions on how to resolve the issue?
Try to use ssh.exe with -vvv flag to see what really happens from the client side. Check also if the service account is properly setup as specified at our FAQ.
After reading the FAQ I found that SvcCOPSSH was not a member of the Administrators group. I manually added it there and it worked, so thank you for your assistance, the issue has been resolved. You may want to reproduce why setting the membership in Administrators fails during an installation with all default settings.
For those who may come across this post later I specifically mention that I finally didn't need to change anything with respect to UAC to make Copssh 5.1.0 work.