KDE Dolphin Network Folder Wizard problem

jcdole · March 22, 2020, 7:14pm

1 -Start Point
3 computers : Computer 1 run leap 15.0; Computer 2 run leap 15.1 Computer 3 run leap 15.0
No problems with KDE Dolphin Network Folder Wizard.

Computer 2 is down and replaced.
I take this opportunity to test some scripts for automatically configure any new computer from a script. These tests did not involve changes on computers 1 and 3.0 But public and private SSH keys and . ppk kery bhave been replaced on all three computers.

2 - What works
A standard user can use putty to all three computers from any of all 3 computers.
User root can use putty to to all three computers from any of all 3 computers.

A standard user can ssh to its home folder on all three computers from any of all 3 computers.
User root can ssh to its home folder on all three computers from any of all 3 computers.

Starting dolphin in super user mode it is possible to create and save any link to root home folder on any computer from any computer.
Starting dolphin in super user mode it is possible to create and save any link to a standard user home folder on any computer from any computer.

You can start a sftp session from command line from any computer.
Example from computer 1 ( Leap 15.0)

sftp -4 -i /home/user_install/.ssh/id_rsa -P 11945    user_install@192.168.130.80:/home/user_install

 +----------------------------------------------------------------+
 |                                                                |
 |  Unauthorized or improper use of this system may result in     |
 |  administrative disciplinary action, civil charges/criminal    |
 |  penalties, and/or other sanctions. By continuing to use this  |
 |  system you indicate your awareness of and consent to these    |
 |  terms and conditions of use.                                  |
 |                                                                |
 +----------------------------------------------------------------+

Connected to 192.168.130.80.
Changing to: /home/user_install
sftp> ls
000_linx_echg.txt                                         1111111111111                                             
92ff1fae-5904-46d1-9b97-07cd90d35c39.jpg                  Desktop                                                   
Documents                                                 Downloads  
.........
....

**
On computer 2 only **it is possible for the initial standard user ( there is no other user on this computer ) to create and save any link to it’s home folder on any computer (from computer 2).

3 - What does not work.
**On computer 1 and 3 **it is impossible for the initial standard user ( all computers have the same initial user ) to create and save any link to it’s home folder on any other computer ( from computer 1 to computer 2 and 3 ; from computer 3 to computer 1 and 2 ).

4- Error message during an attempt to create a network folder.
Journald message on sender :

mars 22 18:39:56 MY-SERVER-LINUX kdeinit5[6417]: log_kio_sftp: *** Starting kio_sftp
mars 22 18:39:56 MY-SERVER-LINUX kdeinit5[6417]: log_kio_sftp: pid =  6417
mars 22 18:39:56 MY-SERVER-LINUX kdeinit5[6417]: log_kio_sftp: debug =
mars 22 18:39:56 MY-SERVER-LINUX kdeinit5[6417]: log_kio_sftp: "user_install" @ "192.168.130.80" : 11945
mars 22 18:39:56 MY-SERVER-LINUX kdeinit5[6417]: log_kio_sftp:
mars 22 18:39:56 MY-SERVER-LINUX kdeinit5[6417]: log_kio_sftp: QUrl("sftp://user_install@192.168.130.80:11945/home/user_install")
mars 22 18:39:56 MY-SERVER-LINUX kdeinit5[6417]: log_kio_sftp: checking cache: info.username = "user_install" , info.url = "sftp://user_install@192.168.130.80:11945"
mars 22 18:39:56 MY-SERVER-LINUX kiod5[3892]: org.kde.kio.kpasswdserver: User = "user_install" , WindowId = 136314885
mars 22 18:39:56 MY-SERVER-LINUX kdeinit5[6417]: log_kio_sftp: Creating the SSH session and setting options
mars 22 18:39:56 MY-SERVER-LINUX kdeinit5[6417]: log_kio_sftp: Trying to connect to the SSH server
mars 22 18:39:56 MY-SERVER-LINUX kdeinit5[6417]: log_kio_sftp: username= "user_install" , host= "192.168.130.80" , port= 11945
mars 22 18:39:56 MY-SERVER-LINUX kdeinit5[6417]: log_kio_sftp: Getting the SSH server hash
mars 22 18:39:56 MY-SERVER-LINUX kdeinit5[6417]: log_kio_sftp: Checking if the SSH server is known
mars 22 18:39:56 MY-SERVER-LINUX kdeinit5[6417]: log_kio_sftp: Trying to authenticate with the server
mars 22 18:39:56 MY-SERVER-LINUX kdeinit5[6417]: log_kio_sftp: Trying to authenticate with public key
mars 22 18:39:56 MY-SERVER-LINUX kdeinit5[6417]: log_kio_sftp: connected ? false username: old= "user_install" new= "user_install"

Debug message on remote side :

