I'm new with guacamole and configured basic WEB authentication with tokens
${GUAC_PASSWORD} and ${GUAC_USERNAME) to use with RDP connection.
This work with static
My goal is to use dynamic WEB authentication with tokens based on LDAP (
Active Directory)
I've read topic
https://sourceforge.net/
I had same error over RDP. Problem is to set ignore certificates and use NLA
authentication (windows 2012 R2) This settings helped me connect with
success:
rdp
192.168.0.2
3389
test
password
nla
true
true
--
Sent from:
http://apache-guacamole-general-user-mailing-list.2363388.n4.nabble.com/
I just played around with my setup for an RDP connection we have, and what you
suggested didn't work. The RDP server is a Windows 2008 R2 server. I truly
believe that the issue is due to us making our machines FIPS compliant, which
is why SSH connections now fail with "SSH handshake failed".
On Mon, Jan 22, 2018 at 9:15 AM, wrote:
> Guacd is running. I looked at /var/log/messages and encountered the
> following:
>
>
>
> Jan 22 09:09:21 access guacd[1760]: Creating new client for protocol "ssh"
>
> Jan 22 09:09:21 access guacd[1760]: Connection ID is
> "$e25765a1-e06d-4bd7-959c-2e787
OK, I see that. Looks like it has support for it, however, I have libssh2
version 1.4.3 installed. I couldn’t find anything that says what 1.4.3 had
support for. Assuming that it DOES support the FIPS algorithms, what settings
for an SSH connection will I need to set to allow this? The only
As a test, I made a new Guacamole connection to a server that we did NOT make
FIPS 140-2 compliant yet, and was able to get right in. So the FIPS 140-2 is
definitely the issue. So I need to know if there’s something in guacamole
0.9.13 that I need to tweak, or libssh2. I’m not sure if I can u
On Wed, Jan 24, 2018 at 10:55 AM, wrote:
> As a test, I made a new Guacamole connection to a server that we did NOT
> make FIPS 140-2 compliant yet, and was able to get right in. So the FIPS
> 140-2 is definitely the issue. So I need to know if there’s something in
> guacamole 0.9.13 that I nee
We had a fully patched RHEL 7.4 server, and ran the following commands on it
(based on the article found here, which requires a Red Hat account to look at:
https://access.redhat.com/solutions/137833 ):
yum install dracut-fips
grep -qw aes /proc/cpuinfo && echo YES || echo no
# If the above grep
Did some more debugging. When we try to connect to a server that is FIPS 140-2
compliant, here’s what the algorithms that are expected are:
When I try to connect via a Guacamole SSH session, here are the algorithms
being sent:
debug2: KEX algorithms:
ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-
Hi, im trying to specify the color-depth parameter and the dpi parameter to
an windows server.
The dpi is working fine, but when I try to specify the color-depth it not
changes the default value.
I have tried to set 16 and 32 as value.
On the guacd logs It says nothing about the color-depth parame
On Wed, Jan 24, 2018 at 1:14 PM, genesis wrote:
> Hi, im trying to specify the color-depth parameter and the dpi parameter to
> an windows server.
> The dpi is working fine ...
On the contrary, for the "dpi" parameter, your logs say:
> Jan 24 12:55:12 debian guacd[9281]: Specified value "[#015
On Wed, Jan 24, 2018 at 11:49 AM, wrote:
> Did some more debugging. When we try to connect to a server that is FIPS
> 140-2 compliant, here’s what the algorithms that are expected are:
>
>
>
> When I try to connect via a Guacamole SSH session, here are the algorithms
> being sent:
>
> debug2: KE
On Wed, Jan 24, 2018 at 2:02 PM, Mike Jumper
wrote:
> On Wed, Jan 24, 2018 at 11:49 AM, wrote:
>
>> Did some more debugging. When we try to connect to a server that is FIPS
>> 140-2 compliant, here’s what the algorithms that are expected are:
>>
>>
>>
>> When I try to connect via a Guacamole SS
13 matches
Mail list logo
