Bug 4115 - Invalid key format on Windows client gives confusing error message
Summary: Invalid key format on Windows client gives confusing error message
Status: CLOSED DUPLICATE of bug 7313
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Client (show other bugs)
Version: 3.3.0
Hardware: PC Windows
: P2 Normal
Target Milestone: 4.15.0
Assignee: Bugzilla mail exporter
URL:
Keywords:
: 4249 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-12-22 13:24 CET by Aaron Sowry
Modified: 2022-09-28 15:24 CEST (History)
2 users (show)

See Also:
Acceptance Criteria:

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

Description Aaron Sowry cendio 2011-12-22 13:24:31 CET 
According to the TAG, the Windows client expects the key to be in PuTTY's special format. If it isn't, and one tries to connect using PKA, the client gives the message:

"Server does not support public key authentication."

The server does support PKA; the key is just in the wrong format. A message more along these lines would be much more helpful.
Comment 1 Peter Åstrand cendio 2012-04-04 10:49:48 CEST 
*** Bug 4249 has been marked as a duplicate of this bug. ***
Comment 2 Samuel Mannehed cendio 2022-09-28 14:59:21 CEST 
(In reply to Aaron Sowry from comment #0)
> According to the TAG, the Windows client expects the key to be in PuTTY's
> special format.

Note that this is no longer true, our TAG now says:

> The client currently only supports the OpenSSH key format. If your keys
> are in another format, e.g. for PuTTY, then they must first be converted
> before they can be used with ThinLinc.

https://www.cendio.com/resources/docs/tag-devel/html/authentication_publickey.html?highlight=putty#client-configuration
Comment 3 Pierre Ossman cendio 2022-09-28 15:24:31 CEST 

*** This bug has been marked as a duplicate of bug 7313 ***
Note You need to log in before you can comment on or make changes to this bug.