Bug 5317 - bad error message for bad permissions on public key file
Summary: bad error message for bad permissions on public key file
Status: CLOSED FIXED
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Client (show other bugs)
Version: pre-1.0
Hardware: PC Unknown
: P2 Normal
Target Milestone: 4.10.1
Assignee: Samuel Mannehed
URL:
Keywords: ossman_tester, relnotes
Depends on:
Blocks:
 
Reported: 2014-10-17 16:38 CEST by Pierre Ossman
Modified: 2019-05-21 15:09 CEST (History)
2 users (show)

See Also:
Acceptance Criteria:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Pierre Ossman cendio 2014-10-17 16:38:30 CEST 
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.
Comment 1 Pierre Ossman cendio 2018-09-26 16:05:30 CEST 
See also bug 7207.
Comment 3 Samuel Mannehed cendio 2019-03-05 16:25:23 CET 
See also bug 7313.
Comment 6 Pierre Ossman cendio 2019-04-01 11:17:42 CEST 
Works fine on Linux, but not on Windows. The client gladly proceeds even with a file that cannot be opened.
Comment 8 Samuel Mannehed cendio 2019-04-08 15:07:18 CEST 
Fixed. Tested on Windows 10 and Fedora 29.
Comment 13 Samuel Mannehed cendio 2019-04-08 15:54:00 CEST 
There were some additional errors in the committed code that has been fixed now.
Comment 14 Pierre Ossman cendio 2019-04-10 12:40:58 CEST 
Works well on both Linux and Windows now. Also checked release notes.
Comment 15 Pierre Ossman cendio 2019-05-17 11:14:42 CEST 
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.
Comment 17 Samuel Mannehed cendio 2019-05-17 15:58:27 CEST 
Fixed now.
Comment 18 Pierre Ossman cendio 2019-05-21 15:09:53 CEST 
Much better. :)

I've tested: 

 * Successful login
 * Unreadable key
 * Missing key
Note You need to log in before you can comment on or make changes to this bug.