[solved] can not access remote with login/password (update to ssh 7)

student975 · 2015-08-14 20:51:11

Hi! I have (headless!!) NAS running Arch (as well as workstation), and after today updates I can not access to the NAS - password isn't accepted.
Nothing related to today Arch announce (don't use dsa keys).

How to resolve? What is additional information I must to supply?

Last edited by student975 (2015-08-14 23:50:28)

jasonwryan · 2015-08-14 20:55:18

Paste the output of `grep ssh-dss ~/.ssh/authorized_keys` on the NAS.

What else was updated? What does `ssh -vvv...` show?

Moving to NC...

student975 · 2015-08-14 20:57:43

Additional information: say, access to samba still does work.

student975 · 2015-08-14 21:00:08

jasonwryan wrote:

Paste the output of `grep ssh-dss ~/.ssh/authorized_keys` on the NAS.
What else was updated? What does `ssh -vvv...` show?

Moving to NC...

How will I execute commands? At the moment I have just access to few directories with samba. Do your questions mean there is the only way to repair all my flat to get NAS connected to keyboard and display?

Last edited by student975 (2015-08-14 21:02:23)

jasonwryan · 2015-08-14 21:03:32

Well, the ssh command can be executed from the remote machine. As for the other two, yes, you'll need access to the NAS.

student975 · 2015-08-14 21:05:08

jasonwryan wrote:

What does `ssh -vvv...` show?

On the client side:

~ $ ssh -vvv root@nas
OpenSSH_7.0p1, OpenSSL 1.0.2d 9 Jul 2015
debug1: Reading configuration data /etc/ssh/ssh_config
debug2: ssh_connect: needpriv 0
debug1: Connecting to nas [192.168.1.103] port 22.
debug1: Connection established.
debug1: identity file /home/anli/.ssh/id_rsa type 1
debug1: key_load_public: No such file or directory
debug1: identity file /home/anli/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/anli/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/anli/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/anli/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/anli/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/anli/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/anli/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.0
debug1: Remote protocol version 2.0, remote software version OpenSSH_7.0
debug1: match: OpenSSH_7.0 pat OpenSSH* compat 0x04000000
debug2: fd 3 setting O_NONBLOCK
debug1: Authenticating to nas:22 as 'root'
debug3: hostkeys_foreach: reading file "/home/anli/.ssh/known_hosts"
debug3: record_hostkey: found key type ECDSA in file /home/anli/.ssh/known_hosts:1
debug3: load_hostkeys: loaded 1 keys from nas
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
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug2: kex_parse_kexinit: curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1
debug2: kex_parse_kexinit: 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,ssh-rsa-cert-v01@openssh.com,ssh-ed25519,ssh-rsa
debug2: kex_parse_kexinit: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se
debug2: kex_parse_kexinit: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se
debug2: kex_parse_kexinit: 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,hmac-md5-etm@openssh.com,hmac-ripemd160-etm@openssh.com,hmac-sha1-96-etm@openssh.com,hmac-md5-96-etm@openssh.com,hmac-md5,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: 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,hmac-md5-etm@openssh.com,hmac-ripemd160-etm@openssh.com,hmac-sha1-96-etm@openssh.com,hmac-md5-96-etm@openssh.com,hmac-md5,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib
debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib
debug2: kex_parse_kexinit: 
debug2: kex_parse_kexinit: 
debug2: kex_parse_kexinit: first_kex_follows 0 
debug2: kex_parse_kexinit: reserved 0 
debug2: kex_parse_kexinit: curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1
debug2: kex_parse_kexinit: ssh-rsa,ecdsa-sha2-nistp256,ssh-ed25519
debug2: kex_parse_kexinit: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
debug2: kex_parse_kexinit: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
debug2: kex_parse_kexinit: 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: kex_parse_kexinit: 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: kex_parse_kexinit: none,zlib@openssh.com
debug2: kex_parse_kexinit: none,zlib@openssh.com
debug2: kex_parse_kexinit: 
debug2: kex_parse_kexinit: 
debug2: kex_parse_kexinit: first_kex_follows 0 
debug2: kex_parse_kexinit: reserved 0 
debug1: kex: server->client chacha20-poly1305@openssh.com <implicit> none
debug1: kex: client->server chacha20-poly1305@openssh.com <implicit> none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ecdsa-sha2-nistp256 SHA256:/2DaK0DJDPC66d71YzPxp/woCzQsjmE5X5VUTi/Tebo
debug3: hostkeys_foreach: reading file "/home/anli/.ssh/known_hosts"
debug3: record_hostkey: found key type ECDSA in file /home/anli/.ssh/known_hosts:1
debug3: load_hostkeys: loaded 1 keys from nas
debug3: hostkeys_foreach: reading file "/home/anli/.ssh/known_hosts"
debug3: record_hostkey: found key type ECDSA in file /home/anli/.ssh/known_hosts:1
debug3: load_hostkeys: loaded 1 keys from 192.168.1.103
debug1: Host 'nas' is known and matches the ECDSA host key.
debug1: Found key in /home/anli/.ssh/known_hosts:1
debug2: set_newkeys: mode 1
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug2: set_newkeys: mode 0
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug2: key: /home/anli/.ssh/id_rsa (0x55db7efefd40),
debug2: key: /home/anli/.ssh/id_dsa ((nil)),
debug2: key: /home/anli/.ssh/id_ecdsa ((nil)),
debug2: key: /home/anli/.ssh/id_ed25519 ((nil)),
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 RSA public key: /home/anli/.ssh/id_rsa
debug3: send_pubkey_test
debug2: we sent a publickey packet, wait for reply
debug1: Authentications that can continue: publickey,password
debug1: Trying private key: /home/anli/.ssh/id_dsa
debug3: no such identity: /home/anli/.ssh/id_dsa: No such file or directory
debug1: Trying private key: /home/anli/.ssh/id_ecdsa
debug3: no such identity: /home/anli/.ssh/id_ecdsa: No such file or directory
debug1: Trying private key: /home/anli/.ssh/id_ed25519
debug3: no such identity: /home/anli/.ssh/id_ed25519: No such file or directory
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
root@nas's password:

student975 · 2015-08-14 21:08:53

jasonwryan wrote:

What else was updated?

At the moment just can say, I have previously updated NAS a day or two days ago, all was fine.

student975 · 2015-08-14 21:13:21

Aha. Good (for me) news!! I can access as not-root and then su.

[root@nas ~]# grep ssh-dss ~/.ssh/authorized_keys
grep: /root/.ssh/authorized_keys: No such file or directory

jasonwryan · 2015-08-14 21:16:09

Post the sshd_config of the NAS

student975 · 2015-08-14 21:17:36

jasonwryan wrote:

What else was updated?

Only three packages were updated:

[2015-08-14 20:00] [ALPM] upgraded fontconfig (2.11.1-1 -> 2.11.1-2)
[2015-08-14 20:00] [ALPM] upgraded libdrm (2.4.62-1 -> 2.4.63-1)
[2015-08-14 20:00] [ALPM] upgraded openssh (6.9p1-2 -> 7.0p1-1)

student975 · 2015-08-14 21:22:39

jasonwryan wrote:

Post the sshd_config of the NAS

#	$OpenBSD: sshd_config,v 1.97 2015/08/06 14:53:21 deraadt Exp $

# This is the sshd server system-wide configuration file.  See
# sshd_config(5) for more information.

# This sshd was compiled with PATH=/usr/bin:/bin:/usr/sbin:/sbin

# The strategy used for options in the default sshd_config shipped with
# OpenSSH is to specify options with their default value where
# possible, but leave them commented.  Uncommented options override the
# default value.

#Port 22
#AddressFamily any
#ListenAddress 0.0.0.0
#ListenAddress ::

# The default requires explicit activation of protocol 1
#Protocol 2

# HostKey for protocol version 1
#HostKey /etc/ssh/ssh_host_key
# HostKeys for protocol version 2
#HostKey /etc/ssh/ssh_host_rsa_key
#HostKey /etc/ssh/ssh_host_dsa_key
#HostKey /etc/ssh/ssh_host_ecdsa_key
#HostKey /etc/ssh/ssh_host_ed25519_key

# Lifetime and size of ephemeral version 1 server key
#KeyRegenerationInterval 1h
#ServerKeyBits 1024

# Ciphers and keying
#RekeyLimit default none

# Logging
# obsoletes QuietMode and FascistLogging
#SyslogFacility AUTH
#LogLevel INFO

# Authentication:

#LoginGraceTime 2m
#PermitRootLogin prohibit-password
#StrictModes yes
#MaxAuthTries 6
#MaxSessions 10

#RSAAuthentication yes
#PubkeyAuthentication yes

# The default is to check both .ssh/authorized_keys and .ssh/authorized_keys2
# but this is overridden so installations will only check .ssh/authorized_keys
AuthorizedKeysFile	.ssh/authorized_keys

#AuthorizedPrincipalsFile none

#AuthorizedKeysCommand none
#AuthorizedKeysCommandUser nobody

# For this to work you will also need host keys in /etc/ssh/ssh_known_hosts
#RhostsRSAAuthentication no
# similar for protocol version 2
#HostbasedAuthentication no
# Change to yes if you don't trust ~/.ssh/known_hosts for
# RhostsRSAAuthentication and HostbasedAuthentication
#IgnoreUserKnownHosts no
# Don't read the user's ~/.rhosts and ~/.shosts files
#IgnoreRhosts yes

# To disable tunneled clear text passwords, change to no here!
#PasswordAuthentication yes
#PermitEmptyPasswords no

# Change to no to disable s/key passwords
ChallengeResponseAuthentication no

# Kerberos options
#KerberosAuthentication no
#KerberosOrLocalPasswd yes
#KerberosTicketCleanup yes
#KerberosGetAFSToken no

# GSSAPI options
#GSSAPIAuthentication no
#GSSAPICleanupCredentials yes

# Set this to 'yes' to enable PAM authentication, account processing,
# and session processing. If this is enabled, PAM authentication will
# be allowed through the ChallengeResponseAuthentication and
# PasswordAuthentication.  Depending on your PAM configuration,
# PAM authentication via ChallengeResponseAuthentication may bypass
# the setting of "PermitRootLogin without-password".
# If you just want the PAM account and session checks to run without
# PAM authentication, then enable this but set PasswordAuthentication
# and ChallengeResponseAuthentication to 'no'.
UsePAM yes

#AllowAgentForwarding yes
#AllowTcpForwarding yes
#GatewayPorts no
#X11Forwarding no
#X11DisplayOffset 10
#X11UseLocalhost yes
#PermitTTY yes
PrintMotd no # pam does that
#PrintLastLog yes
#TCPKeepAlive yes
#UseLogin no
UsePrivilegeSeparation sandbox		# Default for new installations.
#PermitUserEnvironment no
#Compression delayed
#ClientAliveInterval 0
#ClientAliveCountMax 3
#UseDNS no
#PidFile /run/sshd.pid
#MaxStartups 10:30:100
#PermitTunnel no
#ChrootDirectory none
#VersionAddendum none

# no default banner path
#Banner none

# override default of no subsystems
Subsystem	sftp	/usr/lib/ssh/sftp-server

# Example of overriding settings on a per-user basis
#Match User anoncvs
#	X11Forwarding no
#	AllowTcpForwarding no
#	PermitTTY no
#	ForceCommand cvs server

jasonwryan · 2015-08-14 23:34:03

man sshd_config | less -p PermitRootLogin

student975 · 2015-08-14 23:49:34

jasonwryan wrote:

man sshd_config | less -p PermitRootLogin

Thanks!

I guess the default behavior has changed (as far as I haven't changed any configuration files), and it would be useful to announce it.

jasonwryan · 2015-08-14 23:58:12

student975 wrote:

jasonwryan wrote:
man sshd_config | less -p PermitRootLogin
Thanks!
I guess the default behavior has changed (as far as I haven't changed any configuration files), and it would be useful to announce it.

It was announced: in the upstream changelog that is linked to from the News item...

Arch Linux

#1 2015-08-14 20:51:11

[solved] can not access remote with login/password (update to ssh 7)

#2 2015-08-14 20:55:18

Re: [solved] can not access remote with login/password (update to ssh 7)

#3 2015-08-14 20:57:43

Re: [solved] can not access remote with login/password (update to ssh 7)

#4 2015-08-14 21:00:08

Re: [solved] can not access remote with login/password (update to ssh 7)

#5 2015-08-14 21:03:32

Re: [solved] can not access remote with login/password (update to ssh 7)

#6 2015-08-14 21:05:08

Re: [solved] can not access remote with login/password (update to ssh 7)

#7 2015-08-14 21:08:53

Re: [solved] can not access remote with login/password (update to ssh 7)

#8 2015-08-14 21:13:21

Re: [solved] can not access remote with login/password (update to ssh 7)

#9 2015-08-14 21:16:09

Re: [solved] can not access remote with login/password (update to ssh 7)

#10 2015-08-14 21:17:36

Re: [solved] can not access remote with login/password (update to ssh 7)

#11 2015-08-14 21:22:39

Re: [solved] can not access remote with login/password (update to ssh 7)

#12 2015-08-14 23:34:03

Re: [solved] can not access remote with login/password (update to ssh 7)

#13 2015-08-14 23:49:34

Re: [solved] can not access remote with login/password (update to ssh 7)

#14 2015-08-14 23:58:12

Re: [solved] can not access remote with login/password (update to ssh 7)

Board footer