I setup a new user with a ssh public key, but everytime I try to log in with the key, it just falls back to password login (exits if I disable it)
The user home directories are in /mnt/vdev1/home/<username>. The keys are correctly saved in their respective ~/.ssh/authorized_keys but sshd just sends "SSH_MSG_USERAUTH_FAILURE" after my ssh client offers it's key fingerprint:
I checked the key fingerprint multiple times on my local machine, and remote freenas machine using
Output from my local machine:
Output from freenas:
Full ssh client debug output:
Note: I tested if this was just a fluke with this one user, the second user that I created (creation scr attached) had an even worse outcome, when I ssh into the new user I just get put into root (and ofc the key doesn't work):
Though the testuser home directory was created and the authorized_keys was filled in correctly (i had to check with root)
Am I like not supposed to create users in the disk pools? Or do I have to add read permissions for other so that ssh can read it? All of those options should like they have huge drawbacks.
The user home directories are in /mnt/vdev1/home/<username>. The keys are correctly saved in their respective ~/.ssh/authorized_keys but sshd just sends "SSH_MSG_USERAUTH_FAILURE" after my ssh client offers it's key fingerprint:
Code:
Offering public key: id_areuz RSA SHA256:VzxEHrULkK+J9LEeX/hzVWjnWIN9njnlbH6XxhJxxEk explicit debug3: send packet: type 50 debug2: we sent a publickey packet, wait for reply debug3: receive packet: type 51
I checked the key fingerprint multiple times on my local machine, and remote freenas machine using
ssh-keygen -lf
Output from my local machine:
Code:
ssh-keygen -lf ./id_areuz 4096 SHA256:VzxEHrULkK+J9LEeX/hzVWjnWIN9njnlbH6XxhJxxEk FreeNAS areuz (RSA) )
Output from freenas:
Code:
ssh-keygen -lf ./.ssh/authorized_keys 4096 SHA256:VzxEHrULkK+J9LEeX/hzVWjnWIN9njnlbH6XxhJxxEk FreeNAS areuz (RSA)
Full ssh client debug output:
Code:
ssh -vvv -i id_areuz areuz@10.0.1.3 OpenSSH_8.0p1, OpenSSL 1.1.1c 28 May 2019 debug1: Reading configuration data /etc/ssh/ssh_config debug2: resolve_canonicalize: hostname 10.0.1.3 is address debug2: ssh_connect_direct debug1: Connecting to 10.0.1.3 [10.0.1.3] port 22. debug1: Connection established. debug1: identity file id_areuz type 0 debug1: identity file id_areuz-cert type -1 debug1: Local version string SSH-2.0-OpenSSH_8.0 debug1: Remote protocol version 2.0, remote software version OpenSSH_7.9-hpn14v15 debug1: match: OpenSSH_7.9-hpn14v15 pat OpenSSH* compat 0x04000000 debug2: fd 3 setting O_NONBLOCK debug1: Authenticating to 10.0.1.3:22 as 'areuz' debug3: hostkeys_foreach: reading file "/c/Users/marek/.ssh/known_hosts" debug3: record_hostkey: found key type ECDSA in file /c/Users/marek/.ssh/known_hosts:1 debug3: load_hostkeys: loaded 1 keys from 10.0.1.3 debug3: order_hostkeyalgs: prefer hostkeyalgs: ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521 debug3: send packet: type 20 debug1: SSH2_MSG_KEXINIT sent debug3: receive packet: type 20 debug1: SSH2_MSG_KEXINIT received debug2: local client KEXINIT proposal debug2: KEX algorithms: curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1,ext-info-c debug2: host key algorithms: ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519-cert-v01@openssh.com,rsa-sha2-512-cert-v01@openssh.com,rsa-sha2-256-cert-v01@openssh.com,ssh-rsa-cert-v01@openssh.com,ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-cbc,3des-cbc,aes256-cbc,aes192-cbc debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-cbc,3des-cbc,aes256-cbc,aes192-cbc debug2: MACs ctos: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1 debug2: MACs stoc: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1 debug2: compression ctos: none,zlib@openssh.com,zlib debug2: compression stoc: none,zlib@openssh.com,zlib debug2: languages ctos: debug2: languages stoc: debug2: first_kex_follows 0 debug2: reserved 0 debug2: peer server KEXINIT proposal debug2: KEX algorithms: curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1 debug2: host key algorithms: rsa-sha2-512,rsa-sha2-256,ssh-rsa,ecdsa-sha2-nistp256,ssh-ed25519 debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-cbc,none debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-cbc,none debug2: MACs ctos: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1 debug2: MACs stoc: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1 debug2: compression ctos: none,zlib@openssh.com debug2: compression stoc: none,zlib@openssh.com debug2: languages ctos: debug2: languages stoc: debug2: first_kex_follows 0 debug2: reserved 0 debug1: kex: algorithm: curve25519-sha256 debug1: kex: host key algorithm: ecdsa-sha2-nistp256 debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none debug3: send packet: type 30 debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug3: receive packet: type 31 debug1: Server host key: ecdsa-sha2-nistp256 SHA256:ZMrWvs3mHSluqfpHx1YW3w0wqah5GX/nWRqP0R+G190 debug3: hostkeys_foreach: reading file "/c/Users/marek/.ssh/known_hosts" debug3: record_hostkey: found key type ECDSA in file /c/Users/marek/.ssh/known_hosts:1 debug3: load_hostkeys: loaded 1 keys from 10.0.1.3 debug1: Host '10.0.1.3' is known and matches the ECDSA host key. debug1: Found key in /c/Users/marek/.ssh/known_hosts:1 debug3: send packet: type 21 debug2: set_newkeys: mode 1 debug1: rekey out after 134217728 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug3: receive packet: type 21 debug1: SSH2_MSG_NEWKEYS received debug2: set_newkeys: mode 0 debug1: rekey in after 134217728 blocks debug1: Will attempt key: id_areuz RSA SHA256:VzxEHrULkK+J9LEeX/hzVWjnWIN9njnlbH6XxhJxxEk explicit debug2: pubkey_prepare: done debug3: send packet: type 5 debug3: receive packet: type 7 debug1: SSH2_MSG_EXT_INFO received debug1: kex_input_ext_info: server-sig-algs=<ssh-ed25519,ssh-rsa,rsa-sha2-256,rsa-sha2-512,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521> debug3: receive packet: type 6 debug2: service_accept: ssh-userauth debug1: SSH2_MSG_SERVICE_ACCEPT received debug3: send packet: type 50 debug3: receive packet: type 51 debug1: Authentications that can continue: publickey,password debug3: start over, passed a different list publickey,password debug3: preferred publickey,keyboard-interactive,password debug3: authmethod_lookup publickey debug3: remaining preferred: keyboard-interactive,password debug3: authmethod_is_enabled publickey debug1: Next authentication method: publickey debug1: Offering public key: id_areuz RSA SHA256:VzxEHrULkK+J9LEeX/hzVWjnWIN9njnlbH6XxhJxxEk explicit debug3: send packet: type 50 debug2: we sent a publickey packet, wait for reply debug3: receive packet: type 51 debug1: Authentications that can continue: publickey,password debug2: we did not send a packet, disable method debug3: authmethod_lookup password debug3: remaining preferred: ,password debug3: authmethod_is_enabled password debug1: Next authentication method: password areuz@10.0.1.3's password:
Note: I tested if this was just a fluke with this one user, the second user that I created (creation scr attached) had an even worse outcome, when I ssh into the new user I just get put into root (and ofc the key doesn't work):
Code:
ssh testuser@10.0.1.3 testuser@10.0.1.3's password: Last login: Wed Nov 13 12:59:23 2019 from 10.0.3.1 FreeBSD 11.2-STABLE (FreeNAS.amd64) #0 r325575+5920981193f(HEAD): Mon Sep 16 23:00:13 UTC 2019 FreeNAS (c) 2009-2019, The FreeNAS Development Team All rights reserved. FreeNAS is released under the modified BSD license. For more information, documentation, help or support, go here: http://freenas.org Welcome to FreeNAS Could not chdir to home directory /mnt/vdev1_4tb_WD-red/home/testuser: Permission denied -bash: /mnt/vdev1_4tb_WD-red/home/testuser/.bash_profile: Permission denied [testuser@freenas /]$ cat ./.ssh/authorized_keys cat: ./.ssh/authorized_keys: No such file or directory
Though the testuser home directory was created and the authorized_keys was filled in correctly (i had to check with root)
Am I like not supposed to create users in the disk pools? Or do I have to add read permissions for other so that ssh can read it? All of those options should like they have huge drawbacks.