SSH will complain to the log about the key being insecure and refusing to use it. But the error the user will get is "You are not authorized to connect to this server". We should present the actual error.
See also bug 7207.
See also bug 7313.
Works fine on Linux, but not on Windows. The client gladly proceeds even with a file that cannot be opened.
Fixed. Tested on Windows 10 and Fedora 29.
There were some additional errors in the committed code that has been fixed now.
Works well on both Linux and Windows now. Also checked release notes.
We didn't test the most important test, that a fully working key actually works with ThinLinc. And that is currently broken. I.e. it's completely impossible to use public keys with ThinLinc right now.
Much better. :)
* Successful login
* Unreadable key
* Missing key