Hello,

I found a bug on ssh.

Before upgrade i use specific port for ssh, after upgrade i succeed in connecting but password is always rejected....

After a downgrade to 4.11 without any other change, i succeed in both connecting and logging....

So according to other posts, ssh seems to have a real problem.

Regards

Hi,

For me SSH on specific port works fine, on x86 platform.

Regards, Grzegorz.

check if you have set ssh-key for that account. If you are using ssh-key you cannot login using password anymore. That is as intended with RouterOS 5

check if you have set ssh-key for that account. If you are using ssh-key you cannot login using password anymore. That is as intended with RouterOS 5

I just wanted say, nice feature addition.

What's new in 5.0beta5 (2010-Jul-23 14:50):

*) ssh - password authentication is disabled for users with public keys;

well...

janisk,
I saw that in the changelog. I think this feature is a good feature for security, as it prevents brute-forcing a password if you use ssh-key for a user account.

Nice work

What's new in 5.0beta5 (2010-Jul-23 14:50):
*) ssh - password authentication is disabled for users with public keys;

I do approve of good default settings for security. But give me a chance to think by myself, please.
First case. I use public-keys from more than one place, and setting key from one place generates problem from another. I need to take roundabout route with key.
The second case. I use public-keys from central admin server. If I go to a customer for service, and can not use internet from there I can not login into machine, because have no access to central admin server.

There is a simple suggestion to patch this up. Let me disable this default environment. For instance:
/user set admin password-login=yes
or something similar.