Has anyone had any luck with SSH in V7.3 or V7.4?
I've not had any luck with /system ssh address=<ip address> user=<user name>
I watch the logs on my remote SSH server and nothing even tries to connect.
Works great on V6.49.6
Which MikroTik device is it? (device that works with v6 but not v7)yes, can ping the server.
and can SSH from another Tik in the office. But its on V6.
# $OpenBSD: sshd_config,v 1.103 2018/04/09 20:41:22 tj Exp $
# This is the sshd server system-wide configuration file. See
# sshd_config(5) for more information.
# This sshd was compiled with PATH=/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/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.
# If you want to change the port on a SELinux system, you have to tell
# SELinux about this change.
# semanage port -a -t ssh_port_t -p tcp #PORTNUMBER
#
#Port 22
#AddressFamily any
#ListenAddress 0.0.0.0
#ListenAddress ::
HostKey /etc/ssh/ssh_host_rsa_key
HostKey /etc/ssh/ssh_host_ecdsa_key
HostKey /etc/ssh/ssh_host_ed25519_key
# Ciphers and keying
#RekeyLimit default none
# This system is following system-wide crypto policy. The changes to
# crypto properties (Ciphers, MACs, ...) will not have any effect here.
# They will be overridden by command-line options passed to the server
# on command line.
# Please, check manual pages for update-crypto-policies(8) and sshd_config(5).
# Logging
#SyslogFacility AUTH
SyslogFacility AUTHPRIV
LogLevel INFO
#LogLevel DEBUG3
# Authentication:
#LoginGraceTime 2m
PermitRootLogin yes
#StrictModes yes
#MaxAuthTries 10
#MaxSessions 10
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
#AuthorizedKeysFile .ssh/authorized_keys/rd_rsa
#AuthorizedPrincipalsFile none
#AuthorizedKeysCommand none
#AuthorizedKeysCommandUser nobody
# For this to work you will also need host keys in /etc/ssh/ssh_known_hosts
#HostbasedAuthentication no
# Change to yes if you don't trust ~/.ssh/known_hosts for
# 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 yes
PasswordAuthentication yes
# Change to no to disable s/key passwords
#ChallengeResponseAuthentication yes
ChallengeResponseAuthentication no
# Kerberos options
#KerberosAuthentication no
#KerberosOrLocalPasswd yes
#KerberosTicketCleanup yes
#KerberosGetAFSToken no
#KerberosUseKuserok yes
# GSSAPI options
#GSSAPIAuthentication yes
#GSSAPICleanupCredentials no
#GSSAPIStrictAcceptorCheck yes
#GSSAPIKeyExchange no
#GSSAPIEnablek5users no
# 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
# and ChallengeResponseAuthentication to 'no'.
# WARNING: 'UsePAM no' is not supported in Fedora and may cause several
# problems.
UsePAM yes
#AllowAgentForwarding yes
#AllowTcpForwarding yes
#GatewayPorts no
X11Forwarding yes
#X11DisplayOffset 10
#X11UseLocalhost yes
#PermitTTY yes
# It is recommended to use pam_motd in /etc/pam.d/sshd instead of PrintMotd,
# as it is more configurable and versatile than the built-in version.
PrintMotd no
#PrintLastLog yes
#TCPKeepAlive yes
#PermitUserEnvironment no
#Compression delayed
#ClientAliveInterval 0
#ClientAliveCountMax 3
#UseDNS no
#PidFile /var/run/sshd.pid
#MaxStartups 10:30:100
#PermitTunnel no
#ChrootDirectory none
#VersionAddendum none
# no default banner path
#Banner none
# Accept locale-related environment variables
AcceptEnv LANG LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY LC_MESSAGES
AcceptEnv LC_PAPER LC_NAME LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT
AcceptEnv LC_IDENTIFICATION LC_ALL LANGUAGE
AcceptEnv XMODIFIERS
# override default of no subsystems
Subsystem sftp /usr/libexec/openssh/sftp-server
#Subsystem sftp internal-sftp
# Example of overriding settings on a per-user basis
#Match User anoncvs
# X11Forwarding no
# AllowTcpForwarding no
# PermitTTY no
# ForceCommand cvs server
#Match Group sftpusers
#ChrootDirectory /data/%u
#ForceCommand internal-sftp
No, turned off strong-crypto=yes.Do you have strong-crypto=yes enabled on the router? I'm not certain that this affects the SSH client as well, but let's get that established, just in case.
RouterOS 7.3 removes DSA authentication. If your remote server requires it, there's your problem. This is a long-obsolete algorithm.
As for the advice about ECDSA and ED25519 above, that would be nice, but RouterOS doesn't support that for SSH yet. This limits you to RSA variants.
If the server is OpenSSH, would you mind posting its configuration file? (Typically /etc/ssh/sshd_config) Feel free to sanitize it, though in all likelihood it will be an OS default file, so not secret.
I generated the key files with -PEM option
But I'm not using the SSH server in RouterOS.
Its also very annoying how the key file gets deleted after its imported. (new feature in v7 apparently)
% ssh centos
$ ssh-keygen -m pem -t rsa -f ~/.ssh/id_myswitch
Generating public/private rsa key pair
Enter passphrase (empty for no passphrase): <ENTER>
Enter same passphrase again: <ENTER>
Your identification has been saved in ~/.ssh/id_myswitch
Your public key has been saved in ~/.ssh/id_myswitch.pub
The key fingerprint is:…
$ scp .ssh/id_myswitch* imac:Desktop
$ cat .ssh/id_myswitch.pub >> .ssh/authorized_keys
$ exit
logout
Connection to centos closed.
% scp ~/Desktop/id_my* me@myswitch:
% ssh me@myswitch
> /user ssh-keys private import private-key-file=id_myswitch user=me
passphrase: <ENTER>
> /system/ssh centos
$ echo 'Et voila!'
Et voila!
$ exit
Welcome back!
> quit
%
Did you use a passphrase? I do.
what version of v7 are you running?
ssh - fixed host key generation (introduced in v7.3);
Thanks for the info, I learned something new.This item in the changelog is referring to the "/ip/ssh/regenerate-host-key" feature. Nothing to do with this topic, as it affects only RouterOS's SSH server, not its SSH client.