[ 
https://issues.apache.org/jira/browse/GUACAMOLE-745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16782129#comment-16782129
 ] 

Nick Couchman commented on GUACAMOLE-745:
-----------------------------------------

{quote}
Looks like libssh2 supports it since this commit, but it is not released yet.
{quote}

Since it's a libssh2 issue, I don't know that there's any point in keeping this 
particular JIRA issue opened - if libssh2 supports it, then I doubt anything 
special will have to be done in Guacamole to gain that support.  For the Docker 
images, we'll have to wait until libssh2 libraries are released for the Debian 
Stable images before it can be integrated there.  All of these I consider 
"upstream" issues.

> Add support for OpenSSH private key format
> ------------------------------------------
>
>                 Key: GUACAMOLE-745
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-745
>             Project: Guacamole
>          Issue Type: Improvement
>          Components: guacd, SSH
>         Environment: Docker official images 1.0.0
>            Reporter: Julien Nicoulaud
>            Priority: Minor
>
> Since OpenSSH 7.8, {{ssh-keygen}} does not generate keys in PEM format by 
> default anymore: [https://www.openssh.com/txt/release-7.8]
> Attempting to use keys in the new format in Guacamole does not work, and does 
> not print any helpful error message even in debug mode:
> {code:java}
> guacd_1      | guacd[296]: DEBUG:        Attempting private key import 
> (WITHOUT passphrase)
> guacd_1      | guacd[296]: DEBUG:        Initial import failed: (null)
> guacd_1      | guacd[296]: DEBUG:        Re-attempting private key import 
> (WITH passphrase)
> guacd_1      | guacd[296]: ERROR:        Auth key import failed: (null){code}
> It would be nice if keys in OpenSSH new format were supported. At least a 
> more helpful error message should be printed (like "unrecognized key format").



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to