Server listening on 0.0.0.0 port 11945.
debug1: Server will not fork when running in debugging mode.
debug1: rexec start in 4 out 4 newsock 4 pipe -1 sock 7
debug1: sshd version OpenSSH_7.6, OpenSSL 1.1.0i-fips  14 Aug 2018
debug1: private host key #0: ssh-rsa SHA256:y2hZs9WJEbGVgeS2dKDgt4NexbIYpL2biJC+HPQfpX8
debug1: private host key #1: ssh-dss SHA256:CjFEq2zmk4P5AOnzF+A1NOaGlmMNKYM3Jh+3IkPjD00
debug1: private host key #2: ecdsa-sha2-nistp256 SHA256:gAQHoyJrd0fIYz/tP75Dg8d+x1pMiI4fsjBXsdxM6X4
debug1: private host key #3: ssh-ed25519 SHA256:IbWzsy4tYwRz4YewkRPyOflz+lz7brnbNjQDrLhlsz0
debug1: inetd sockets after dupping: 3, 3
Connection from 192.168.130.123 port 55212 on 192.168.130.80 port 11945
debug1: Client protocol version 2.0; client software version libssh_0.7.5
debug1: no match: libssh_0.7.5
debug1: Local version string SSH-2.0-OpenSSH_7.6
debug1: permanently_set_uid: 472/475 [preauth]
debug1: list_hostkey_types: ssh-rsa,rsa-sha2-512,rsa-sha2-256,ecdsa-sha2-nistp256,ssh-ed25519 [preauth]
debug1: SSH2_MSG_KEXINIT sent [preauth]
debug1: SSH2_MSG_KEXINIT received [preauth]
debug1: kex: algorithm: curve25519-sha256@libssh.org [preauth]
debug1: kex: host key algorithm: ssh-ed25519 [preauth]
debug1: kex: client->server cipher: aes256-ctr MAC: hmac-sha2-256 compression: none [preauth]
debug1: kex: server->client cipher: aes256-ctr MAC: hmac-sha2-256 compression: none [preauth]
debug1: kex: curve25519-sha256@libssh.org need=32 dh_need=32 [preauth]
debug1: kex: curve25519-sha256@libssh.org need=32 dh_need=32 [preauth]
debug1: expecting SSH2_MSG_KEX_ECDH_INIT [preauth]
debug1: rekey after 4294967296 blocks [preauth]
debug1: SSH2_MSG_NEWKEYS sent [preauth]
debug1: expecting SSH2_MSG_NEWKEYS [preauth]
debug1: SSH2_MSG_NEWKEYS received [preauth]
debug1: rekey after 4294967296 blocks [preauth]
debug1: KEX done [preauth]
debug1: userauth-request for user user_install service ssh-connection method none [preauth]
debug1: attempt 0 failures 0 [preauth]
debug1: PAM: initializing for "user_install"
debug1: PAM: setting PAM_RHOST to "192.168.130.123"
debug1: PAM: setting PAM_TTY to "ssh"
debug1: userauth_send_banner: sent [preauth]
debug1: userauth-request for user user_install service ssh-connection method publickey [preauth]
debug1: attempt 1 failures 0 [preauth]
debug1: userauth_pubkey: test whether pkalg/pkblob are acceptable for RSA SHA256:mNrAjD7bA47LnmV2OVsIl6G/ytJT62IUuDfJ02QAHw8 [preauth]
debug1: temporarily_use_uid: 1000/100 (e=0/0)
debug1: trying public key file /home/user_install/.ssh/authorized_keys
debug1: fd 4 clearing O_NONBLOCK
debug1: matching key found: file /home/user_install/.ssh/authorized_keys, line 3 RSA SHA256:mNrAjD7bA47LnmV2OVsIl6G/ytJT62IUuDfJ02QAHw8
debug1: restore_uid: 0/0
Postponed publickey for user_install from 192.168.130.123 port 55212 ssh2 [preauth]
Received disconnect from 192.168.130.123 port 55212:11: Bye Bye [preauth]
Disconnected from authenticating user user_install 192.168.130.123 port 55212 [preauth]
debug1: do_cleanup [preauth]
debug1: monitor_read_log: child log fd closed
debug1: do_cleanup
debug1: PAM: cleanup
debug1: Killing privsep child 6441

Any help is welcome

tsu2 · March 22, 2020, 8:43pm

I’m pretty sure when the machine was replaced that you didn’t restore from backup all the files as before so you lost the private keys for doing things like trying to authenticate to login to a remote machine… So you can’t use the public key that’s associated with the lost key.

Solution:
At least for what you’ve displayed, you should regenerate a new key pair and use the public key from that to create a new remote login (of course, you’ll need to set up SSH all over again so that the remote machine(s) know the new key is valid).

With your 3 machines, you’re approximately on the borderline between doing things as you are currently vs setting up network authentication like LDAP (or even conceivably SAMBA) or NIS. The idea is that when you do your authentication and store keys on a server, then you only need to protect that one server instead of each and every individual machine.

TSU

jcdole · March 22, 2020, 9:53pm

tsu2:

I’m pretty sure when the machine was replaced that you didn’t restore from backup all the files as before so you lost the private keys for doing things like trying to authenticate to login to a remote machine… So you can’t use the public key that’s associated with the lost key.

Solution:
At least for what you’ve displayed, you should regenerate a new key pair and use the public key from that to create a new remote login (of course, you’ll need to set up SSH all over again so that the remote machine(s) know the new key is valid).

With your 3 machines, you’re approximately on the borderline between doing things as you are currently vs setting up network authentication like LDAP (or even conceivably SAMBA) or NIS. The idea is that when you do your authentication and store keys on a server, then you only need to protect that one server instead of each and every individual machine.

TSU

Have you seen that** all **ssh and putty private and public keys have been replaced on all computers. So there is no old/previous keys on any computers.

As there is no lost keys but only new keys, that explain why I can ssh to any computers and I can putty on any computers.

The question is still there why KDE Dolphin Network Folder Wizard works on dolphin super user mode and not in standard mode.

jcdole · March 22, 2020, 9:55pm

I forgot to say that if I select fish protocol in place of sftp that works.