You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@guacamole.apache.org by "Nick Couchman (Jira)" <ji...@apache.org> on 2020/02/04 12:25:00 UTC

[jira] [Commented] (GUACAMOLE-945) Migrating away from libssh2 dependency?

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

Nick Couchman commented on GUACAMOLE-945:
-----------------------------------------

Interesting, and a shame.  The power of libssh2 is that it's very simple and straight-forward to use - it does a few things very well, and that's pretty much all we need.  We could look at adding support for or migrating to the OpenSSH library - I'm guessing that's the most available and popular one - it's just going to take some work to make the switch, and I don't know if there are any licensing issues, although that tends to be less of an issue with guacd since we don't distribute binary code.

Thanks for submitting this - definitely good to know for our roadmap.

> Migrating away from libssh2 dependency?
> ---------------------------------------
>
>                 Key: GUACAMOLE-945
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-945
>             Project: Guacamole
>          Issue Type: Improvement
>          Components: guacd
>            Reporter: Joonas Tuomisto
>            Priority: Minor
>
> It appears Red Hat / CentOS stopped shipping libssh2 in version 8 which makes building Guacamole a hassle on those platforms - of course, this has nothing to do with Guacamole as such, but would it make sense to consider other libraries?
> I didn't look into this in depth so not sure if there's major benefits feature-wise and how much work this would entail...
>  
> libssh seems to have undergone an external security audit recently so security could be one consideration.
>  
> re: CentOS, this is discussed here: https://bugs.centos.org/view.php?id=16492



--
This message was sent by Atlassian Jira
(v8.3.4#803005)