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

Nick Couchman commented on GUACAMOLE-1658:
------------------------------------------

[~mjumper]: I've circled back to this and am trying to re-implement things 
using the libssh2 built-in functions instead of the custom ones that used to be 
present back in the 0.9.7 days. However, I'm having an unreasonably hard time 
wrapping my head around what the intent of this functionality actually is. My 
*guess* is that, if you use Guacamole to log in to a remote SSH server with a 
private key, the idea is that that private key will then be available to open 
further SSH sessions to other hosts. So, you go Guacamole -> host1.example.com 
with your private key, and then from host1.example.com you can seamlessly SSH 
to host2.example.com, using that same key-based credential?

I guess I'm having trouble conceptualizing it because, normally, I'd physically 
log in to my laptop, start ssh-agent, use "ssh-add" to add my key identity to 
my agent, and then I'd be able to SSH from my laptop to host1.example.com, and, 
if agent forwarding is enabled, I can go from there to host2.example.com, etc. 
So, instead of my physical computer holding the ssh-agent and key, Guacamole 
does that, correct?

Assuming this is the case, does ssh-agent need to already be running under the 
same account that guacd runs under? I think this is the part that I'm most 
confused about - what ssh-agent is actually being connected to - the one on the 
system running guacd, or the one on the initial SSH server?

> Unable to compile guacamole server with --enable-ssh-agent
> ----------------------------------------------------------
>
>                 Key: GUACAMOLE-1658
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-1658
>             Project: Guacamole
>          Issue Type: Bug
>          Components: guacamole-server
>    Affects Versions: 1.4.0
>         Environment: Rocky Linux 8.6 on x64, the latest libssh2 from remi 
> repository, guacamole server version 1.4.0.
>            Reporter: Pavel Kuzel
>            Assignee: Nick Couchman
>            Priority: Minor
>              Labels: guacamole-server, ssh-agent
>             Fix For: 1.6.0
>
>
> Hello there,
> a compilation of guacamole-server on Rocky Linux 8.6 with 
> "--enable-ssh-agent" fails on the missing ssh_key.h header file. Please see 
> the detail below:
> _make[2]: Entering directory 
> '/home/guacamole/guacamole-server/src/protocols/ssh'_
>   _CC       libguac_client_ssh_la-argv.lo_
> _In file included from ssh.h:33,_
>                  _from argv.c:22:_
> _ssh_agent.h:26:10: fatal error: ssh_key.h: No such file or directory_
>  _#include "ssh_key.h"_
>           _^~~~~~~~~~~_
> _compilation terminated._
> Just for the record, I use the latest version of libssh2 (1.10.0) and I'd 
> like to use the agent forwarding functionality within the guacamole server. 
> Is there any way how to get it running in the current version of 
> guacamole-server?
> Regards,
> Pavel
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to