[jira] [Comment Edited] (GUACAMOLE-1957) Permissions system behaving unexpectedly
[ https://issues.apache.org/jira/browse/GUACAMOLE-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17852054#comment-17852054 ] Nick Couchman edited comment on GUACAMOLE-1957 at 6/4/24 2:15 PM: -- [~shargan] There is a bit of nuance to this bug that I think is worth noting. Originally I did not think it was a bug at all, but a little investigation leads me to see what I think is actually at the core of it. However, I think it's important to clarify the ways in which the permissions system is working as designed: * Users who have the right to create connections, whether as System Administrators, or with the "Create Connections" permission, will be the "owner" of that connection, and will have administrative rights to it. This results in *four* permissions entries being created in the guacamole_connection_permission table for this user/connection pair: READ, UPDATE, DELETE, and ADMINISTER. * Removing the "System Administrator" or "Create Connections" (et al) rights does not - and should not - remove ownership of created connections or permissions to those connections. * The connections that the user created are shown at the bottom of the user administration page as connections for which that user has permissions. Again, all of those items are working as expected and intended. The only piece of this that I believe makes this a bug is that, when you clear the checkbox for that connection in the user administration page, only the "READ" permission is cleared from the database - the remaining entries, for UPDATE, DELETE, and ADMINISTER, are left in the database, resulting in the behavior you're seeing. This means that: * While the user cannot read the connection, and, so, cannot see it in the GUI, there is still a chance that the user would be able to update, delete, or otherwise affect it due to the fact that they retain other permissions to the connection. * If you add "READ" access back for the user, they will not only be able to read (use, connect to) the connection, they will also be able to update it. My opinion is that clearing the checkbox for the connection should clear *all* of the permissions in the database for the connection (or other object), not just the READ permission. However, this highlights another aspect of the permissions system, and that's that the GUI only manages a small subset of the permissions - for example, you cannot assign a user "Administer", "Update", or "Delete" permissions to a specific connection, connection group, etc., in the GUI - you have to manually create the entries in the database. There are some limitations to the current setup. In this case, this is a bug that stems from those (designed, or at least expected) limitations. was (Author: nick.couch...@yahoo.com): [~shargan] There is a bit of nuance to this bug that I think is worth noting. Originally I did not think it was a bug at all, but a little investigation leads me to see what I think is actually at the core of it. However, I think it's important to clarify the ways in which the permissions system is working as designed: * Users who have the right to create connections, whether as System Administrators, or with the "Create Connections" permission, will be the "owner" of that connection, and will have administrative rights to it. This results in *four* permissions entries being created in the guacamole_connection_permission table for this user/connection pair: READ, UPDATE, DELETE, and ADMINISTER. * Removing the "System Administrator" or "Create Connections" (et al) rights does not - and should not - remove ownership of created connections or permissions to those connections. * The connections that the user created are shown at the bottom of the user administration page as connections for which that user has permissions. Again, all of those items are working as expected and intended. The only piece of this that I believe makes this a bug is that, when you clear the checkbox for that connection in the user administration page, only the "READ" permission is cleared from the database - the remaining entries, for UPDATE, DELETE, and ADMINISTER, are left in the database, resulting in the behavior you're seeing. This means that: * While the user cannot read the connection, and, so, cannot see it in the GUI, there is still a chance that the user would be able to update, delete, or otherwise affect it due to the fact that they retain other permissions to the connection. * If you add "READ" access back for the user, they will not only be able to read (use, connect to) the connection, they will also be able to update it. My opinion is that clearing the checkbox for the connection should clear *all* of the permissions in the database for the connection (or other object), not just the READ permission. However, this highlights another aspect of the permissions system,
[jira] [Commented] (GUACAMOLE-1957) Permissions system behaving unexpectedly
[ https://issues.apache.org/jira/browse/GUACAMOLE-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17852054#comment-17852054 ] Nick Couchman commented on GUACAMOLE-1957: -- [~shargan] There is a bit of nuance to this bug that I think is worth noting. Originally I did not think it was a bug at all, but a little investigation leads me to see what I think is actually at the core of it. However, I think it's important to clarify the ways in which the permissions system is working as designed: * Users who have the right to create connections, whether as System Administrators, or with the "Create Connections" permission, will be the "owner" of that connection, and will have administrative rights to it. This results in *four* permissions entries being created in the guacamole_connection_permission table for this user/connection pair: READ, UPDATE, DELETE, and ADMINISTER. * Removing the "System Administrator" or "Create Connections" (et al) rights does not - and should not - remove ownership of created connections or permissions to those connections. * The connections that the user created are shown at the bottom of the user administration page as connections for which that user has permissions. Again, all of those items are working as expected and intended. The only piece of this that I believe makes this a bug is that, when you clear the checkbox for that connection in the user administration page, only the "READ" permission is cleared from the database - the remaining entries, for UPDATE, DELETE, and ADMINISTER, are left in the database, resulting in the behavior you're seeing. This means that: * While the user cannot read the connection, and, so, cannot see it in the GUI, there is still a chance that the user would be able to update, delete, or otherwise affect it due to the fact that they retain other permissions to the connection. * If you add "READ" access back for the user, they will not only be able to read (use, connect to) the connection, they will also be able to update it. My opinion is that clearing the checkbox for the connection should clear *all* of the permissions in the database for the connection (or other object), not just the READ permission. However, this highlights another aspect of the permissions system, and that's that the GUI only manages a small subset of the permissions - for example, you cannot assign a user "Administer", "Update", or "Delete" permissions to a specific connection, connection group, etc. There are some limitations to the current setup. In this case, this is a bug that stems from those (designed, or at least expected) limitations. > Permissions system behaving unexpectedly > > > Key: GUACAMOLE-1957 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1957 > Project: Guacamole > Issue Type: Bug >Affects Versions: 1.5.5 > Environment: Guacamole and guacd installed using official docker > images. >Reporter: Adam >Priority: Minor > > If an user have any administrative permissions assigned to him, either > directly or inherited from a group, and created anything using this > permissions (user, group, connection, etc.), he can make administrative > actions on these items even after administrative permissions are detached > from him directly or by removing from group from which these permissions were > inherited. > This effectively makes user a lifelong administrator of items he created, > even after this user does not have these permissions anymore. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GUACAMOLE-1957) Permissions system behaving unexpectedly
[ https://issues.apache.org/jira/browse/GUACAMOLE-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-1957: - Priority: Minor (was: Major) > Permissions system behaving unexpectedly > > > Key: GUACAMOLE-1957 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1957 > Project: Guacamole > Issue Type: Bug >Affects Versions: 1.5.5 > Environment: Guacamole and guacd installed using official docker > images. >Reporter: Adam >Priority: Minor > > If an user have any administrative permissions assigned to him, either > directly or inherited from a group, and created anything using this > permissions (user, group, connection, etc.), he can make administrative > actions on these items even after administrative permissions are detached > from him directly or by removing from group from which these permissions were > inherited. > This effectively makes user a lifelong administrator of items he created, > even after this user does not have these permissions anymore. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GUACAMOLE-1658) Unable to compile guacamole server with --enable-ssh-agent
[ https://issues.apache.org/jira/browse/GUACAMOLE-1658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17851752#comment-17851752 ] Nick Couchman commented on GUACAMOLE-1658: -- [~jlobov] : There isn't much detail to share at the moment - the fix is still being worked, but I have not had time lately to do much with it. > 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)
[jira] [Commented] (GUACAMOLE-1085) Consider migrating web application from AngularJS
[ https://issues.apache.org/jira/browse/GUACAMOLE-1085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17851599#comment-17851599 ] Nick Couchman commented on GUACAMOLE-1085: -- [~everflux] : While the PR is nearly a year old, Leonard continues to actively work on it, as he has time, I'm sure. There were commits pushed a recently as a few weeks ago, and he has a list of things he is working through that also gets updated periodically. > Consider migrating web application from AngularJS > - > > Key: GUACAMOLE-1085 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1085 > Project: Guacamole > Issue Type: Improvement > Components: guacamole >Reporter: Alfred Egger >Priority: Major > Fix For: 2.0.0 > > > [AngularJS is in an LTS period until June 30, > 2021|https://blog.angular.io/stable-angularjs-and-long-term-support-7e077635ee9c]. > Unless resurrected as a community-driven project, it will be cease being > maintained after that date. Assuming no such project surfaces, we should look > into migrate the web application to another framework. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GUACAMOLE-192) Allow selection of whole words by double-clicking
[
https://issues.apache.org/jira/browse/GUACAMOLE-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman updated GUACAMOLE-192:
Fix Version/s: 1.6.0
> Allow selection of whole words by double-clicking
> -
>
> Key: GUACAMOLE-192
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-192
> Project: Guacamole
> Issue Type: Improvement
> Components: Terminal
>Reporter: Mike Jumper
>Priority: Major
> Fix For: 1.6.0
>
>
> {panel:bgColor=#EE}
> *The description of this issue was copied from
> [GUAC-1060|https://glyptodon.org/jira/browse/GUAC-1060], an issue in the JIRA
> instance used by the Guacamole project prior to its acceptance into the
> Apache Incubator.*
> Comments, attachments, related issues, and history from prior to acceptance
> *have not been copied* and can be found instead at the original issue.
> {panel}
> When using SSH or telnet, users should be able to double-click on a word to
> select it, as in most text-based interfaces, rather than clicking and
> dragging over the entire word.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (GUACAMOLE-192) Allow selection of whole words by double-clicking
[
https://issues.apache.org/jira/browse/GUACAMOLE-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman closed GUACAMOLE-192.
---
Resolution: Implemented
> Allow selection of whole words by double-clicking
> -
>
> Key: GUACAMOLE-192
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-192
> Project: Guacamole
> Issue Type: Improvement
> Components: Terminal
>Reporter: Mike Jumper
>Priority: Major
> Fix For: 1.6.0
>
>
> {panel:bgColor=#EE}
> *The description of this issue was copied from
> [GUAC-1060|https://glyptodon.org/jira/browse/GUAC-1060], an issue in the JIRA
> instance used by the Guacamole project prior to its acceptance into the
> Apache Incubator.*
> Comments, attachments, related issues, and history from prior to acceptance
> *have not been copied* and can be found instead at the original issue.
> {panel}
> When using SSH or telnet, users should be able to double-click on a word to
> select it, as in most text-based interfaces, rather than clicking and
> dragging over the entire word.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (GUACAMOLE-1231) RemoteApp windows become inaccessible after being minimized
[ https://issues.apache.org/jira/browse/GUACAMOLE-1231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-1231: - Affects Version/s: (was: 1.2.0) > RemoteApp windows become inaccessible after being minimized > --- > > Key: GUACAMOLE-1231 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1231 > Project: Guacamole > Issue Type: Improvement > Components: RDP > Environment: web brower >Reporter: xiaoshengduan >Assignee: Nick Couchman >Priority: Minor > Fix For: 1.6.0 > > > When using remoteApp, when the application window is minimized, the normal > size cannot be restored, and the application icon cannot be found. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (GUACAMOLE-1231) RemoteApp windows become inaccessible after being minimized
[ https://issues.apache.org/jira/browse/GUACAMOLE-1231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman closed GUACAMOLE-1231. Resolution: Implemented > RemoteApp windows become inaccessible after being minimized > --- > > Key: GUACAMOLE-1231 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1231 > Project: Guacamole > Issue Type: Improvement > Components: RDP > Environment: web brower >Reporter: xiaoshengduan >Assignee: Nick Couchman >Priority: Minor > Fix For: 1.6.0 > > > When using remoteApp, when the application window is minimized, the normal > size cannot be restored, and the application icon cannot be found. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GUACAMOLE-1231) RemoteApp windows become inaccessible after being minimized
[ https://issues.apache.org/jira/browse/GUACAMOLE-1231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-1231: - Issue Type: Improvement (was: Bug) > RemoteApp windows become inaccessible after being minimized > --- > > Key: GUACAMOLE-1231 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1231 > Project: Guacamole > Issue Type: Improvement > Components: RDP >Affects Versions: 1.2.0 > Environment: web brower >Reporter: xiaoshengduan >Assignee: Nick Couchman >Priority: Minor > Fix For: 1.6.0 > > > When using remoteApp, when the application window is minimized, the normal > size cannot be restored, and the application icon cannot be found. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (GUACAMOLE-1952) Add support for FFmpeg 7.0
[ https://issues.apache.org/jira/browse/GUACAMOLE-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman closed GUACAMOLE-1952. Resolution: Implemented > Add support for FFmpeg 7.0 > -- > > Key: GUACAMOLE-1952 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1952 > Project: Guacamole > Issue Type: Task > Components: guacamole-server >Affects Versions: 1.5.5 >Reporter: Robert-André Mauchin >Priority: Minor > Labels: ffmpeg > Fix For: 1.6.0 > > > Currently, Guacamole-server can't be built with the new FFmpeg 7.0, as the > deprecated avcodec_close was removed in FFMPEG 7.0. > avcodec_close can be replaced with avcodec_free_context. > > PR will be sent on Github. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (GUACAMOLE-1084) Open a not published RemoteApp isn’t blocked
[ https://issues.apache.org/jira/browse/GUACAMOLE-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman closed GUACAMOLE-1084. Resolution: Fixed > Open a not published RemoteApp isn’t blocked > > > Key: GUACAMOLE-1084 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1084 > Project: Guacamole > Issue Type: Bug >Affects Versions: 1.1.0 > Environment: the RDS deployment is running on MS-Server 2016. >Reporter: Robert Bloch >Assignee: Nick Couchman >Priority: Minor > Fix For: 1.6.0 > > > If open a not published RemoteApp I get logged on and see blackscreen. > Expected behavior is an Error Message and direct logoff. We had that probem > in the passt with older version too. > In single freerdp cleint its working like expected. Error is there > [06:02:21:465] [2460:2466] [ERROR][com.freerdp.client.x11] - RAIL exec error: > execResult=RAIL_EXEC_E_NOT_IN_ALLOWLIST NtError=0x15 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GUACAMOLE-1084) Open a not published RemoteApp isn’t blocked
[ https://issues.apache.org/jira/browse/GUACAMOLE-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-1084: - Fix Version/s: 1.6.0 > Open a not published RemoteApp isn’t blocked > > > Key: GUACAMOLE-1084 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1084 > Project: Guacamole > Issue Type: Bug >Affects Versions: 1.1.0 > Environment: the RDS deployment is running on MS-Server 2016. >Reporter: Robert Bloch >Assignee: Nick Couchman >Priority: Minor > Fix For: 1.6.0 > > > If open a not published RemoteApp I get logged on and see blackscreen. > Expected behavior is an Error Message and direct logoff. We had that probem > in the passt with older version too. > In single freerdp cleint its working like expected. Error is there > [06:02:21:465] [2460:2466] [ERROR][com.freerdp.client.x11] - RAIL exec error: > execResult=RAIL_EXEC_E_NOT_IN_ALLOWLIST NtError=0x15 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (GUACAMOLE-1954) I try to connect ssh server, but don't work
[
https://issues.apache.org/jira/browse/GUACAMOLE-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman closed GUACAMOLE-1954.
Resolution: Invalid
> I try to connect ssh server, but don't work
> ---
>
> Key: GUACAMOLE-1954
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1954
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole-server, SSH
>Affects Versions: 1.5.5
> Environment: Rocky Linux 9.3
> Guacamole 1.5.5 [Manual Installation]
>Reporter: tzp
>Priority: Minor
>
> It's always not work in ssh connection , but in rdp connection is ok
>
> {code:java}
> //
> May 23 22:19:08 localhost guacd[1143614]: Guacamole proxy daemon (guacd)
> version 1.5.5 started
> May 23 22:19:08 localhost guacd[1143616]: Listening on host 0.0.0.0, port 4822
> May 23 22:21:23 localhost guacd[1143616]: Creating new client for protocol
> "ssh"
> May 23 22:21:23 localhost guacd[1143616]: Connection ID is
> "$8061380a-add0-444f-a048-3aaf32e4830b"
> May 23 22:21:23 localhost guacd[1145026]: User
> "@02a4654d-7cbf-44c1-baee-d89ee914b8f5" joined connection
> "$8061380a-add0-444f-a048-3aaf32e4830b" (1 users now present)
> May 23 22:21:23 localhost kernel: traps: guacd[1145032] trap divide error
> ip:7f5c90a10ed5 sp:7f5c8affaaf0 error:0 in
> libguac-terminal.so.0.1.0[7f5c90a0e000+e000]
> May 23 22:21:23 localhost systemd-coredump[1145040]: Resource limits disable
> core dumping for process 1145026 (guacd).
> May 23 22:21:23 localhost systemd-coredump[1145040]: Process 1145026 (guacd)
> of user 0 dumped core.
> May 23 22:21:23 localhost guacd[1143616]: Connection
> "$8061380a-add0-444f-a048-3aaf32e4830b" removed. {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Reopened] (GUACAMOLE-1954) I try to connect ssh server, but don't work
[
https://issues.apache.org/jira/browse/GUACAMOLE-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman reopened GUACAMOLE-1954:
--
> I try to connect ssh server, but don't work
> ---
>
> Key: GUACAMOLE-1954
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1954
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole-server, SSH
>Affects Versions: 1.5.5
> Environment: Rocky Linux 9.3
> Guacamole 1.5.5 [Manual Installation]
>Reporter: tzp
>Priority: Minor
> Fix For: 1.5.5
>
>
> It's always not work in ssh connection , but in rdp connection is ok
>
> {code:java}
> //
> May 23 22:19:08 localhost guacd[1143614]: Guacamole proxy daemon (guacd)
> version 1.5.5 started
> May 23 22:19:08 localhost guacd[1143616]: Listening on host 0.0.0.0, port 4822
> May 23 22:21:23 localhost guacd[1143616]: Creating new client for protocol
> "ssh"
> May 23 22:21:23 localhost guacd[1143616]: Connection ID is
> "$8061380a-add0-444f-a048-3aaf32e4830b"
> May 23 22:21:23 localhost guacd[1145026]: User
> "@02a4654d-7cbf-44c1-baee-d89ee914b8f5" joined connection
> "$8061380a-add0-444f-a048-3aaf32e4830b" (1 users now present)
> May 23 22:21:23 localhost kernel: traps: guacd[1145032] trap divide error
> ip:7f5c90a10ed5 sp:7f5c8affaaf0 error:0 in
> libguac-terminal.so.0.1.0[7f5c90a0e000+e000]
> May 23 22:21:23 localhost systemd-coredump[1145040]: Resource limits disable
> core dumping for process 1145026 (guacd).
> May 23 22:21:23 localhost systemd-coredump[1145040]: Process 1145026 (guacd)
> of user 0 dumped core.
> May 23 22:21:23 localhost guacd[1143616]: Connection
> "$8061380a-add0-444f-a048-3aaf32e4830b" removed. {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (GUACAMOLE-1954) I try to connect ssh server, but don't work
[
https://issues.apache.org/jira/browse/GUACAMOLE-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman updated GUACAMOLE-1954:
-
Fix Version/s: (was: 1.5.5)
> I try to connect ssh server, but don't work
> ---
>
> Key: GUACAMOLE-1954
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1954
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole-server, SSH
>Affects Versions: 1.5.5
> Environment: Rocky Linux 9.3
> Guacamole 1.5.5 [Manual Installation]
>Reporter: tzp
>Priority: Minor
>
> It's always not work in ssh connection , but in rdp connection is ok
>
> {code:java}
> //
> May 23 22:19:08 localhost guacd[1143614]: Guacamole proxy daemon (guacd)
> version 1.5.5 started
> May 23 22:19:08 localhost guacd[1143616]: Listening on host 0.0.0.0, port 4822
> May 23 22:21:23 localhost guacd[1143616]: Creating new client for protocol
> "ssh"
> May 23 22:21:23 localhost guacd[1143616]: Connection ID is
> "$8061380a-add0-444f-a048-3aaf32e4830b"
> May 23 22:21:23 localhost guacd[1145026]: User
> "@02a4654d-7cbf-44c1-baee-d89ee914b8f5" joined connection
> "$8061380a-add0-444f-a048-3aaf32e4830b" (1 users now present)
> May 23 22:21:23 localhost kernel: traps: guacd[1145032] trap divide error
> ip:7f5c90a10ed5 sp:7f5c8affaaf0 error:0 in
> libguac-terminal.so.0.1.0[7f5c90a0e000+e000]
> May 23 22:21:23 localhost systemd-coredump[1145040]: Resource limits disable
> core dumping for process 1145026 (guacd).
> May 23 22:21:23 localhost systemd-coredump[1145040]: Process 1145026 (guacd)
> of user 0 dumped core.
> May 23 22:21:23 localhost guacd[1143616]: Connection
> "$8061380a-add0-444f-a048-3aaf32e4830b" removed. {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Reopened] (GUACAMOLE-1686) extend wol-intelligence
[ https://issues.apache.org/jira/browse/GUACAMOLE-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman reopened GUACAMOLE-1686: -- Reopening to fix resource leak identified by Coverity. > extend wol-intelligence > --- > > Key: GUACAMOLE-1686 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1686 > Project: Guacamole > Issue Type: Wish > Components: guacamole >Reporter: Karsten >Assignee: Nick Couchman >Priority: Trivial > Fix For: 1.6.0 > > > It would be nice to make the wol-feature more flexible and intelligent: > > * wol-wait-time is appended to the connection process even if the machine is > running > * just try simple connect to the machine and only if this fails send a > wol-event and add the wol-wait-time to the whole process > With these little changes it would be less frustrating in reconnect-events to > not wait untill the wol-wait-time is over... -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GUACAMOLE-1954) I try to connect ssh server, but don't work
[
https://issues.apache.org/jira/browse/GUACAMOLE-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17849022#comment-17849022
]
Nick Couchman commented on GUACAMOLE-1954:
--
@tzp: You might try this:
[https://forums.rockylinux.org/t/how-to-enable-core-and-change-core-path/6422/6.]
Once you have the core dump file, you can use "gdb" to analyze it and get the
stack trace (bt):
https://stackoverflow.com/questions/5115613/core-dump-file-analysis
> I try to connect ssh server, but don't work
> ---
>
> Key: GUACAMOLE-1954
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1954
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole-server, SSH
>Affects Versions: 1.5.5
> Environment: Rocky Linux 9.3
> Guacamole 1.5.5 [Manual Installation]
>Reporter: tzp
>Priority: Minor
>
> It's always not work in ssh connection , but in rdp connection is ok
>
> {code:java}
> //
> May 23 22:19:08 localhost guacd[1143614]: Guacamole proxy daemon (guacd)
> version 1.5.5 started
> May 23 22:19:08 localhost guacd[1143616]: Listening on host 0.0.0.0, port 4822
> May 23 22:21:23 localhost guacd[1143616]: Creating new client for protocol
> "ssh"
> May 23 22:21:23 localhost guacd[1143616]: Connection ID is
> "$8061380a-add0-444f-a048-3aaf32e4830b"
> May 23 22:21:23 localhost guacd[1145026]: User
> "@02a4654d-7cbf-44c1-baee-d89ee914b8f5" joined connection
> "$8061380a-add0-444f-a048-3aaf32e4830b" (1 users now present)
> May 23 22:21:23 localhost kernel: traps: guacd[1145032] trap divide error
> ip:7f5c90a10ed5 sp:7f5c8affaaf0 error:0 in
> libguac-terminal.so.0.1.0[7f5c90a0e000+e000]
> May 23 22:21:23 localhost systemd-coredump[1145040]: Resource limits disable
> core dumping for process 1145026 (guacd).
> May 23 22:21:23 localhost systemd-coredump[1145040]: Process 1145026 (guacd)
> of user 0 dumped core.
> May 23 22:21:23 localhost guacd[1143616]: Connection
> "$8061380a-add0-444f-a048-3aaf32e4830b" removed. {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (GUACAMOLE-1954) I try to connect ssh server, but don't work
[
https://issues.apache.org/jira/browse/GUACAMOLE-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman updated GUACAMOLE-1954:
-
Flags: (was: Important)
> I try to connect ssh server, but don't work
> ---
>
> Key: GUACAMOLE-1954
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1954
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole-server, SSH
>Affects Versions: 1.5.5
> Environment: Rocky Linux 9.3
> Guacamole 1.5.5 [Manual Installation]
>Reporter: tzp
>Priority: Minor
>
> It's always not work in ssh connection , but in rdp connection is ok
>
> {code:java}
> //
> May 23 22:19:08 localhost guacd[1143614]: Guacamole proxy daemon (guacd)
> version 1.5.5 started
> May 23 22:19:08 localhost guacd[1143616]: Listening on host 0.0.0.0, port 4822
> May 23 22:21:23 localhost guacd[1143616]: Creating new client for protocol
> "ssh"
> May 23 22:21:23 localhost guacd[1143616]: Connection ID is
> "$8061380a-add0-444f-a048-3aaf32e4830b"
> May 23 22:21:23 localhost guacd[1145026]: User
> "@02a4654d-7cbf-44c1-baee-d89ee914b8f5" joined connection
> "$8061380a-add0-444f-a048-3aaf32e4830b" (1 users now present)
> May 23 22:21:23 localhost kernel: traps: guacd[1145032] trap divide error
> ip:7f5c90a10ed5 sp:7f5c8affaaf0 error:0 in
> libguac-terminal.so.0.1.0[7f5c90a0e000+e000]
> May 23 22:21:23 localhost systemd-coredump[1145040]: Resource limits disable
> core dumping for process 1145026 (guacd).
> May 23 22:21:23 localhost systemd-coredump[1145040]: Process 1145026 (guacd)
> of user 0 dumped core.
> May 23 22:21:23 localhost guacd[1143616]: Connection
> "$8061380a-add0-444f-a048-3aaf32e4830b" removed. {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (GUACAMOLE-1954) I try to connect ssh server, but don't work
[
https://issues.apache.org/jira/browse/GUACAMOLE-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17849009#comment-17849009
]
Nick Couchman commented on GUACAMOLE-1954:
--
[~阿杜不在车底] In order to further debug this crash to figure out if it is a bug,
and what's causing it, we'll need the stack trace from the core dump mentioned
in the error you posted above.
> I try to connect ssh server, but don't work
> ---
>
> Key: GUACAMOLE-1954
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1954
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole-server, SSH
>Affects Versions: 1.5.5
> Environment: Rocky Linux 9.3
> Guacamole 1.5.5 [Manual Installation]
>Reporter: tzp
>Priority: Minor
>
> It's always not work in ssh connection , but in rdp connection is ok
>
> {code:java}
> //
> May 23 22:19:08 localhost guacd[1143614]: Guacamole proxy daemon (guacd)
> version 1.5.5 started
> May 23 22:19:08 localhost guacd[1143616]: Listening on host 0.0.0.0, port 4822
> May 23 22:21:23 localhost guacd[1143616]: Creating new client for protocol
> "ssh"
> May 23 22:21:23 localhost guacd[1143616]: Connection ID is
> "$8061380a-add0-444f-a048-3aaf32e4830b"
> May 23 22:21:23 localhost guacd[1145026]: User
> "@02a4654d-7cbf-44c1-baee-d89ee914b8f5" joined connection
> "$8061380a-add0-444f-a048-3aaf32e4830b" (1 users now present)
> May 23 22:21:23 localhost kernel: traps: guacd[1145032] trap divide error
> ip:7f5c90a10ed5 sp:7f5c8affaaf0 error:0 in
> libguac-terminal.so.0.1.0[7f5c90a0e000+e000]
> May 23 22:21:23 localhost systemd-coredump[1145040]: Resource limits disable
> core dumping for process 1145026 (guacd).
> May 23 22:21:23 localhost systemd-coredump[1145040]: Process 1145026 (guacd)
> of user 0 dumped core.
> May 23 22:21:23 localhost guacd[1143616]: Connection
> "$8061380a-add0-444f-a048-3aaf32e4830b" removed. {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (GUACAMOLE-1954) I try to connect ssh server, but don't work
[
https://issues.apache.org/jira/browse/GUACAMOLE-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman updated GUACAMOLE-1954:
-
Priority: Minor (was: Blocker)
> I try to connect ssh server, but don't work
> ---
>
> Key: GUACAMOLE-1954
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1954
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole-server, SSH
>Affects Versions: 1.5.5
> Environment: Rocky Linux 9.3
> Guacamole 1.5.5 [Manual Installation]
>Reporter: tzp
>Priority: Minor
>
> It's always not work in ssh connection , but in rdp connection is ok
>
> {code:java}
> //
> May 23 22:19:08 localhost guacd[1143614]: Guacamole proxy daemon (guacd)
> version 1.5.5 started
> May 23 22:19:08 localhost guacd[1143616]: Listening on host 0.0.0.0, port 4822
> May 23 22:21:23 localhost guacd[1143616]: Creating new client for protocol
> "ssh"
> May 23 22:21:23 localhost guacd[1143616]: Connection ID is
> "$8061380a-add0-444f-a048-3aaf32e4830b"
> May 23 22:21:23 localhost guacd[1145026]: User
> "@02a4654d-7cbf-44c1-baee-d89ee914b8f5" joined connection
> "$8061380a-add0-444f-a048-3aaf32e4830b" (1 users now present)
> May 23 22:21:23 localhost kernel: traps: guacd[1145032] trap divide error
> ip:7f5c90a10ed5 sp:7f5c8affaaf0 error:0 in
> libguac-terminal.so.0.1.0[7f5c90a0e000+e000]
> May 23 22:21:23 localhost systemd-coredump[1145040]: Resource limits disable
> core dumping for process 1145026 (guacd).
> May 23 22:21:23 localhost systemd-coredump[1145040]: Process 1145026 (guacd)
> of user 0 dumped core.
> May 23 22:21:23 localhost guacd[1143616]: Connection
> "$8061380a-add0-444f-a048-3aaf32e4830b" removed. {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (GUACAMOLE-1686) extend wol-intelligence
[ https://issues.apache.org/jira/browse/GUACAMOLE-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman closed GUACAMOLE-1686. Resolution: Implemented > extend wol-intelligence > --- > > Key: GUACAMOLE-1686 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1686 > Project: Guacamole > Issue Type: Wish > Components: guacamole >Reporter: Karsten >Assignee: Nick Couchman >Priority: Trivial > Fix For: 1.6.0 > > > It would be nice to make the wol-feature more flexible and intelligent: > > * wol-wait-time is appended to the connection process even if the machine is > running > * just try simple connect to the machine and only if this fails send a > wol-event and add the wol-wait-time to the whole process > With these little changes it would be less frustrating in reconnect-events to > not wait untill the wol-wait-time is over... -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (GUACAMOLE-1004) Some keyboard input is not passed to the RDP server.
[ https://issues.apache.org/jira/browse/GUACAMOLE-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman closed GUACAMOLE-1004. Resolution: Duplicate [~tanakakz] This is a duplicate of GUACAMOLE-520 - please reference that issue, instead. > Some keyboard input is not passed to the RDP server. > > > Key: GUACAMOLE-1004 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1004 > Project: Guacamole > Issue Type: Bug >Reporter: Kazuhiko Tanaka >Priority: Minor > > I entered the "Zenkaku_Hankaku" key, "Capslock" key, and "Hiragana" key, > but they were not passed to the RDP server. > Entering these keys affects the browser's IME. Perhaps Guacamole does > not handle these keys properly. > If enter the "Zenkaku_Hankaku" key in a Japanese browser, "Zenkaku (keyup > 243 and keydown 244)" and "Hankaku (keyup 244 and keydown 243)" will be > entered alternately, so you need to obtain both. > Also, when the text area was selected, JavaScript could not get "keydown" > and only get "keyup" in some cases. This may also be relevant. > In particular, the "Zenkaku_Hankaku" key is a very important key for OS > in Japanese environment. If the "Zenkaku_Hankaku" key cannot be entered, > nothing can be done. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GUACAMOLE-1026) Add support for FreeRDP 3.0.0
[
https://issues.apache.org/jira/browse/GUACAMOLE-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman updated GUACAMOLE-1026:
-
Fix Version/s: 1.6.0
> Add support for FreeRDP 3.0.0
> -
>
> Key: GUACAMOLE-1026
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1026
> Project: Guacamole
> Issue Type: Improvement
> Components: RDP
>Reporter: Mike Jumper
>Priority: Major
> Fix For: 1.6.0
>
>
> The nightly CI build testing that guacamole-server builds against the FreeRDP
> {{master}} branch started failing on 2020-04-10 due to the version bump to
> 3.0.0. It's currently unclear whether the API has changed, as well.
> The guacamole-server build should be adjusted such that it recognizes FreeRDP
> 3.0.0. If further code changes are necessary for this to work, those changes
> should probably also be made now before things get too hairy.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (GUACAMOLE-1951) Improve RemoteApp Handling of Multiple Applications
Nick Couchman created GUACAMOLE-1951: Summary: Improve RemoteApp Handling of Multiple Applications Key: GUACAMOLE-1951 URL: https://issues.apache.org/jira/browse/GUACAMOLE-1951 Project: Guacamole Issue Type: Improvement Components: RDP Reporter: Nick Couchman The way RemoteApp connections are currently handled by Guacamole fails to take advantage of the fact that multiple applications can be opened with the same RDP connection, and thus causes some less-than-ideal behavior if you, for example, try to open multiple applications on the same RDP server. Currently, Guacamole will attempt a new RDP connection to the same server to launch the application. This can result in: * The initial connection being terminated by the RDP server (in the case where the RDP server enforces a single connection per user), OR... * ...extra resources being allocated for each login in the case where the RDP server allows users to log in multiple times. * The new connection that is opened containing both of the applications that you have launched, but not necessarily activating the correct application (it may be behind another one on the desktop. In order to improve Remote App (RAIL) support in Guacamole, we probably need to do a few things: * Track connections to a RDP host based on server, port, username, and domain name. * Implement a mechanism for safely and securely re-use existing RDP connections to launch additional applications on the same server. * Track the RAIL windows open on a given connection, and close down the RDP connection when the last window is closed * And probably other things... -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (GUACAMOLE-1948) Provide a comprehensive error message for input exceeding database column
[ https://issues.apache.org/jira/browse/GUACAMOLE-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman closed GUACAMOLE-1948. Resolution: Implemented > Provide a comprehensive error message for input exceeding database column > - > > Key: GUACAMOLE-1948 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1948 > Project: Guacamole > Issue Type: Improvement > Components: guacamole-auth-jdbc >Reporter: Alexander Leitner >Priority: Trivial > Fix For: 1.6.0 > > > A large input value for any parameter results in a generic error message. > This is because a provided input exceeds the connection parameter column size > in Guacamole's database is (4096 characters) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GUACAMOLE-1948) Provide a comprehensive error message for input exceeding database column
[ https://issues.apache.org/jira/browse/GUACAMOLE-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-1948: - Affects Version/s: (was: 1.5.5) > Provide a comprehensive error message for input exceeding database column > - > > Key: GUACAMOLE-1948 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1948 > Project: Guacamole > Issue Type: Improvement > Components: guacamole-auth-jdbc >Reporter: Alexander Leitner >Priority: Trivial > > A large input value for any parameter results in a generic error message. > This is because a provided input exceeds the connection parameter column size > in Guacamole's database is (4096 characters) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GUACAMOLE-1948) Provide a comprehensive error message for input exceeding database column
[ https://issues.apache.org/jira/browse/GUACAMOLE-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-1948: - Fix Version/s: 1.6.0 > Provide a comprehensive error message for input exceeding database column > - > > Key: GUACAMOLE-1948 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1948 > Project: Guacamole > Issue Type: Improvement > Components: guacamole-auth-jdbc >Reporter: Alexander Leitner >Priority: Trivial > Fix For: 1.6.0 > > > A large input value for any parameter results in a generic error message. > This is because a provided input exceeds the connection parameter column size > in Guacamole's database is (4096 characters) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (GUACAMOLE-1950) Alpine 3.18 docker build issue
[
https://issues.apache.org/jira/browse/GUACAMOLE-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman reopened GUACAMOLE-1950:
--
> Alpine 3.18 docker build issue
> --
>
> Key: GUACAMOLE-1950
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1950
> Project: Guacamole
> Issue Type: Test
> Components: guacamole-server
>Affects Versions: 1.5.5
> Environment: Centos 5.10.6-1.el7.elrepo.x86_64
>Reporter: murat
>Priority: Major
>
> Building FreeRDP @ 2.11.7 ...
> HEAD is now at 7f6cc93c2 release-2.11.7
> CMake Deprecation Warning at CMakeLists.txt:21 (cmake_minimum_required):
> Compatibility with CMake < 2.8.12 will be removed from a future version of
> CMake.
> Update the VERSION argument value or use a ... suffix to tell
> CMake that the project does not need compatibility with older versions.
> -- The C compiler identification is GNU 12.2.1
> -- The CXX compiler identification is GNU 12.2.1
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - failed
> -- Check for working C compiler: /usr/bin/cc
> -- Check for working C compiler: /usr/bin/cc - broken
> CMake Error at /usr/share/cmake/Modules/CMakeTestCCompiler.cmake:67 (message):
> The C compiler
> "/usr/bin/cc"
> is not able to compile a simple test program.
> It fails with the following output:
> Change Dir: /tmp/FreeRDP/CMakeFiles/CMakeScratch/TryCompile-bnhdfi
>
> Run Build Command(s):/usr/bin/cmake -E env VERBOSE=1 /usr/bin/make -f
> Makefile cmTC_eff9c/fast && /usr/bin/make -f
> CMakeFiles/cmTC_eff9c.dir/build.make CMakeFiles/cmTC_eff9c.dir/build
> make: /usr/bin/make: Operation not permitted
> make: *** [Makefile:127: cmTC_eff9c/fast] Error 127
>
>
>
> CMake will not be able to correctly generate this project.
> Call Stack (most recent call first):
> CMakeLists.txt:23 (project)
> -- Configuring incomplete, errors occurred!
> The command '/bin/sh -c ${BUILD_DIR}/src/guacd-docker/bin/build-all.sh'
> returned a non-zero code: 1
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (GUACAMOLE-1950) Alpine 3.18 docker build issue
[
https://issues.apache.org/jira/browse/GUACAMOLE-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman closed GUACAMOLE-1950.
Resolution: Invalid
> Alpine 3.18 docker build issue
> --
>
> Key: GUACAMOLE-1950
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1950
> Project: Guacamole
> Issue Type: Test
> Components: guacamole-server
>Affects Versions: 1.5.5
> Environment: Centos 5.10.6-1.el7.elrepo.x86_64
>Reporter: murat
>Priority: Major
>
> Building FreeRDP @ 2.11.7 ...
> HEAD is now at 7f6cc93c2 release-2.11.7
> CMake Deprecation Warning at CMakeLists.txt:21 (cmake_minimum_required):
> Compatibility with CMake < 2.8.12 will be removed from a future version of
> CMake.
> Update the VERSION argument value or use a ... suffix to tell
> CMake that the project does not need compatibility with older versions.
> -- The C compiler identification is GNU 12.2.1
> -- The CXX compiler identification is GNU 12.2.1
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - failed
> -- Check for working C compiler: /usr/bin/cc
> -- Check for working C compiler: /usr/bin/cc - broken
> CMake Error at /usr/share/cmake/Modules/CMakeTestCCompiler.cmake:67 (message):
> The C compiler
> "/usr/bin/cc"
> is not able to compile a simple test program.
> It fails with the following output:
> Change Dir: /tmp/FreeRDP/CMakeFiles/CMakeScratch/TryCompile-bnhdfi
>
> Run Build Command(s):/usr/bin/cmake -E env VERBOSE=1 /usr/bin/make -f
> Makefile cmTC_eff9c/fast && /usr/bin/make -f
> CMakeFiles/cmTC_eff9c.dir/build.make CMakeFiles/cmTC_eff9c.dir/build
> make: /usr/bin/make: Operation not permitted
> make: *** [Makefile:127: cmTC_eff9c/fast] Error 127
>
>
>
> CMake will not be able to correctly generate this project.
> Call Stack (most recent call first):
> CMakeLists.txt:23 (project)
> -- Configuring incomplete, errors occurred!
> The command '/bin/sh -c ${BUILD_DIR}/src/guacd-docker/bin/build-all.sh'
> returned a non-zero code: 1
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (GUACAMOLE-1719) Correct autoconf issues that result in odd build results
[
https://issues.apache.org/jira/browse/GUACAMOLE-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman resolved GUACAMOLE-1719.
--
Fix Version/s: 1.6.0
Resolution: Fixed
> Correct autoconf issues that result in odd build results
>
>
> Key: GUACAMOLE-1719
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1719
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole
>Affects Versions: 1.4.0
>Reporter: Libor Svehlak
>Assignee: Nick Couchman
>Priority: Major
> Fix For: 1.6.0
>
> Attachments: configure-output.log
>
>
> Documentation at
> [https://guacamole.apache.org/doc/gug/installing-guacamole.html] specifies
> that {{libavcodec}} is needed only when {{guacenc}} is required. Nevertheless
> when {{--with-libavcodec=no}} is specified in {{configure}} script it is
> causing that protocols RDP, SSH, Telnet are not supported.
> Prerequisite: All required packages for RDP, SSH, Telnet, VNC are installed:
> Steps to reproduce:
> {noformat}
> tar -xzf guacamole-server-1.4.0.tar.gz
> cd guacamole-server-1.4.0
> ./configure --with-libavformat=no
> {noformat}
> Output:
> {noformat}
>
> guacamole-server version 1.4.0
>
>Library status:
> freerdp2 no
> pango ... no
> libavcodec .. disabled
> libavformat.. no
> libavutil ... no
> libssh2 . yes
> libssl .. yes
> libswscale .. no
> libtelnet ... yes
> libVNCServer yes
> libvorbis ... yes
> libpulse no
> libwebsockets ... no
> libwebp . yes
> wsock32 . no
>Protocol support:
> Kubernetes no
> RDP ... no
> SSH ... no
> Telnet no
> VNC ... yes
>Services / tools:
> guacd .. yes
> guacenc no
> guaclog yes
>FreeRDP plugins: no
>Init scripts: no
>Systemd units: no
> Type "make" to compile guacamole-server.
> {noformat}
> Without the explicit specification of {{{}--with-libavformat=no{}}}:
> {noformat}
> tar -xzf guacamole-server-1.4.0.tar.gz
> cd guacamole-server-1.4.0
> ./configure
> {noformat}
> Output:
> {noformat}
>
> guacamole-server version 1.4.0
>
>Library status:
> freerdp2 yes
> pango ... yes
> libavcodec .. no
> libavformat.. no
> libavutil ... no
> libssh2 . yes
> libssl .. yes
> libswscale .. no
> libtelnet ... yes
> libVNCServer yes
> libvorbis ... yes
> libpulse no
> libwebsockets ... no
> libwebp . yes
> wsock32 . no
>Protocol support:
> Kubernetes no
> RDP ... yes
> SSH ... yes
> Telnet yes
> VNC ... yes
>Services / tools:
> guacd .. yes
> guacenc no
> guaclog yes
>FreeRDP plugins: /usr/lib64/freerdp2
>Init scripts: no
>Systemd units: no
> Type "make" to compile guacamole-server.
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (GUACAMOLE-1718) Configure script fails when "--with-libavformat=no" is specified
[
https://issues.apache.org/jira/browse/GUACAMOLE-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman closed GUACAMOLE-1718.
Resolution: Duplicate
> Configure script fails when "--with-libavformat=no" is specified
>
>
> Key: GUACAMOLE-1718
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1718
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole-server
>Affects Versions: 1.5.3
>Reporter: Libor Svehlak
>Assignee: Mike Jumper
>Priority: Minor
>
> Steps to reproduce:
> {noformat}
> tar -xzf guacamole-server-1.5.3.tar.gz
> cd guacamole-server-1.5.3
> ./configure --with-libavformat=no
> {noformat}
> Output:
> {noformat}
>
> checking for ssize_t... yes
> checking for pkg-config... /usr/bin/pkg-config
> checking pkg-config is at least version 0.9.0... yes
> checking for AVCODEC... no
> ./configure: line 15051: .: filename argument required
> .: usage: . filename [arguments] {noformat}
> Reason: There seems to be a typo in {{configure.ac}} file on the line 251
> (line 15051 in generated {{configure}} script provided in the source
> package). There is specified {{[].}} instead of the correct {{{}[],{}}}:
> {noformat}
> #
> # libavformat
> #
> have_libavformat=disabled
> AC_ARG_WITH([libavformat],
> [AS_HELP_STRING([--with-libavformat],
> [use libavformat when encoding video
> @<:@default=check@:>@])],
> [].
> [with_libavformat=check])
> if test "x$with_libavformat" != "xno"
> then
> have_libavformat=yes
> PKG_CHECK_MODULES([AVFORMAT], [libavformat],, [have_libavformat=no]);
> fi
> {noformat}
> Side question / suggestion for enhancement: Isn't there a build & test
> infrastructure to test that at least specification of switches (combination
> of switches) are not causing build errors? Due to large test space (amount of
> switches and their values) it would be most probably impossible to test all
> combinations nevertheless at least a basic check (e.g. nothing provided, all
> switches provided with "no" value, etc.) can help to avoid such errors in the
> future.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (GUACAMOLE-1719) Correct autoconf issues that result in odd build results
[
https://issues.apache.org/jira/browse/GUACAMOLE-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman updated GUACAMOLE-1719:
-
Summary: Correct autoconf issues that result in odd build results (was:
Protocols RDP, SSH, Telnet are not supported when "--with-libavcodec=no" is
specified in configure script)
> Correct autoconf issues that result in odd build results
>
>
> Key: GUACAMOLE-1719
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1719
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole
>Affects Versions: 1.4.0
>Reporter: Libor Svehlak
>Assignee: Nick Couchman
>Priority: Major
> Attachments: configure-output.log
>
>
> Documentation at
> [https://guacamole.apache.org/doc/gug/installing-guacamole.html] specifies
> that {{libavcodec}} is needed only when {{guacenc}} is required. Nevertheless
> when {{--with-libavcodec=no}} is specified in {{configure}} script it is
> causing that protocols RDP, SSH, Telnet are not supported.
> Prerequisite: All required packages for RDP, SSH, Telnet, VNC are installed:
> Steps to reproduce:
> {noformat}
> tar -xzf guacamole-server-1.4.0.tar.gz
> cd guacamole-server-1.4.0
> ./configure --with-libavformat=no
> {noformat}
> Output:
> {noformat}
>
> guacamole-server version 1.4.0
>
>Library status:
> freerdp2 no
> pango ... no
> libavcodec .. disabled
> libavformat.. no
> libavutil ... no
> libssh2 . yes
> libssl .. yes
> libswscale .. no
> libtelnet ... yes
> libVNCServer yes
> libvorbis ... yes
> libpulse no
> libwebsockets ... no
> libwebp . yes
> wsock32 . no
>Protocol support:
> Kubernetes no
> RDP ... no
> SSH ... no
> Telnet no
> VNC ... yes
>Services / tools:
> guacd .. yes
> guacenc no
> guaclog yes
>FreeRDP plugins: no
>Init scripts: no
>Systemd units: no
> Type "make" to compile guacamole-server.
> {noformat}
> Without the explicit specification of {{{}--with-libavformat=no{}}}:
> {noformat}
> tar -xzf guacamole-server-1.4.0.tar.gz
> cd guacamole-server-1.4.0
> ./configure
> {noformat}
> Output:
> {noformat}
>
> guacamole-server version 1.4.0
>
>Library status:
> freerdp2 yes
> pango ... yes
> libavcodec .. no
> libavformat.. no
> libavutil ... no
> libssh2 . yes
> libssl .. yes
> libswscale .. no
> libtelnet ... yes
> libVNCServer yes
> libvorbis ... yes
> libpulse no
> libwebsockets ... no
> libwebp . yes
> wsock32 . no
>Protocol support:
> Kubernetes no
> RDP ... yes
> SSH ... yes
> Telnet yes
> VNC ... yes
>Services / tools:
> guacd .. yes
> guacenc no
> guaclog yes
>FreeRDP plugins: /usr/lib64/freerdp2
>Init scripts: no
>Systemd units: no
> Type "make" to compile guacamole-server.
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (GUACAMOLE-1719) Protocols RDP, SSH, Telnet are not supported when "--with-libavcodec=no" is specified in configure script
[
https://issues.apache.org/jira/browse/GUACAMOLE-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman reassigned GUACAMOLE-1719:
Assignee: Nick Couchman
> Protocols RDP, SSH, Telnet are not supported when "--with-libavcodec=no" is
> specified in configure script
> -
>
> Key: GUACAMOLE-1719
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1719
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole
>Affects Versions: 1.4.0
>Reporter: Libor Svehlak
>Assignee: Nick Couchman
>Priority: Major
> Attachments: configure-output.log
>
>
> Documentation at
> [https://guacamole.apache.org/doc/gug/installing-guacamole.html] specifies
> that {{libavcodec}} is needed only when {{guacenc}} is required. Nevertheless
> when {{--with-libavcodec=no}} is specified in {{configure}} script it is
> causing that protocols RDP, SSH, Telnet are not supported.
> Prerequisite: All required packages for RDP, SSH, Telnet, VNC are installed:
> Steps to reproduce:
> {noformat}
> tar -xzf guacamole-server-1.4.0.tar.gz
> cd guacamole-server-1.4.0
> ./configure --with-libavformat=no
> {noformat}
> Output:
> {noformat}
>
> guacamole-server version 1.4.0
>
>Library status:
> freerdp2 no
> pango ... no
> libavcodec .. disabled
> libavformat.. no
> libavutil ... no
> libssh2 . yes
> libssl .. yes
> libswscale .. no
> libtelnet ... yes
> libVNCServer yes
> libvorbis ... yes
> libpulse no
> libwebsockets ... no
> libwebp . yes
> wsock32 . no
>Protocol support:
> Kubernetes no
> RDP ... no
> SSH ... no
> Telnet no
> VNC ... yes
>Services / tools:
> guacd .. yes
> guacenc no
> guaclog yes
>FreeRDP plugins: no
>Init scripts: no
>Systemd units: no
> Type "make" to compile guacamole-server.
> {noformat}
> Without the explicit specification of {{{}--with-libavformat=no{}}}:
> {noformat}
> tar -xzf guacamole-server-1.4.0.tar.gz
> cd guacamole-server-1.4.0
> ./configure
> {noformat}
> Output:
> {noformat}
>
> guacamole-server version 1.4.0
>
>Library status:
> freerdp2 yes
> pango ... yes
> libavcodec .. no
> libavformat.. no
> libavutil ... no
> libssh2 . yes
> libssl .. yes
> libswscale .. no
> libtelnet ... yes
> libVNCServer yes
> libvorbis ... yes
> libpulse no
> libwebsockets ... no
> libwebp . yes
> wsock32 . no
>Protocol support:
> Kubernetes no
> RDP ... yes
> SSH ... yes
> Telnet yes
> VNC ... yes
>Services / tools:
> guacd .. yes
> guacenc no
> guaclog yes
>FreeRDP plugins: /usr/lib64/freerdp2
>Init scripts: no
>Systemd units: no
> Type "make" to compile guacamole-server.
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (GUACAMOLE-1719) Protocols RDP, SSH, Telnet are not supported when "--with-libavcodec=no" is specified in configure script
[
https://issues.apache.org/jira/browse/GUACAMOLE-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841138#comment-17841138
]
Nick Couchman commented on GUACAMOLE-1719:
--
Thank you [~libor.svehlak] !
> Protocols RDP, SSH, Telnet are not supported when "--with-libavcodec=no" is
> specified in configure script
> -
>
> Key: GUACAMOLE-1719
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1719
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole
>Affects Versions: 1.4.0
>Reporter: Libor Svehlak
>Priority: Major
> Attachments: configure-output.log
>
>
> Documentation at
> [https://guacamole.apache.org/doc/gug/installing-guacamole.html] specifies
> that {{libavcodec}} is needed only when {{guacenc}} is required. Nevertheless
> when {{--with-libavcodec=no}} is specified in {{configure}} script it is
> causing that protocols RDP, SSH, Telnet are not supported.
> Prerequisite: All required packages for RDP, SSH, Telnet, VNC are installed:
> Steps to reproduce:
> {noformat}
> tar -xzf guacamole-server-1.4.0.tar.gz
> cd guacamole-server-1.4.0
> ./configure --with-libavformat=no
> {noformat}
> Output:
> {noformat}
>
> guacamole-server version 1.4.0
>
>Library status:
> freerdp2 no
> pango ... no
> libavcodec .. disabled
> libavformat.. no
> libavutil ... no
> libssh2 . yes
> libssl .. yes
> libswscale .. no
> libtelnet ... yes
> libVNCServer yes
> libvorbis ... yes
> libpulse no
> libwebsockets ... no
> libwebp . yes
> wsock32 . no
>Protocol support:
> Kubernetes no
> RDP ... no
> SSH ... no
> Telnet no
> VNC ... yes
>Services / tools:
> guacd .. yes
> guacenc no
> guaclog yes
>FreeRDP plugins: no
>Init scripts: no
>Systemd units: no
> Type "make" to compile guacamole-server.
> {noformat}
> Without the explicit specification of {{{}--with-libavformat=no{}}}:
> {noformat}
> tar -xzf guacamole-server-1.4.0.tar.gz
> cd guacamole-server-1.4.0
> ./configure
> {noformat}
> Output:
> {noformat}
>
> guacamole-server version 1.4.0
>
>Library status:
> freerdp2 yes
> pango ... yes
> libavcodec .. no
> libavformat.. no
> libavutil ... no
> libssh2 . yes
> libssl .. yes
> libswscale .. no
> libtelnet ... yes
> libVNCServer yes
> libvorbis ... yes
> libpulse no
> libwebsockets ... no
> libwebp . yes
> wsock32 . no
>Protocol support:
> Kubernetes no
> RDP ... yes
> SSH ... yes
> Telnet yes
> VNC ... yes
>Services / tools:
> guacd .. yes
> guacenc no
> guaclog yes
>FreeRDP plugins: /usr/lib64/freerdp2
>Init scripts: no
>Systemd units: no
> Type "make" to compile guacamole-server.
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (GUACAMOLE-1719) Protocols RDP, SSH, Telnet are not supported when "--with-libavcodec=no" is specified in configure script
[
https://issues.apache.org/jira/browse/GUACAMOLE-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17840970#comment-17840970
]
Nick Couchman commented on GUACAMOLE-1719:
--
Well, I've managed to find and correct one issue in the code related to the
build, but the --with-libavcodec=no issue is just stumping me completely.
{code}
- [AS_HELP_STRING([--with-libavformat],
- [use libavformat when encoding video
@<:@default=check@:>@])],
-[].
+[AS_HELP_STRING([--with-libavformat],
+[use libavformat when encoding video
@<:@default=check@:>@])],
+[],
[with_libavformat=check])
+
{code}
There was a "." (period) instead of a "," (comma) on one of the lines that was
causing the issues with libavformat. The libavcodec one is just completely
puzzling me - there must be some quote or bracket that's getting open and not
closed or something like that, but I cannot, for the life of me, figure out
where it is.
> Protocols RDP, SSH, Telnet are not supported when "--with-libavcodec=no" is
> specified in configure script
> -
>
> Key: GUACAMOLE-1719
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1719
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole
>Affects Versions: 1.4.0
>Reporter: Libor Svehlak
>Priority: Major
> Attachments: configure-output.log
>
>
> Documentation at
> [https://guacamole.apache.org/doc/gug/installing-guacamole.html] specifies
> that {{libavcodec}} is needed only when {{guacenc}} is required. Nevertheless
> when {{--with-libavcodec=no}} is specified in {{configure}} script it is
> causing that protocols RDP, SSH, Telnet are not supported.
> Prerequisite: All required packages for RDP, SSH, Telnet, VNC are installed:
> Steps to reproduce:
> {noformat}
> tar -xzf guacamole-server-1.4.0.tar.gz
> cd guacamole-server-1.4.0
> ./configure --with-libavformat=no
> {noformat}
> Output:
> {noformat}
>
> guacamole-server version 1.4.0
>
>Library status:
> freerdp2 no
> pango ... no
> libavcodec .. disabled
> libavformat.. no
> libavutil ... no
> libssh2 . yes
> libssl .. yes
> libswscale .. no
> libtelnet ... yes
> libVNCServer yes
> libvorbis ... yes
> libpulse no
> libwebsockets ... no
> libwebp . yes
> wsock32 . no
>Protocol support:
> Kubernetes no
> RDP ... no
> SSH ... no
> Telnet no
> VNC ... yes
>Services / tools:
> guacd .. yes
> guacenc no
> guaclog yes
>FreeRDP plugins: no
>Init scripts: no
>Systemd units: no
> Type "make" to compile guacamole-server.
> {noformat}
> Without the explicit specification of {{{}--with-libavformat=no{}}}:
> {noformat}
> tar -xzf guacamole-server-1.4.0.tar.gz
> cd guacamole-server-1.4.0
> ./configure
> {noformat}
> Output:
> {noformat}
>
> guacamole-server version 1.4.0
>
>Library status:
> freerdp2 yes
> pango ... yes
> libavcodec .. no
> libavformat.. no
> libavutil ... no
> libssh2 . yes
> libssl .. yes
> libswscale .. no
> libtelnet ... yes
> libVNCServer yes
> libvorbis ... yes
> libpulse no
> libwebsockets ... no
> libwebp . yes
> wsock32 . no
>Protocol support:
> Kubernetes no
> RDP ... yes
> SSH ... yes
> Telnet yes
> VNC ... yes
>Services / tools:
> guacd .. yes
> guacenc no
> guaclog yes
>FreeRDP plugins: /usr/lib64/freerdp2
>Init scripts: no
>Systemd units: no
> Type "make" to compile guacamole-server.
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (GUACAMOLE-1719) Protocols RDP, SSH, Telnet are not supported when "--with-libavcodec=no" is specified in configure script
[
https://issues.apache.org/jira/browse/GUACAMOLE-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17840970#comment-17840970
]
Nick Couchman edited comment on GUACAMOLE-1719 at 4/25/24 8:53 PM:
---
Well, I've managed to find and correct one issue in the code related to the
build, but the --with-libavcodec=no issue is just stumping me completely.
{code}
- [AS_HELP_STRING([--with-libavformat],
- [use libavformat when encoding video
@<:@default=check@:>@])],
-[].
+[AS_HELP_STRING([--with-libavformat],
+[use libavformat when encoding video
@<:@default=check@:>@])],
+[],
[with_libavformat=check])
+
{code}
There was a "." (period) instead of a "," (comma) on one of the lines that was
causing the issues with libavformat. The libavcodec one is just completely
puzzling me - there must be some quote or bracket that's getting open and not
closed or something like that, but I cannot, for the life of me, figure out
where it is.
was (Author: nick.couch...@yahoo.com):
Well, I've managed to find and correct one issue in the code related to the
build, but the --with-libavcodec=no issue is just stumping me completely.
{code}
- [AS_HELP_STRING([--with-libavformat],
- [use libavformat when encoding video
@<:@default=check@:>@])],
-[].
+[AS_HELP_STRING([--with-libavformat],
+[use libavformat when encoding video
@<:@default=check@:>@])],
+[],
[with_libavformat=check])
+
{code}
There was a "." (period) instead of a "," (comma) on one of the lines that was
causing the issues with libavformat. The libavcodec one is just completely
puzzling me - there must be some quote or bracket that's getting open and not
closed or something like that, but I cannot, for the life of me, figure out
where it is.
> Protocols RDP, SSH, Telnet are not supported when "--with-libavcodec=no" is
> specified in configure script
> -
>
> Key: GUACAMOLE-1719
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1719
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole
>Affects Versions: 1.4.0
>Reporter: Libor Svehlak
>Priority: Major
> Attachments: configure-output.log
>
>
> Documentation at
> [https://guacamole.apache.org/doc/gug/installing-guacamole.html] specifies
> that {{libavcodec}} is needed only when {{guacenc}} is required. Nevertheless
> when {{--with-libavcodec=no}} is specified in {{configure}} script it is
> causing that protocols RDP, SSH, Telnet are not supported.
> Prerequisite: All required packages for RDP, SSH, Telnet, VNC are installed:
> Steps to reproduce:
> {noformat}
> tar -xzf guacamole-server-1.4.0.tar.gz
> cd guacamole-server-1.4.0
> ./configure --with-libavformat=no
> {noformat}
> Output:
> {noformat}
>
> guacamole-server version 1.4.0
>
>Library status:
> freerdp2 no
> pango ... no
> libavcodec .. disabled
> libavformat.. no
> libavutil ... no
> libssh2 . yes
> libssl .. yes
> libswscale .. no
> libtelnet ... yes
> libVNCServer yes
> libvorbis ... yes
> libpulse no
> libwebsockets ... no
> libwebp . yes
> wsock32 . no
>Protocol support:
> Kubernetes no
> RDP ... no
> SSH ... no
> Telnet no
> VNC ... yes
>Services / tools:
> guacd .. yes
> guacenc no
> guaclog yes
>FreeRDP plugins: no
>Init scripts: no
>Systemd units: no
> Type "make" to compile guacamole-server.
> {noformat}
> Without the explicit specification of {{{}--with-libavformat=no{}}}:
> {noformat}
> tar -xzf guacamole-server-1.4.0.tar.gz
> cd guacamole-server-1.4.0
> ./configure
> {noformat}
> Output:
> {noformat}
>
> guacamole-server version 1.4.0
>
>Library status:
> freerdp2 yes
> pango ... yes
> libavcodec .. no
> libavformat.. no
> libavutil ... no
> libssh2 . yes
> libssl .. yes
> libswscale .. no
> libtelnet ... yes
> libVNCServer yes
> libvorbis ... yes
> libpulse no
> libwebsockets ...
[jira] [Updated] (GUACAMOLE-1947) Issue rendering VNC when screen is scaled
[ https://issues.apache.org/jira/browse/GUACAMOLE-1947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-1947: - Priority: Minor (was: Major) > Issue rendering VNC when screen is scaled > - > > Key: GUACAMOLE-1947 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1947 > Project: Guacamole > Issue Type: Bug > Components: guacamole >Affects Versions: 1.5.5 >Reporter: Brian Doherty >Priority: Minor > Attachments: guac1.png > > > The VNC client renders strangely when I either: > 1) Use xrandr to adjust screen scaling: "/usr/bin/xrandr --output HDMI-2 > --scale-from 1920x1080" > 2) Use the Scale option in GNOME's Display Settings to scale to 200% > See the attached image for details. Mouse functionality is limited to upper > left quadrant. > Syslog below: > Apr 24 16:49:07 mediaserver guacd[59789]: Creating new client for protocol > "vnc" > Apr 24 16:49:07 mediaserver guacd[59789]: Connection ID is > "$1d76912f-e9da-4282-99bd-a374ddc8e893" > Apr 24 16:49:07 mediaserver guacd[188111]: Cursor rendering: local > Apr 24 16:49:07 mediaserver guacd[188111]: User > "@1cc032bf-5961-4d3c-a58f-62d006dabcee" joined connection > "$1d76912f-e9da-4282-99bd-a374ddc8e893" (1 users now present) > Apr 24 16:49:07 mediaserver tomcat9[59787]: 16:49:07.691 > [http-nio-8080-exec-9] INFO o.a.g.tunnel.TunnelRequestService - User "brian" > connected to connection "VNC 0". > Apr 24 16:49:07 mediaserver x11vnc[152024]: 24/04/2024 16:49:07 Got > connection from client 127.0.0.1 > Apr 24 16:49:07 mediaserver x11vnc[152024]: 24/04/2024 16:49:07 0 other > clients > Apr 24 16:49:07 mediaserver x11vnc[152024]: 24/04/2024 16:49:07 Normal socket > connection > Apr 24 16:49:07 mediaserver x11vnc[152024]: 24/04/2024 16:49:07 Disabled X > server key autorepeat. > Apr 24 16:49:07 mediaserver x11vnc[152024]: 24/04/2024 16:49:07 to force > back on run: 'xset r on' (3 times) > Apr 24 16:49:07 mediaserver x11vnc[152024]: 24/04/2024 16:49:07 incr > accepted_client=1 for 127.0.0.1:41410 sock=10 > Apr 24 16:49:07 mediaserver guacd[188111]: VNC server supports protocol > version 3.8 (viewer 3.8) > Apr 24 16:49:07 mediaserver x11vnc[152024]: 24/04/2024 16:49:07 Client > Protocol Version 3.8 > Apr 24 16:49:07 mediaserver x11vnc[152024]: 24/04/2024 16:49:07 Protocol > version sent 3.8, using 3.8 > Apr 24 16:49:07 mediaserver x11vnc[152024]: 24/04/2024 16:49:07 > rfbProcessClientSecurityType: executing handler for type 2 > Apr 24 16:49:07 mediaserver guacd[188111]: We have 1 security types to read > Apr 24 16:49:07 mediaserver guacd[188111]: 0) Received security type 2 > Apr 24 16:49:07 mediaserver guacd[188111]: Selecting security type 2 (0/1 in > the list) > Apr 24 16:49:07 mediaserver guacd[188111]: Selected Security Scheme 2 > Apr 24 16:49:07 mediaserver guacd[188111]: Libgcrypt warning: missing > initialization - please fix the application > Apr 24 16:49:07 mediaserver x11vnc: Libgcrypt warning: missing initialization > - please fix the application > Apr 24 16:49:07 mediaserver guacd[188111]: VNC authentication succeeded > Apr 24 16:49:07 mediaserver guacd[188111]: Desktop name > "mediaserver.dohertyfamily.me:0" > Apr 24 16:49:07 mediaserver guacd[188111]: Connected to VNC server, using > protocol version 3.8 > Apr 24 16:49:07 mediaserver guacd[188111]: VNC server default format: > Apr 24 16:49:07 mediaserver guacd[188111]: 32 bits per pixel. > Apr 24 16:49:07 mediaserver guacd[188111]: Least significant byte first in > each pixel. > Apr 24 16:49:07 mediaserver guacd[188111]: TRUE colour: max red 255 green > 255 blue 255, shift red 16 green 8 blue 0 > Apr 24 16:49:08 mediaserver x11vnc[152024]: 24/04/2024 16:49:08 Pixel format > for client 127.0.0.1: > Apr 24 16:49:08 mediaserver x11vnc[152024]: 24/04/2024 16:49:08 32 bpp, > depth 24, little endian > Apr 24 16:49:08 mediaserver x11vnc[152024]: 24/04/2024 16:49:08 true > colour: max r 255 g 255 b 255, shift r 16 g 8 b 0 > Apr 24 16:49:08 mediaserver x11vnc[152024]: 24/04/2024 16:49:08 no > translation needed > Apr 24 16:49:08 mediaserver x11vnc[152024]: 24/04/2024 16:49:08 > rfbProcessClientNormalMessage: ignoring unsupported encoding type ultraZip > Apr 24 16:49:08 mediaserver x11vnc[152024]: 24/04/2024 16:49:08 Using > compression level 3 for client 127.0.0.1 > Apr 24 16:49:08 mediaserver x11vnc[152024]: 24/04/2024 16:49:08 Enabling > X-style cursor updates for client 127.0.0.1 > Apr 24 16:49:08 mediaserver x11vnc[152024]: 24/04/2024 16:49:08 Enabling > full-color cursor updates for client 127.0.0.1 > Apr 24 16:49:08 mediaserver x11vnc[152024]: 24/04/2024 16:49:08 Enabling > cursor position updates for client 127.0.0.1 > Apr 24 16:49:08 mediaserver x11vnc[152024]: 24/04/2024 16:49:08 Enabling > KeyboardLedState
[jira] [Resolved] (GUACAMOLE-1646) Document setting log level for Guacamole Client Docker container
[ https://issues.apache.org/jira/browse/GUACAMOLE-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman resolved GUACAMOLE-1646. -- Resolution: Implemented Documentation has been added for the 1.6.0 release. > Document setting log level for Guacamole Client Docker container > > > Key: GUACAMOLE-1646 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1646 > Project: Guacamole > Issue Type: Improvement > Components: Documentation >Reporter: Lucas >Assignee: Nick Couchman >Priority: Minor > > While the Guacamole Client Docker container supports setting the log level > via the LOGBACK_LEVEL environment variable, there is no documentation in the > manual that leads users in this direction. This should be documented. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (GUACAMOLE-1935) Document requirements for compatibility with UltraVNC's MSLogonII
[ https://issues.apache.org/jira/browse/GUACAMOLE-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman closed GUACAMOLE-1935. Resolution: Implemented Note has been added to the documentation and will be released when 1.6.0 is released. > Document requirements for compatibility with UltraVNC's MSLogonII > - > > Key: GUACAMOLE-1935 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1935 > Project: Guacamole > Issue Type: Improvement > Components: Documentation >Reporter: nick >Assignee: Nick Couchman >Priority: Minor > > UltraVNC's MSLogonII uses Microsoft domain authentication as the security > protocol for opening a VNC connection. [Support for this protocol was only > added to libvncserver in > v0.9.14|https://github.com/LibVNC/libvncserver/commit/f8333e3] (the latest > version as of writing this), however, as far as I can tell, all of the Red > Hat-based distros recommended for running Guacamole (Fedora, CentOS, > Enterprise Linux) [only have packages with v0.9.13 of > libvncserver|https://pkgs.org/search/?q=libvncserver]. I am running Guacamole > 1.5.4 on RockyLinux 9. > What would be the best way to overcome this? > Updating the packages for those distros to v0.9.14 is probably the best plan, > but I imagine this would take a fair while to ensure the update doesn’t cause > problems for other applications that use libvncserver. > Building libvncserver v0.9.14 from source would probably be the > simplest/fastest workaround but unfortunately this didn’t work for me. Even > after trying to move all the necessary library and shared object files to the > same locations as they are when libvncserver is installed via the package > manager (DNF), I was getting still getting an error in journalctl: – “VNC > connection failed: authentication rejected”. I’m not sure why this didn’t > work but I suspect there is something about the way the package manager > installs the library that I missed when building it from source. > The way I solved it was to rebuild the [libvncserver source RPM for my > distro|https://dl.fedoraproject.org/pub/epel/9/Everything/source/tree/Packages/l/]. > Inside the libvncserver .tar.gz file I added in JUST the extra lines of code > from that libvncserver commit (changes to rfbproto .c and .h files) to avoid > causing any problems with Guacamole, or interfering with any of the > patches/specfile inside that RPM. I installed the libvncserver RPM and then > the libvncserver-devel RPM with DNF and MSLogonII authentication worked! But > it seems like a bit of a dirty way to do it, so I thought I’d share this and > see if anyone has a better idea/method. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GUACAMOLE-1944) SSH Offset between selected text and cursor position
[ https://issues.apache.org/jira/browse/GUACAMOLE-1944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-1944: - Affects Version/s: 1.6.0 (was: 1.5.5) > SSH Offset between selected text and cursor position > - > > Key: GUACAMOLE-1944 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1944 > Project: Guacamole > Issue Type: Bug > Components: guacamole-server >Affects Versions: 1.6.0 >Reporter: Corentin Soriano >Priority: Minor > Attachments: image-2024-04-16-11-49-12-127.png > > > Offset between selected text and real cursor position (only on the main > branch). > !image-2024-04-16-11-49-12-127.png! > Seems related to GUACAMOLE-1622: Add small margins to SSH sessions. > PR : [https://github.com/apache/guacamole-server/pull/509] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GUACAMOLE-1944) SSH Offset between selected text and cursor position
[ https://issues.apache.org/jira/browse/GUACAMOLE-1944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-1944: - Fix Version/s: 1.6.0 > SSH Offset between selected text and cursor position > - > > Key: GUACAMOLE-1944 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1944 > Project: Guacamole > Issue Type: Bug > Components: guacamole-server >Affects Versions: 1.6.0 >Reporter: Corentin Soriano >Priority: Minor > Fix For: 1.6.0 > > Attachments: image-2024-04-16-11-49-12-127.png > > > Offset between selected text and real cursor position (only on the main > branch). > !image-2024-04-16-11-49-12-127.png! > Seems related to GUACAMOLE-1622: Add small margins to SSH sessions. > PR : [https://github.com/apache/guacamole-server/pull/509] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GUACAMOLE-1944) SSH Offset between selected text and cursor position
[ https://issues.apache.org/jira/browse/GUACAMOLE-1944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-1944: - Affects Version/s: 1.5.5 (was: 1.6.0) > SSH Offset between selected text and cursor position > - > > Key: GUACAMOLE-1944 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1944 > Project: Guacamole > Issue Type: Bug > Components: guacamole-server >Affects Versions: 1.5.5 >Reporter: Corentin Soriano >Priority: Minor > Attachments: image-2024-04-16-11-49-12-127.png > > > Offset between selected text and real cursor position (only on the main > branch). > !image-2024-04-16-11-49-12-127.png! > Seems related to GUACAMOLE-1622: Add small margins to SSH sessions. > PR : [https://github.com/apache/guacamole-server/pull/509] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GUACAMOLE-1936) Add Finnish keyboard support
[ https://issues.apache.org/jira/browse/GUACAMOLE-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-1936: - Component/s: RDP > Add Finnish keyboard support > > > Key: GUACAMOLE-1936 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1936 > Project: Guacamole > Issue Type: Improvement > Components: RDP >Reporter: zhenfa zhao >Priority: Minor > Attachments: image-2024-04-19-16-01-16-642.png, > image-2024-04-19-16-02-13-876.png > > > When the local computer uses the Finnish keyboard and the RDP is set to the > Finnish keyboard, the symbols cannot be entered accurately > Corresponding keyboard keys: > / ; ' [ ] \ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (GUACAMOLE-1944) SSH Offset between selected text and cursor position
[ https://issues.apache.org/jira/browse/GUACAMOLE-1944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman resolved GUACAMOLE-1944. -- Resolution: Fixed > SSH Offset between selected text and cursor position > - > > Key: GUACAMOLE-1944 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1944 > Project: Guacamole > Issue Type: Bug > Components: guacamole-server >Affects Versions: 1.6.0 >Reporter: Corentin Soriano >Priority: Minor > Fix For: 1.6.0 > > Attachments: image-2024-04-16-11-49-12-127.png > > > Offset between selected text and real cursor position (only on the main > branch). > !image-2024-04-16-11-49-12-127.png! > Seems related to GUACAMOLE-1622: Add small margins to SSH sessions. > PR : [https://github.com/apache/guacamole-server/pull/509] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GUACAMOLE-1936) Finnish keyboard input
[ https://issues.apache.org/jira/browse/GUACAMOLE-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-1936: - Priority: Minor (was: Major) > Finnish keyboard input > -- > > Key: GUACAMOLE-1936 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1936 > Project: Guacamole > Issue Type: Improvement >Reporter: zhenfa zhao >Priority: Minor > Attachments: image-2024-04-19-16-01-16-642.png, > image-2024-04-19-16-02-13-876.png > > > When the local computer uses the Finnish keyboard and the RDP is set to the > Finnish keyboard, the symbols cannot be entered accurately > Corresponding keyboard keys: > / ; ' [ ] \ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GUACAMOLE-1936) Add Finnish keyboard support
[ https://issues.apache.org/jira/browse/GUACAMOLE-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-1936: - Summary: Add Finnish keyboard support (was: Finnish keyboard input) > Add Finnish keyboard support > > > Key: GUACAMOLE-1936 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1936 > Project: Guacamole > Issue Type: Improvement >Reporter: zhenfa zhao >Priority: Minor > Attachments: image-2024-04-19-16-01-16-642.png, > image-2024-04-19-16-02-13-876.png > > > When the local computer uses the Finnish keyboard and the RDP is set to the > Finnish keyboard, the symbols cannot be entered accurately > Corresponding keyboard keys: > / ; ' [ ] \ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GUACAMOLE-1936) Finnish keyboard input
[ https://issues.apache.org/jira/browse/GUACAMOLE-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-1936: - Issue Type: Improvement (was: Bug) > Finnish keyboard input > -- > > Key: GUACAMOLE-1936 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1936 > Project: Guacamole > Issue Type: Improvement >Reporter: zhenfa zhao >Priority: Major > Attachments: image-2024-04-19-16-01-16-642.png, > image-2024-04-19-16-02-13-876.png > > > When the local computer uses the Finnish keyboard and the RDP is set to the > Finnish keyboard, the symbols cannot be entered accurately > Corresponding keyboard keys: > / ; ' [ ] \ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (GUACAMOLE-1646) Document setting log level for Guacamole Client Docker container
[ https://issues.apache.org/jira/browse/GUACAMOLE-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman reassigned GUACAMOLE-1646: Assignee: Nick Couchman > Document setting log level for Guacamole Client Docker container > > > Key: GUACAMOLE-1646 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1646 > Project: Guacamole > Issue Type: Improvement > Components: Documentation >Reporter: Lucas >Assignee: Nick Couchman >Priority: Minor > > While the Guacamole Client Docker container supports setting the log level > via the LOGBACK_LEVEL environment variable, there is no documentation in the > manual that leads users in this direction. This should be documented. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (GUACAMOLE-1935) Document requirements for compatibility with UltraVNC's MSLogonII
[ https://issues.apache.org/jira/browse/GUACAMOLE-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman reassigned GUACAMOLE-1935: Assignee: Nick Couchman > Document requirements for compatibility with UltraVNC's MSLogonII > - > > Key: GUACAMOLE-1935 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1935 > Project: Guacamole > Issue Type: Improvement > Components: Documentation >Reporter: nick >Assignee: Nick Couchman >Priority: Minor > > UltraVNC's MSLogonII uses Microsoft domain authentication as the security > protocol for opening a VNC connection. [Support for this protocol was only > added to libvncserver in > v0.9.14|https://github.com/LibVNC/libvncserver/commit/f8333e3] (the latest > version as of writing this), however, as far as I can tell, all of the Red > Hat-based distros recommended for running Guacamole (Fedora, CentOS, > Enterprise Linux) [only have packages with v0.9.13 of > libvncserver|https://pkgs.org/search/?q=libvncserver]. I am running Guacamole > 1.5.4 on RockyLinux 9. > What would be the best way to overcome this? > Updating the packages for those distros to v0.9.14 is probably the best plan, > but I imagine this would take a fair while to ensure the update doesn’t cause > problems for other applications that use libvncserver. > Building libvncserver v0.9.14 from source would probably be the > simplest/fastest workaround but unfortunately this didn’t work for me. Even > after trying to move all the necessary library and shared object files to the > same locations as they are when libvncserver is installed via the package > manager (DNF), I was getting still getting an error in journalctl: – “VNC > connection failed: authentication rejected”. I’m not sure why this didn’t > work but I suspect there is something about the way the package manager > installs the library that I missed when building it from source. > The way I solved it was to rebuild the [libvncserver source RPM for my > distro|https://dl.fedoraproject.org/pub/epel/9/Everything/source/tree/Packages/l/]. > Inside the libvncserver .tar.gz file I added in JUST the extra lines of code > from that libvncserver commit (changes to rfbproto .c and .h files) to avoid > causing any problems with Guacamole, or interfering with any of the > patches/specfile inside that RPM. I installed the libvncserver RPM and then > the libvncserver-devel RPM with DNF and MSLogonII authentication worked! But > it seems like a bit of a dirty way to do it, so I thought I’d share this and > see if anyone has a better idea/method. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (GUACAMOLE-1068) Randomize generation of TOTP key until enrollment is confirmed
[ https://issues.apache.org/jira/browse/GUACAMOLE-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman closed GUACAMOLE-1068. Resolution: Implemented > Randomize generation of TOTP key until enrollment is confirmed > -- > > Key: GUACAMOLE-1068 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1068 > Project: Guacamole > Issue Type: Improvement > Components: Documentation, guacamole-auth-totp >Reporter: Marcos >Assignee: Nick Couchman >Priority: Minor > Fix For: 1.6.0 > > > When activating TOTP 2 factor authentication, the first time a user enters > his credentials, the TOTP key is inserted in the database and the QR code is > shown. If the user does not complete the enrollment by entering the OTP code, > the key remains in the database and it will be reused next time he tries > again. > This opens a window between when the account is created and when the user > indeed verifies the OTP token, where an attacker that already knows the > username and password of the user, can get the generated OTP token. It will > be the same that the user gets when he finishes enrolment. The user doesn't > know that this key has been stolen and can be used in the future. > Security would be increased if the key would be generated randomly every time > until the pin code is entered and the enrolment process is finished, as the > malicious user would get a different key, and only the key validated by > entering the pin would be stored in the database. The attacker would be able > to get a key, but when the legitimate user tries to login and the QR code is > not displayed anymore the attack would be uncovered. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GUACAMOLE-1068) Randomize generation of TOTP key until enrollment is confirmed
[ https://issues.apache.org/jira/browse/GUACAMOLE-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-1068: - Component/s: Documentation > Randomize generation of TOTP key until enrollment is confirmed > -- > > Key: GUACAMOLE-1068 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1068 > Project: Guacamole > Issue Type: Improvement > Components: Documentation, guacamole-auth-totp >Reporter: Marcos >Assignee: Nick Couchman >Priority: Minor > > When activating TOTP 2 factor authentication, the first time a user enters > his credentials, the TOTP key is inserted in the database and the QR code is > shown. If the user does not complete the enrollment by entering the OTP code, > the key remains in the database and it will be reused next time he tries > again. > This opens a window between when the account is created and when the user > indeed verifies the OTP token, where an attacker that already knows the > username and password of the user, can get the generated OTP token. It will > be the same that the user gets when he finishes enrolment. The user doesn't > know that this key has been stolen and can be used in the future. > Security would be increased if the key would be generated randomly every time > until the pin code is entered and the enrolment process is finished, as the > malicious user would get a different key, and only the key validated by > entering the pin would be stored in the database. The attacker would be able > to get a key, but when the legitimate user tries to login and the QR code is > not displayed anymore the attack would be uncovered. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GUACAMOLE-1068) Randomize generation of TOTP key until enrollment is confirmed
[ https://issues.apache.org/jira/browse/GUACAMOLE-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-1068: - Fix Version/s: 1.6.0 > Randomize generation of TOTP key until enrollment is confirmed > -- > > Key: GUACAMOLE-1068 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1068 > Project: Guacamole > Issue Type: Improvement > Components: Documentation, guacamole-auth-totp >Reporter: Marcos >Assignee: Nick Couchman >Priority: Minor > Fix For: 1.6.0 > > > When activating TOTP 2 factor authentication, the first time a user enters > his credentials, the TOTP key is inserted in the database and the QR code is > shown. If the user does not complete the enrollment by entering the OTP code, > the key remains in the database and it will be reused next time he tries > again. > This opens a window between when the account is created and when the user > indeed verifies the OTP token, where an attacker that already knows the > username and password of the user, can get the generated OTP token. It will > be the same that the user gets when he finishes enrolment. The user doesn't > know that this key has been stolen and can be used in the future. > Security would be increased if the key would be generated randomly every time > until the pin code is entered and the enrolment process is finished, as the > malicious user would get a different key, and only the key validated by > entering the pin would be stored in the database. The attacker would be able > to get a key, but when the legitimate user tries to login and the QR code is > not displayed anymore the attack would be uncovered. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GUACAMOLE-1760) vnc connect add Quality and Compression level params
[ https://issues.apache.org/jira/browse/GUACAMOLE-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-1760: - Component/s: Documentation (was: guacamole) > vnc connect add Quality and Compression level params > -- > > Key: GUACAMOLE-1760 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1760 > Project: Guacamole > Issue Type: Wish > Components: Documentation, guacamole-client, guacd >Reporter: peterzhou >Priority: Minor > Fix For: 1.6.0 > > > How to add the Quality and Compression level parameter to a vnc connection -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (GUACAMOLE-1760) vnc connect add Quality and Compression level params
[ https://issues.apache.org/jira/browse/GUACAMOLE-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman closed GUACAMOLE-1760. Resolution: Implemented > vnc connect add Quality and Compression level params > -- > > Key: GUACAMOLE-1760 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1760 > Project: Guacamole > Issue Type: Wish > Components: Documentation, guacamole-client, guacd >Reporter: peterzhou >Assignee: Nick Couchman >Priority: Minor > Fix For: 1.6.0 > > > How to add the Quality and Compression level parameter to a vnc connection -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GUACAMOLE-1760) vnc connect add Quality and Compression level params
[ https://issues.apache.org/jira/browse/GUACAMOLE-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-1760: - Fix Version/s: 1.6.0 > vnc connect add Quality and Compression level params > -- > > Key: GUACAMOLE-1760 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1760 > Project: Guacamole > Issue Type: Wish > Components: guacamole, guacamole-client, guacd >Reporter: peterzhou >Priority: Minor > Fix For: 1.6.0 > > > How to add the Quality and Compression level parameter to a vnc connection -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (GUACAMOLE-1760) vnc connect add Quality and Compression level params
[ https://issues.apache.org/jira/browse/GUACAMOLE-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman reassigned GUACAMOLE-1760: Assignee: Nick Couchman > vnc connect add Quality and Compression level params > -- > > Key: GUACAMOLE-1760 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1760 > Project: Guacamole > Issue Type: Wish > Components: Documentation, guacamole-client, guacd >Reporter: peterzhou >Assignee: Nick Couchman >Priority: Minor > Fix For: 1.6.0 > > > How to add the Quality and Compression level parameter to a vnc connection -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (GUACAMOLE-1866) Improvements to the "Recent connections" section
[ https://issues.apache.org/jira/browse/GUACAMOLE-1866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman closed GUACAMOLE-1866. Resolution: Implemented > Improvements to the "Recent connections" section > > > Key: GUACAMOLE-1866 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1866 > Project: Guacamole > Issue Type: New Feature > Components: Documentation, guacamole-client >Reporter: Julien Lejeune >Assignee: Nick Couchman >Priority: Trivial > Fix For: 1.6.0 > > > The "Recent Connections" section takes some place on the Guacamole homepage, > but I have the feeling that it is not useful for all users, only for those > who mostly connect to the same few connections. > This comes from the assumption that the "Recent Connections" section only > shows the five last connections, which is what I have seen so far. Let me > know if I am wrong. > So, I would suggest either of those : > * Allow a user or an administrator to remove or hide the "Recent > Connections" section. > * Improve the usefulness of the "Recent Connections" section so it is useful > to more users. For example, it would be nice to allow a user to remove a > connection showing in the "Recent Connections" section if the user does not > need this suggestion anymore. Also, when a connection is removed that way, > the sixth last connection could come back again in the "Recent Connections" > section. > I am not a developer, so I am not sure how to implement it myself, but I > would be open to try. > First, I would like to read what you all think of those suggestions and where > the discussion goes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (GUACAMOLE-1861) Document RemoteIPValve to cover IPv4 and IPv6
[ https://issues.apache.org/jira/browse/GUACAMOLE-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman closed GUACAMOLE-1861. Resolution: Implemented > Document RemoteIPValve to cover IPv4 and IPv6 > - > > Key: GUACAMOLE-1861 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1861 > Project: Guacamole > Issue Type: Improvement > Components: Documentation >Reporter: Nick Couchman >Assignee: Nick Couchman >Priority: Minor > Fix For: 1.6.0 > > > The current documentation for RemoteIPValve in the manual is very > IPv4-centric, and lacks some pointers that could help people with either > IPv6-only or IPv4 + IPv6 systems have better luck getting the proxy > configuration going. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (GUACAMOLE-1945) Changed OpenSSL to build using source code
[
https://issues.apache.org/jira/browse/GUACAMOLE-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17838622#comment-17838622
]
Nick Couchman edited comment on GUACAMOLE-1945 at 4/18/24 11:55 AM:
{quote}
Due to the lack of support for more architectures in guacd, I maintain a
multi-architecture code base based on the debian:bookworm-slim image, including
amd64 arm64 ppc64le s390x.
{quote}
The current Dockerfile bases the guacd image off of the alipine:3.18 tag.
According to Docker Hub, this already has support for all of the architectures
you mentioned: https://hub.docker.com/_/alpine/tags
I notice that your changes still base on Alpine, but move from the 3.18 tag to
latest - this will need some additional testing to make sure other things don't
break in the process of making this change.
{quote}
In newer operating systems, the default openssl version is 3.0, and the vnc
feature will not be available.
{quote}
I want to make sure I understand what you're saying, here. Are you saying that:
1. *Without* the changes you've made, VNC support will not be available? OR:
2. The changes you've made, bumping the OpenSSL version to 3.0, *cause* VNC
support to be unavailable?
was (Author: nick.couch...@yahoo.com):
{quote}
Due to the lack of support for more architectures in guacd, I maintain a
multi-architecture code base based on the debian:bookworm-slim image, including
amd64 arm64 ppc64le s390x.
{quote}
The current Dockerfile bases the guacd image off of the alipine:3.18 tag.
According to Docker Hub, this already has support for all of the architectures
you mentioned: https://hub.docker.com/_/alpine/tags
I notice that your changes still base on Alpine, but move from the 3.18 tag to
latest - this will need some additional testing to make sure other things don't
break in the process of making this change.
{quote}
In newer operating systems, the default openssl version is 3.0, and the vnc
feature will not be available.
{quote}
I want to make sure I understand what you're saying, here. Are you saying that:
1. *Without* the changes you've made, VNC support will not be available? OR:
2. The changes you've made, bumping the OpenSSL version to 3.0, *cause* VNC
support unavailable?
> Changed OpenSSL to build using source code
> --
>
> Key: GUACAMOLE-1945
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1945
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-server
>Reporter: wuxiaobai
>Priority: Minor
>
> Build OpenSSL from source code to adapt to newer operating systems.
> - https://github.com/apache/guacamole-server/pull/510
>
> {code:java}
> diff --git a/Dockerfile b/Dockerfile
> index 5f1e824c..6cea233e 100644
> --- a/Dockerfile
> +++ b/Dockerfile
> @@ -22,9 +22,7 @@
> # # The Alpine Linux image that should be used as the basis for the guacd
> image
> -# NOTE: Using 3.18 because the required openssl1.1-compat-dev package was
> -# removed in more recent versions.
> -ARG ALPINE_BASE_IMAGE=3.18
> +ARG ALPINE_BASE_IMAGE=latest
> FROM alpine:${ALPINE_BASE_IMAGE} AS builder # Install build dependencies
> @@ -42,7 +40,6 @@ RUN apk add --no-cache \
> libtool \
> libwebp-dev \
> make \
> - openssl1.1-compat-dev \
> pango-dev \
> pulseaudio-dev \
> util-linux-dev
> @@ -64,6 +61,7 @@ ARG PREFIX_DIR=/opt/guacamole
> # library (these can be overridden at build time if a specific version is
> # needed)
> #
> +ARG WITH_OPENSSL='OpenSSL_1(\_\d+\w*)+'
> ARG WITH_FREERDP='2(\.\d+)+'
> ARG WITH_LIBSSH2='libssh2-\d+(\.\d+)+'
> ARG WITH_LIBTELNET='\d+(\.\d+)+'
> @@ -76,6 +74,8 @@ ARG WITH_LIBWEBSOCKETS='v\d+(\.\d+)+'
> # options are needed)
> #+ARG OPENSSL_OPTS=""
> +
> ARG FREERDP_OPTS="\
> -DBUILTIN_CHANNELS=OFF \
> -DCHANNEL_URBDRC=OFF \
> @@ -101,7 +101,6 @@ ARG FREERDP_OPTS="\
> -DWITH_SERVER_INTERFACE=OFF \
> -DWITH_SHADOW_MAC=OFF \
> -DWITH_SHADOW_X11=OFF \
> - -DWITH_SSE2=ON \
> -DWITH_WAYLAND=OFF \
> -DWITH_X11=OFF \
> -DWITH_X264=OFF \
> diff --git a/src/guacd-docker/bin/build-all.sh
> b/src/guacd-docker/bin/build-all.sh
> index b8c33b8f..a559babb 100755
> --- a/src/guacd-docker/bin/build-all.sh
> +++ b/src/guacd-docker/bin/build-all.sh
> @@ -28,7 +28,7 @@
> # Pre-populate build control variables such that the custom build prefix is
> # used for C headers, locating libraries, etc.
> export CFLAGS="-I${PREFIX_DIR}/include"
> -export LDFLAGS="-L${PREFIX_DIR}/lib"
> +export LDFLAGS="-Wl,-rpath,${PREFIX_DIR}/lib -L${PREFIX_DIR}/lib"
> export PKG_CONFIG_PATH="${PREFIX_DIR}/lib/pkgconfig" # Ensure thread stack
>
[jira] [Comment Edited] (GUACAMOLE-1945) Changed OpenSSL to build using source code
[
https://issues.apache.org/jira/browse/GUACAMOLE-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17838622#comment-17838622
]
Nick Couchman edited comment on GUACAMOLE-1945 at 4/18/24 11:54 AM:
{quote}
Due to the lack of support for more architectures in guacd, I maintain a
multi-architecture code base based on the debian:bookworm-slim image, including
amd64 arm64 ppc64le s390x.
{quote}
The current Dockerfile bases the guacd image off of the alipine:3.18 tag.
According to Docker Hub, this already has support for all of the architectures
you mentioned: https://hub.docker.com/_/alpine/tags
I notice that your changes still base on Alpine, but move from the 3.18 tag to
latest - this will need some additional testing to make sure other things don't
break in the process of making this change.
{quote}
In newer operating systems, the default openssl version is 3.0, and the vnc
feature will not be available.
{quote}
I want to make sure I understand what you're saying, here. Are you saying that:
1. *Without* the changes you've made, VNC support will not be available? OR:
2. The changes you've made, bumping the OpenSSL version to 3.0, *cause* VNC
support unavailable?
was (Author: nick.couch...@yahoo.com):
{quote}
Due to the lack of support for more architectures in guacd, I maintain a
multi-architecture code base based on the debian:bookworm-slim image, including
amd64 arm64 ppc64le s390x.
{quote}
The current Dockerfile bases the guacd image off of the alipine:3.18 tag.
According to Docker Hub, this already has support for all of the architectures
you mentioned: https://hub.docker.com/_/alpine/tags
I notice that your changes still base on Alpine, but move from the 3.18 tag to
latest - this will need some additional testing to make sure other things don't
break in the process of making this change.
{quote}
In newer operating systems, the default openssl version is 3.0, and the vnc
feature will not be available.
{quote}
I want to make sure I understand what you're saying, here. Are you saying that:
1. *Without* the changes you've made, VNC support will not be available? OR:
2. The changes you've made, bumping the OpenSSL version to 3.0, make VNC
support unavailable?
> Changed OpenSSL to build using source code
> --
>
> Key: GUACAMOLE-1945
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1945
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-server
>Reporter: wuxiaobai
>Priority: Minor
>
> Build OpenSSL from source code to adapt to newer operating systems.
> - https://github.com/apache/guacamole-server/pull/510
>
> {code:java}
> diff --git a/Dockerfile b/Dockerfile
> index 5f1e824c..6cea233e 100644
> --- a/Dockerfile
> +++ b/Dockerfile
> @@ -22,9 +22,7 @@
> # # The Alpine Linux image that should be used as the basis for the guacd
> image
> -# NOTE: Using 3.18 because the required openssl1.1-compat-dev package was
> -# removed in more recent versions.
> -ARG ALPINE_BASE_IMAGE=3.18
> +ARG ALPINE_BASE_IMAGE=latest
> FROM alpine:${ALPINE_BASE_IMAGE} AS builder # Install build dependencies
> @@ -42,7 +40,6 @@ RUN apk add --no-cache \
> libtool \
> libwebp-dev \
> make \
> - openssl1.1-compat-dev \
> pango-dev \
> pulseaudio-dev \
> util-linux-dev
> @@ -64,6 +61,7 @@ ARG PREFIX_DIR=/opt/guacamole
> # library (these can be overridden at build time if a specific version is
> # needed)
> #
> +ARG WITH_OPENSSL='OpenSSL_1(\_\d+\w*)+'
> ARG WITH_FREERDP='2(\.\d+)+'
> ARG WITH_LIBSSH2='libssh2-\d+(\.\d+)+'
> ARG WITH_LIBTELNET='\d+(\.\d+)+'
> @@ -76,6 +74,8 @@ ARG WITH_LIBWEBSOCKETS='v\d+(\.\d+)+'
> # options are needed)
> #+ARG OPENSSL_OPTS=""
> +
> ARG FREERDP_OPTS="\
> -DBUILTIN_CHANNELS=OFF \
> -DCHANNEL_URBDRC=OFF \
> @@ -101,7 +101,6 @@ ARG FREERDP_OPTS="\
> -DWITH_SERVER_INTERFACE=OFF \
> -DWITH_SHADOW_MAC=OFF \
> -DWITH_SHADOW_X11=OFF \
> - -DWITH_SSE2=ON \
> -DWITH_WAYLAND=OFF \
> -DWITH_X11=OFF \
> -DWITH_X264=OFF \
> diff --git a/src/guacd-docker/bin/build-all.sh
> b/src/guacd-docker/bin/build-all.sh
> index b8c33b8f..a559babb 100755
> --- a/src/guacd-docker/bin/build-all.sh
> +++ b/src/guacd-docker/bin/build-all.sh
> @@ -28,7 +28,7 @@
> # Pre-populate build control variables such that the custom build prefix is
> # used for C headers, locating libraries, etc.
> export CFLAGS="-I${PREFIX_DIR}/include"
> -export LDFLAGS="-L${PREFIX_DIR}/lib"
> +export LDFLAGS="-Wl,-rpath,${PREFIX_DIR}/lib -L${PREFIX_DIR}/lib"
> export PKG_CONFIG_PATH="${PREFIX_DIR}/lib/pkgconfig" # Ensure thread stack
> size will
[jira] [Commented] (GUACAMOLE-1945) Changed OpenSSL to build using source code
[
https://issues.apache.org/jira/browse/GUACAMOLE-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17838622#comment-17838622
]
Nick Couchman commented on GUACAMOLE-1945:
--
{quote}
Due to the lack of support for more architectures in guacd, I maintain a
multi-architecture code base based on the debian:bookworm-slim image, including
amd64 arm64 ppc64le s390x.
{quote}
The current Dockerfile bases the guacd image off of the alipine:3.18 tag.
According to Docker Hub, this already has support for all of the architectures
you mentioned: https://hub.docker.com/_/alpine/tags
I notice that your changes still base on Alpine, but move from the 3.18 tag to
latest - this will need some additional testing to make sure other things don't
break in the process of making this change.
{quote}
In newer operating systems, the default openssl version is 3.0, and the vnc
feature will not be available.
{quote}
I want to make sure I understand what you're saying, here. Are you saying that:
1. *Without* the changes you've made, VNC support will not be available? OR:
2. The changes you've made, bumping the OpenSSL version to 3.0, make VNC
support unavailable?
> Changed OpenSSL to build using source code
> --
>
> Key: GUACAMOLE-1945
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1945
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-server
>Reporter: wuxiaobai
>Priority: Minor
>
> Build OpenSSL from source code to adapt to newer operating systems.
> - https://github.com/apache/guacamole-server/pull/510
>
> {code:java}
> diff --git a/Dockerfile b/Dockerfile
> index 5f1e824c..6cea233e 100644
> --- a/Dockerfile
> +++ b/Dockerfile
> @@ -22,9 +22,7 @@
> # # The Alpine Linux image that should be used as the basis for the guacd
> image
> -# NOTE: Using 3.18 because the required openssl1.1-compat-dev package was
> -# removed in more recent versions.
> -ARG ALPINE_BASE_IMAGE=3.18
> +ARG ALPINE_BASE_IMAGE=latest
> FROM alpine:${ALPINE_BASE_IMAGE} AS builder # Install build dependencies
> @@ -42,7 +40,6 @@ RUN apk add --no-cache \
> libtool \
> libwebp-dev \
> make \
> - openssl1.1-compat-dev \
> pango-dev \
> pulseaudio-dev \
> util-linux-dev
> @@ -64,6 +61,7 @@ ARG PREFIX_DIR=/opt/guacamole
> # library (these can be overridden at build time if a specific version is
> # needed)
> #
> +ARG WITH_OPENSSL='OpenSSL_1(\_\d+\w*)+'
> ARG WITH_FREERDP='2(\.\d+)+'
> ARG WITH_LIBSSH2='libssh2-\d+(\.\d+)+'
> ARG WITH_LIBTELNET='\d+(\.\d+)+'
> @@ -76,6 +74,8 @@ ARG WITH_LIBWEBSOCKETS='v\d+(\.\d+)+'
> # options are needed)
> #+ARG OPENSSL_OPTS=""
> +
> ARG FREERDP_OPTS="\
> -DBUILTIN_CHANNELS=OFF \
> -DCHANNEL_URBDRC=OFF \
> @@ -101,7 +101,6 @@ ARG FREERDP_OPTS="\
> -DWITH_SERVER_INTERFACE=OFF \
> -DWITH_SHADOW_MAC=OFF \
> -DWITH_SHADOW_X11=OFF \
> - -DWITH_SSE2=ON \
> -DWITH_WAYLAND=OFF \
> -DWITH_X11=OFF \
> -DWITH_X264=OFF \
> diff --git a/src/guacd-docker/bin/build-all.sh
> b/src/guacd-docker/bin/build-all.sh
> index b8c33b8f..a559babb 100755
> --- a/src/guacd-docker/bin/build-all.sh
> +++ b/src/guacd-docker/bin/build-all.sh
> @@ -28,7 +28,7 @@
> # Pre-populate build control variables such that the custom build prefix is
> # used for C headers, locating libraries, etc.
> export CFLAGS="-I${PREFIX_DIR}/include"
> -export LDFLAGS="-L${PREFIX_DIR}/lib"
> +export LDFLAGS="-Wl,-rpath,${PREFIX_DIR}/lib -L${PREFIX_DIR}/lib"
> export PKG_CONFIG_PATH="${PREFIX_DIR}/lib/pkgconfig" # Ensure thread stack
> size will be 8 MB (glibc's default on Linux) rather than
> @@ -85,6 +85,8 @@ install_from_git() {
> # used by the library being built
> if [ -e CMakeLists.txt ]; then
> cmake -DCMAKE_INSTALL_PREFIX:PATH="$PREFIX_DIR" "$@" .
> + elif [ -e config ]; then
> + ./config --prefix="$PREFIX_DIR" "$@"
> else
> [ -e configure ] || autoreconf -fi
> ./configure --prefix="$PREFIX_DIR" "$@"
> @@ -103,11 +105,11 @@ export BUILD_ARCHITECTURE="$(arch)" # Determine
> architecture building on
> echo "Build architecture: $BUILD_ARCHITECTURE" case $BUILD_ARCHITECTURE in
> - armv6l|armv7l|aarch64)
> - export FREERDP_OPTS_OVERRIDES="-DWITH_SSE2=OFF" # Disable SSE2 on ARM
> + x86_64)
> + export FREERDP_OPTS_OVERRIDES="-DWITH_SSE2=ON" # Enable SSE2 on
> x86_64
> ;;
> *)
> - export FREERDP_OPTS_OVERRIDES=""
> + export FREERDP_OPTS_OVERRIDES="-DWITH_SSE2=OFF"
> ;;
> esac@@ -115,6 +117,7 @@ esac
> # Build and install core protocol library dependencies
> #+install_from_git
[jira] [Updated] (GUACAMOLE-1866) Improvements to the "Recent connections" section
[ https://issues.apache.org/jira/browse/GUACAMOLE-1866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-1866: - Component/s: Documentation > Improvements to the "Recent connections" section > > > Key: GUACAMOLE-1866 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1866 > Project: Guacamole > Issue Type: New Feature > Components: Documentation, guacamole-client >Reporter: Julien Lejeune >Assignee: Nick Couchman >Priority: Trivial > Fix For: 1.6.0 > > > The "Recent Connections" section takes some place on the Guacamole homepage, > but I have the feeling that it is not useful for all users, only for those > who mostly connect to the same few connections. > This comes from the assumption that the "Recent Connections" section only > shows the five last connections, which is what I have seen so far. Let me > know if I am wrong. > So, I would suggest either of those : > * Allow a user or an administrator to remove or hide the "Recent > Connections" section. > * Improve the usefulness of the "Recent Connections" section so it is useful > to more users. For example, it would be nice to allow a user to remove a > connection showing in the "Recent Connections" section if the user does not > need this suggestion anymore. Also, when a connection is removed that way, > the sixth last connection could come back again in the "Recent Connections" > section. > I am not a developer, so I am not sure how to implement it myself, but I > would be open to try. > First, I would like to read what you all think of those suggestions and where > the discussion goes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GUACAMOLE-1945) Changed OpenSSL to build using source code
[
https://issues.apache.org/jira/browse/GUACAMOLE-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17838099#comment-17838099
]
Nick Couchman commented on GUACAMOLE-1945:
--
[~qq296015668]: Can you explain further why this is necessary or beneficial? Is
there some additional functionality or security that this provides?
> Changed OpenSSL to build using source code
> --
>
> Key: GUACAMOLE-1945
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1945
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-server
>Reporter: wuxiaobai
>Priority: Minor
>
> Build OpenSSL from source code to adapt to newer operating systems.
> - https://github.com/apache/guacamole-server/pull/510
>
> {code:java}
> diff --git a/Dockerfile b/Dockerfile
> index 5f1e824c..6cea233e 100644
> --- a/Dockerfile
> +++ b/Dockerfile
> @@ -22,9 +22,7 @@
> # # The Alpine Linux image that should be used as the basis for the guacd
> image
> -# NOTE: Using 3.18 because the required openssl1.1-compat-dev package was
> -# removed in more recent versions.
> -ARG ALPINE_BASE_IMAGE=3.18
> +ARG ALPINE_BASE_IMAGE=latest
> FROM alpine:${ALPINE_BASE_IMAGE} AS builder # Install build dependencies
> @@ -42,7 +40,6 @@ RUN apk add --no-cache \
> libtool \
> libwebp-dev \
> make \
> - openssl1.1-compat-dev \
> pango-dev \
> pulseaudio-dev \
> util-linux-dev
> @@ -64,6 +61,7 @@ ARG PREFIX_DIR=/opt/guacamole
> # library (these can be overridden at build time if a specific version is
> # needed)
> #
> +ARG WITH_OPENSSL='OpenSSL_1(\_\d+\w*)+'
> ARG WITH_FREERDP='2(\.\d+)+'
> ARG WITH_LIBSSH2='libssh2-\d+(\.\d+)+'
> ARG WITH_LIBTELNET='\d+(\.\d+)+'
> @@ -76,6 +74,8 @@ ARG WITH_LIBWEBSOCKETS='v\d+(\.\d+)+'
> # options are needed)
> #+ARG OPENSSL_OPTS=""
> +
> ARG FREERDP_OPTS="\
> -DBUILTIN_CHANNELS=OFF \
> -DCHANNEL_URBDRC=OFF \
> @@ -101,7 +101,6 @@ ARG FREERDP_OPTS="\
> -DWITH_SERVER_INTERFACE=OFF \
> -DWITH_SHADOW_MAC=OFF \
> -DWITH_SHADOW_X11=OFF \
> - -DWITH_SSE2=ON \
> -DWITH_WAYLAND=OFF \
> -DWITH_X11=OFF \
> -DWITH_X264=OFF \
> diff --git a/src/guacd-docker/bin/build-all.sh
> b/src/guacd-docker/bin/build-all.sh
> index b8c33b8f..a559babb 100755
> --- a/src/guacd-docker/bin/build-all.sh
> +++ b/src/guacd-docker/bin/build-all.sh
> @@ -28,7 +28,7 @@
> # Pre-populate build control variables such that the custom build prefix is
> # used for C headers, locating libraries, etc.
> export CFLAGS="-I${PREFIX_DIR}/include"
> -export LDFLAGS="-L${PREFIX_DIR}/lib"
> +export LDFLAGS="-Wl,-rpath,${PREFIX_DIR}/lib -L${PREFIX_DIR}/lib"
> export PKG_CONFIG_PATH="${PREFIX_DIR}/lib/pkgconfig" # Ensure thread stack
> size will be 8 MB (glibc's default on Linux) rather than
> @@ -85,6 +85,8 @@ install_from_git() {
> # used by the library being built
> if [ -e CMakeLists.txt ]; then
> cmake -DCMAKE_INSTALL_PREFIX:PATH="$PREFIX_DIR" "$@" .
> + elif [ -e config ]; then
> + ./config --prefix="$PREFIX_DIR" "$@"
> else
> [ -e configure ] || autoreconf -fi
> ./configure --prefix="$PREFIX_DIR" "$@"
> @@ -103,11 +105,11 @@ export BUILD_ARCHITECTURE="$(arch)" # Determine
> architecture building on
> echo "Build architecture: $BUILD_ARCHITECTURE" case $BUILD_ARCHITECTURE in
> - armv6l|armv7l|aarch64)
> - export FREERDP_OPTS_OVERRIDES="-DWITH_SSE2=OFF" # Disable SSE2 on ARM
> + x86_64)
> + export FREERDP_OPTS_OVERRIDES="-DWITH_SSE2=ON" # Enable SSE2 on
> x86_64
> ;;
> *)
> - export FREERDP_OPTS_OVERRIDES=""
> + export FREERDP_OPTS_OVERRIDES="-DWITH_SSE2=OFF"
> ;;
> esac@@ -115,6 +117,7 @@ esac
> # Build and install core protocol library dependencies
> #+install_from_git "https://github.com/openssl/openssl; "$WITH_OPENSSL"
> $OPENSSL_OPTS
> install_from_git "https://github.com/FreeRDP/FreeRDP; "$WITH_FREERDP"
> $FREERDP_OPTS $FREERDP_OPTS_OVERRIDES
> install_from_git "https://github.com/libssh2/libssh2; "$WITH_LIBSSH2"
> $LIBSSH2_OPTS
> install_from_git "https://github.com/seanmiddleditch/libtelnet;
> "$WITH_LIBTELNET" $LIBTELNET_OPTS{code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (GUACAMOLE-1940) rdp-connect failed when microphone input is enabled
[
https://issues.apache.org/jira/browse/GUACAMOLE-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman resolved GUACAMOLE-1940.
--
Resolution: Fixed
> rdp-connect failed when microphone input is enabled
> ---
>
> Key: GUACAMOLE-1940
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1940
> Project: Guacamole
> Issue Type: Bug
> Components: RDP
>Affects Versions: 1.5.5
> Environment: GUACD-INTRANET-SERVER:
> OS: Linux rdg-dev 5.10.0-28-amd64 #1 SMP Debian 5.10.209-2 (2024-01-31)
> x86_64 GNU/Linux
> GUACD: Guacamole proxy daemon (guacd) version 1.5.5
> TOMCAT-DMZ-SERVER:
> OS: Linux rdg-dev 5.10.0-28-amd64 #1 SMP Debian 5.10.209-2 (2024-01-31)
> x86_64 GNU/Linux
> TOMCAT: tomcat99.0.43-2~deb11u9 all
> Apache Tomcat 9 - Servlet and JSP engine
> JAVA: openjdk version "11.0.22" 2024-01-16
> OpenJDK Runtime Environment (build 11.0.22+7-post-Debian-1deb11u1)
> OpenJDK 64-Bit Server VM (build 11.0.22+7-post-Debian-1deb11u1, mixed
> mode, sharing)
>Reporter: Karsten
>Priority: Major
> Fix For: 1.6.0
>
> Attachments: guacamole-error.png
>
>
> Hello,
> after installing 1.5.5 we can't connect to rdp targets (linux/windows) if the
> microphone redirection is enabled in the rdp settings dialog. In version
> 1.5.4 everything is working as expected.
>
>
> Working connection without enabled microphone:
>
>
> {code:java}
>
> tomcat:
> [2024-04-11 09:53:52] [info] 09:53:52.286 [http-nio-8080-exec-7] INFO
> o.a.g.tunnel.TunnelRequestService - User "XXX" connected to connection "154".
> guacd:
> Apr 11 09:53:52 rdg-dev guacd[536]: Creating new client for protocol "rdp"
> Apr 11 09:53:52 rdg-dev guacd[536]: guacd[536]: INFO:#011Creating new client
> for protocol "rdp"
> Apr 11 09:53:52 rdg-dev guacd[536]: guacd[536]: INFO:#011Connection ID is
> "$338a4ce1-4249-4ba4-88d6-abe10c1d2f94"
> Apr 11 09:53:52 rdg-dev guacd[536]: Connection ID is
> "$338a4ce1-4249-4ba4-88d6-abe10c1d2f94"
> Apr 11 09:53:52 rdg-dev guacd[23830]: Security mode: Negotiate (ANY)
> Apr 11 09:53:52 rdg-dev guacd[23830]: guacd[23830]: INFO:#011Security mode:
> Negotiate (ANY)
> Apr 11 09:53:52 rdg-dev guacd[23830]: guacd[23830]: INFO:#011Resize method:
> display-update
> Apr 11 09:53:52 rdg-dev guacd[23830]: guacd[23830]: INFO:#011No clipboard
> line-ending normalization specified. Defaulting to preserving the format of
> all line endings.
> Apr 11 09:53:52 rdg-dev guacd[23830]: guacd[23830]: INFO:#011User
> "@09e8a660-12ab-4476-803a-536fc878afe9" joined connection
> "$338a4ce1-4249-4ba4-88d6-abe10c1d2f94" (1 users now present)
> Apr 11 09:53:52 rdg-dev guacd[23830]: Resize method: display-update
> Apr 11 09:53:52 rdg-dev guacd[23830]: No clipboard line-ending normalization
> specified. Defaulting to preserving the format of all line endings.
> Apr 11 09:53:52 rdg-dev guacd[23830]: User
> "@09e8a660-12ab-4476-803a-536fc878afe9" joined connection
> "$338a4ce1-4249-4ba4-88d6-abe10c1d2f94" (1 users now present)
> Apr 11 09:53:52 rdg-dev guacd[23830]: Loading keymap "base"
> Apr 11 09:53:52 rdg-dev guacd[23830]: guacd[23830]: INFO:#011Loading keymap
> "base"
> Apr 11 09:53:52 rdg-dev guacd[23830]: guacd[23830]: INFO:#011Loading keymap
> "de-de-qwertz"
> Apr 11 09:53:52 rdg-dev guacd[23830]: Loading keymap "de-de-qwertz"
> Apr 11 09:53:54 rdg-dev guacd[23830]: Connected to RDPDR 1.13 as client 0x0009
> Apr 11 09:53:54 rdg-dev guacd[23830]: guacd[23830]: INFO:#011Connected to
> RDPDR 1.13 as client 0x0009
>
>
> {code}
>
> Failed connection with enabled microphone:
>
>
> {code:java}
> tomcat:
> [2024-04-11 09:51:03] [info] 09:51:03.364 [http-nio-8080-exec-5] INFO
> o.a.g.tunnel.TunnelRequestService - User "XXX" connected to connection "154".
> guacd:
> Apr 11 09:51:03 rdg-dev guacd[536]: Creating new client for protocol "rdp"
> Apr 11 09:51:03 rdg-dev guacd[536]: guacd[536]: INFO:#011Creating new client
> for protocol "rdp"
> Apr 11 09:51:03 rdg-dev guacd[536]: guacd[536]: INFO:#011Connection ID is
> "$85523c97-55d9-4e63-9027-f9dac8371efc"
> Apr 11 09:51:03 rdg-dev guacd[536]: Connection ID is
> "$85523c97-55d9-4e63-9027-f9dac8371efc"
> Apr 11 09:51:03 rdg-dev guacd[22025]: Security mode: Negotiate (ANY)
> Apr 11 09:51:03 rdg-dev guacd[22025]: guacd[22025]: INFO:#011Security mode:
> Negotiate (ANY)
> Apr 11 09:51:03 rdg-dev guacd[22025]: guacd[22025]: INFO:#011Resize method:
> display-update
> Apr 11 09:51:03 rdg-dev guacd[22025]: guacd[22025]: INFO:#011No clipboard
> line-ending normalization specified. Defaulting to preserving the format of
> all line endings.
> Apr 11 09:51:03 rdg-dev guacd[22025]: guacd[22025]: INFO:#011User
> "@4be353f0-b143-4d11-a0c1-e04c2547fd45" joined connection
>
[jira] [Updated] (GUACAMOLE-1940) rdp-connect failed when microphone input is enabled
[
https://issues.apache.org/jira/browse/GUACAMOLE-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman updated GUACAMOLE-1940:
-
Fix Version/s: 1.6.0
> rdp-connect failed when microphone input is enabled
> ---
>
> Key: GUACAMOLE-1940
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1940
> Project: Guacamole
> Issue Type: Bug
> Components: RDP
>Affects Versions: 1.5.5
> Environment: GUACD-INTRANET-SERVER:
> OS: Linux rdg-dev 5.10.0-28-amd64 #1 SMP Debian 5.10.209-2 (2024-01-31)
> x86_64 GNU/Linux
> GUACD: Guacamole proxy daemon (guacd) version 1.5.5
> TOMCAT-DMZ-SERVER:
> OS: Linux rdg-dev 5.10.0-28-amd64 #1 SMP Debian 5.10.209-2 (2024-01-31)
> x86_64 GNU/Linux
> TOMCAT: tomcat99.0.43-2~deb11u9 all
> Apache Tomcat 9 - Servlet and JSP engine
> JAVA: openjdk version "11.0.22" 2024-01-16
> OpenJDK Runtime Environment (build 11.0.22+7-post-Debian-1deb11u1)
> OpenJDK 64-Bit Server VM (build 11.0.22+7-post-Debian-1deb11u1, mixed
> mode, sharing)
>Reporter: Karsten
>Priority: Major
> Fix For: 1.6.0
>
> Attachments: guacamole-error.png
>
>
> Hello,
> after installing 1.5.5 we can't connect to rdp targets (linux/windows) if the
> microphone redirection is enabled in the rdp settings dialog. In version
> 1.5.4 everything is working as expected.
>
>
> Working connection without enabled microphone:
>
>
> {code:java}
>
> tomcat:
> [2024-04-11 09:53:52] [info] 09:53:52.286 [http-nio-8080-exec-7] INFO
> o.a.g.tunnel.TunnelRequestService - User "XXX" connected to connection "154".
> guacd:
> Apr 11 09:53:52 rdg-dev guacd[536]: Creating new client for protocol "rdp"
> Apr 11 09:53:52 rdg-dev guacd[536]: guacd[536]: INFO:#011Creating new client
> for protocol "rdp"
> Apr 11 09:53:52 rdg-dev guacd[536]: guacd[536]: INFO:#011Connection ID is
> "$338a4ce1-4249-4ba4-88d6-abe10c1d2f94"
> Apr 11 09:53:52 rdg-dev guacd[536]: Connection ID is
> "$338a4ce1-4249-4ba4-88d6-abe10c1d2f94"
> Apr 11 09:53:52 rdg-dev guacd[23830]: Security mode: Negotiate (ANY)
> Apr 11 09:53:52 rdg-dev guacd[23830]: guacd[23830]: INFO:#011Security mode:
> Negotiate (ANY)
> Apr 11 09:53:52 rdg-dev guacd[23830]: guacd[23830]: INFO:#011Resize method:
> display-update
> Apr 11 09:53:52 rdg-dev guacd[23830]: guacd[23830]: INFO:#011No clipboard
> line-ending normalization specified. Defaulting to preserving the format of
> all line endings.
> Apr 11 09:53:52 rdg-dev guacd[23830]: guacd[23830]: INFO:#011User
> "@09e8a660-12ab-4476-803a-536fc878afe9" joined connection
> "$338a4ce1-4249-4ba4-88d6-abe10c1d2f94" (1 users now present)
> Apr 11 09:53:52 rdg-dev guacd[23830]: Resize method: display-update
> Apr 11 09:53:52 rdg-dev guacd[23830]: No clipboard line-ending normalization
> specified. Defaulting to preserving the format of all line endings.
> Apr 11 09:53:52 rdg-dev guacd[23830]: User
> "@09e8a660-12ab-4476-803a-536fc878afe9" joined connection
> "$338a4ce1-4249-4ba4-88d6-abe10c1d2f94" (1 users now present)
> Apr 11 09:53:52 rdg-dev guacd[23830]: Loading keymap "base"
> Apr 11 09:53:52 rdg-dev guacd[23830]: guacd[23830]: INFO:#011Loading keymap
> "base"
> Apr 11 09:53:52 rdg-dev guacd[23830]: guacd[23830]: INFO:#011Loading keymap
> "de-de-qwertz"
> Apr 11 09:53:52 rdg-dev guacd[23830]: Loading keymap "de-de-qwertz"
> Apr 11 09:53:54 rdg-dev guacd[23830]: Connected to RDPDR 1.13 as client 0x0009
> Apr 11 09:53:54 rdg-dev guacd[23830]: guacd[23830]: INFO:#011Connected to
> RDPDR 1.13 as client 0x0009
>
>
> {code}
>
> Failed connection with enabled microphone:
>
>
> {code:java}
> tomcat:
> [2024-04-11 09:51:03] [info] 09:51:03.364 [http-nio-8080-exec-5] INFO
> o.a.g.tunnel.TunnelRequestService - User "XXX" connected to connection "154".
> guacd:
> Apr 11 09:51:03 rdg-dev guacd[536]: Creating new client for protocol "rdp"
> Apr 11 09:51:03 rdg-dev guacd[536]: guacd[536]: INFO:#011Creating new client
> for protocol "rdp"
> Apr 11 09:51:03 rdg-dev guacd[536]: guacd[536]: INFO:#011Connection ID is
> "$85523c97-55d9-4e63-9027-f9dac8371efc"
> Apr 11 09:51:03 rdg-dev guacd[536]: Connection ID is
> "$85523c97-55d9-4e63-9027-f9dac8371efc"
> Apr 11 09:51:03 rdg-dev guacd[22025]: Security mode: Negotiate (ANY)
> Apr 11 09:51:03 rdg-dev guacd[22025]: guacd[22025]: INFO:#011Security mode:
> Negotiate (ANY)
> Apr 11 09:51:03 rdg-dev guacd[22025]: guacd[22025]: INFO:#011Resize method:
> display-update
> Apr 11 09:51:03 rdg-dev guacd[22025]: guacd[22025]: INFO:#011No clipboard
> line-ending normalization specified. Defaulting to preserving the format of
> all line endings.
> Apr 11 09:51:03 rdg-dev guacd[22025]: guacd[22025]: INFO:#011User
> "@4be353f0-b143-4d11-a0c1-e04c2547fd45" joined connection
>
[jira] [Commented] (GUACAMOLE-925) Add Russian keyboard support for RDP
[ https://issues.apache.org/jira/browse/GUACAMOLE-925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17837337#comment-17837337 ] Nick Couchman commented on GUACAMOLE-925: - [~nickstep]: Thanks for the information this. In regard to your feedback: * The transmission of Unicde in absence of the proper scancodes is an intended feature - as you mention, the solution is to make sure the scancodes are being sent, which means having a correct, up-to-date keymap. * Thank you for providing the updated keymap - it would be great if you could open a pull request on Github with this information and we can get it merged into the code. > Add Russian keyboard support for RDP > > > Key: GUACAMOLE-925 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-925 > Project: Guacamole > Issue Type: Improvement > Components: RDP >Affects Versions: 1.0.0 >Reporter: Roman Adyev >Priority: Minor > Attachments: SCREEN.jpg, apache_guacamole_Russian_layouts.txt, > image-2021-01-04-14-42-50-393.png, ru_ru_qwerty-2.keymap, ru_ru_qwerty.keymap > > > Hello, dear support team! > I'm using Unicode layout because Russian layout isn't presented there, but > with Unicode layout I can't send keyboard shortcuts to remote RDP machine > (CTRL + C for example). > If I switch Unicode to English layout in connection settings, I can do > keyboard shortcuts but unfortunately some signs doesn't match when I use RU > layout, for example instead of period sign I got Russian letter "ю". > The keyboard layouts on remote and local machine are identical, that's 100%, > tested many times on different clean windows 10 installs, on work, on VMs, on > friend's PCs, etc. The issue always the same. > As I can see Russian layout isn't presented in Guacamole connection settings > by itself so it would be highly appreciated if you can suggest any workaround > for Russian users. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (GUACAMOLE-1942) First user login with enforced option "password expired" not working due to sessionproblem
[ https://issues.apache.org/jira/browse/GUACAMOLE-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman closed GUACAMOLE-1942. Resolution: Duplicate > First user login with enforced option "password expired" not working due to > sessionproblem > -- > > Key: GUACAMOLE-1942 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1942 > Project: Guacamole > Issue Type: Bug > Components: guacamole >Affects Versions: 1.5.5 > Environment: GUACD-INTRANET-SERVER: > OS: Linux rdg-dev 5.10.0-28-amd64 #1 SMP Debian 5.10.209-2 (2024-01-31) > x86_64 GNU/Linux > GUACD: Guacamole proxy daemon (guacd) version 1.5.5 > TOMCAT-DMZ-SERVER: > OS: Linux rdg-dev 5.10.0-28-amd64 #1 SMP Debian 5.10.209-2 (2024-01-31) > x86_64 GNU/Linux > TOMCAT: tomcat99.0.43-2~deb11u9 all > Apache Tomcat 9 - Servlet and JSP engine > JAVA: openjdk version "11.0.22" 2024-01-16 > OpenJDK Runtime Environment (build 11.0.22+7-post-Debian-1deb11u1) > OpenJDK 64-Bit Server VM (build 11.0.22+7-post-Debian-1deb11u1, mixed > mode, sharing) >Reporter: Karsten >Priority: Major > > Hello, > for onboarding purpose we set the checkbox „password is expired“ to force new > users to change their initial password to a custom one. We also enforce totp. > > Problem since a few versions: > > # user signs in with initial password a > # user forced to change password a to a custom password b > # user pairs totp to authenticator > # user gets redirected to login panel > # login with password a and b not working > # Only using incognito or a newly opened browserwindow made it possible to > login with password b - session problem? > # Now password b is working but the otp dialog requires confirmation again > with entering totp code (setup window with qr code is shown) > It worked until some versions ago. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GUACAMOLE-1658) Unable to compile guacamole server with --enable-ssh-agent
[ https://issues.apache.org/jira/browse/GUACAMOLE-1658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836823#comment-17836823 ] Nick Couchman commented on GUACAMOLE-1658: -- Looking at the 0.9.7 code, along with the functions provided by libssh2, I think they are getting at slightly different functionality: * If I read the code from 0.9.7 correctly, it's actually implementing ssh-agent functionality, effectively completely replacing ssh-agent and allowing what I've described above - a user logging in with a private key will have that private key accessible via agent forwarding. * The libssh2 functions handle the forwarding, but expect that you're going to be running ssh-agent somewhere on the system where the libssh2 code is running (where guacd runs, in this case), and that you'll connect to that libssh2 agent. That being the case, we either need to: * Update the code from 0.9.7 and make it functional, again, which really means either re-implementing or replacing the ssh_key functionality, OR * Use the libssh2 functions, but also have the code start up a copy of ssh-agent, add the identity, and set up the forwarding, and then tear it all down when it's done. > 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)
[jira] [Assigned] (GUACAMOLE-1068) Randomize generation of TOTP key until enrollment is confirmed
[ https://issues.apache.org/jira/browse/GUACAMOLE-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman reassigned GUACAMOLE-1068: Assignee: Nick Couchman > Randomize generation of TOTP key until enrollment is confirmed > -- > > Key: GUACAMOLE-1068 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1068 > Project: Guacamole > Issue Type: Improvement > Components: guacamole-auth-totp >Reporter: Marcos >Assignee: Nick Couchman >Priority: Minor > > When activating TOTP 2 factor authentication, the first time a user enters > his credentials, the TOTP key is inserted in the database and the QR code is > shown. If the user does not complete the enrollment by entering the OTP code, > the key remains in the database and it will be reused next time he tries > again. > This opens a window between when the account is created and when the user > indeed verifies the OTP token, where an attacker that already knows the > username and password of the user, can get the generated OTP token. It will > be the same that the user gets when he finishes enrolment. The user doesn't > know that this key has been stolen and can be used in the future. > Security would be increased if the key would be generated randomly every time > until the pin code is entered and the enrolment process is finished, as the > malicious user would get a different key, and only the key validated by > entering the pin would be stored in the database. The attacker would be able > to get a key, but when the legitimate user tries to login and the QR code is > not displayed anymore the attack would be uncovered. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GUACAMOLE-1940) rdp-connect failed when microphone input is enabled
[
https://issues.apache.org/jira/browse/GUACAMOLE-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836604#comment-17836604
]
Nick Couchman commented on GUACAMOLE-1940:
--
Thanks [~ehprf] - sounds like we have a race condition with that lock where it
has already been acquired and never gets released.
> rdp-connect failed when microphone input is enabled
> ---
>
> Key: GUACAMOLE-1940
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1940
> Project: Guacamole
> Issue Type: Bug
> Components: RDP
>Affects Versions: 1.5.5
> Environment: GUACD-INTRANET-SERVER:
> OS: Linux rdg-dev 5.10.0-28-amd64 #1 SMP Debian 5.10.209-2 (2024-01-31)
> x86_64 GNU/Linux
> GUACD: Guacamole proxy daemon (guacd) version 1.5.5
> TOMCAT-DMZ-SERVER:
> OS: Linux rdg-dev 5.10.0-28-amd64 #1 SMP Debian 5.10.209-2 (2024-01-31)
> x86_64 GNU/Linux
> TOMCAT: tomcat99.0.43-2~deb11u9 all
> Apache Tomcat 9 - Servlet and JSP engine
> JAVA: openjdk version "11.0.22" 2024-01-16
> OpenJDK Runtime Environment (build 11.0.22+7-post-Debian-1deb11u1)
> OpenJDK 64-Bit Server VM (build 11.0.22+7-post-Debian-1deb11u1, mixed
> mode, sharing)
>Reporter: Karsten
>Priority: Major
>
> Hello,
> after installing 1.5.5 we can't connect to rdp targets (linux/windows) if the
> microphone redirection is enabled in the rdp settings dialog. In version
> 1.5.4 everything is working as expected.
>
>
> Working connection without enabled microphone:
>
>
> {code:java}
>
> tomcat:
> [2024-04-11 09:53:52] [info] 09:53:52.286 [http-nio-8080-exec-7] INFO
> o.a.g.tunnel.TunnelRequestService - User "XXX" connected to connection "154".
> guacd:
> Apr 11 09:53:52 rdg-dev guacd[536]: Creating new client for protocol "rdp"
> Apr 11 09:53:52 rdg-dev guacd[536]: guacd[536]: INFO:#011Creating new client
> for protocol "rdp"
> Apr 11 09:53:52 rdg-dev guacd[536]: guacd[536]: INFO:#011Connection ID is
> "$338a4ce1-4249-4ba4-88d6-abe10c1d2f94"
> Apr 11 09:53:52 rdg-dev guacd[536]: Connection ID is
> "$338a4ce1-4249-4ba4-88d6-abe10c1d2f94"
> Apr 11 09:53:52 rdg-dev guacd[23830]: Security mode: Negotiate (ANY)
> Apr 11 09:53:52 rdg-dev guacd[23830]: guacd[23830]: INFO:#011Security mode:
> Negotiate (ANY)
> Apr 11 09:53:52 rdg-dev guacd[23830]: guacd[23830]: INFO:#011Resize method:
> display-update
> Apr 11 09:53:52 rdg-dev guacd[23830]: guacd[23830]: INFO:#011No clipboard
> line-ending normalization specified. Defaulting to preserving the format of
> all line endings.
> Apr 11 09:53:52 rdg-dev guacd[23830]: guacd[23830]: INFO:#011User
> "@09e8a660-12ab-4476-803a-536fc878afe9" joined connection
> "$338a4ce1-4249-4ba4-88d6-abe10c1d2f94" (1 users now present)
> Apr 11 09:53:52 rdg-dev guacd[23830]: Resize method: display-update
> Apr 11 09:53:52 rdg-dev guacd[23830]: No clipboard line-ending normalization
> specified. Defaulting to preserving the format of all line endings.
> Apr 11 09:53:52 rdg-dev guacd[23830]: User
> "@09e8a660-12ab-4476-803a-536fc878afe9" joined connection
> "$338a4ce1-4249-4ba4-88d6-abe10c1d2f94" (1 users now present)
> Apr 11 09:53:52 rdg-dev guacd[23830]: Loading keymap "base"
> Apr 11 09:53:52 rdg-dev guacd[23830]: guacd[23830]: INFO:#011Loading keymap
> "base"
> Apr 11 09:53:52 rdg-dev guacd[23830]: guacd[23830]: INFO:#011Loading keymap
> "de-de-qwertz"
> Apr 11 09:53:52 rdg-dev guacd[23830]: Loading keymap "de-de-qwertz"
> Apr 11 09:53:54 rdg-dev guacd[23830]: Connected to RDPDR 1.13 as client 0x0009
> Apr 11 09:53:54 rdg-dev guacd[23830]: guacd[23830]: INFO:#011Connected to
> RDPDR 1.13 as client 0x0009
>
>
> {code}
>
> Failed connection with enabled microphone:
>
>
> {code:java}
> tomcat:
> [2024-04-11 09:51:03] [info] 09:51:03.364 [http-nio-8080-exec-5] INFO
> o.a.g.tunnel.TunnelRequestService - User "XXX" connected to connection "154".
> guacd:
> Apr 11 09:51:03 rdg-dev guacd[536]: Creating new client for protocol "rdp"
> Apr 11 09:51:03 rdg-dev guacd[536]: guacd[536]: INFO:#011Creating new client
> for protocol "rdp"
> Apr 11 09:51:03 rdg-dev guacd[536]: guacd[536]: INFO:#011Connection ID is
> "$85523c97-55d9-4e63-9027-f9dac8371efc"
> Apr 11 09:51:03 rdg-dev guacd[536]: Connection ID is
> "$85523c97-55d9-4e63-9027-f9dac8371efc"
> Apr 11 09:51:03 rdg-dev guacd[22025]: Security mode: Negotiate (ANY)
> Apr 11 09:51:03 rdg-dev guacd[22025]: guacd[22025]: INFO:#011Security mode:
> Negotiate (ANY)
> Apr 11 09:51:03 rdg-dev guacd[22025]: guacd[22025]: INFO:#011Resize method:
> display-update
> Apr 11 09:51:03 rdg-dev guacd[22025]: guacd[22025]: INFO:#011No clipboard
> line-ending normalization specified. Defaulting to preserving the format of
> all line endings.
> Apr 11 09:51:03 rdg-dev guacd[22025]: guacd[22025]: INFO:#011User
>
[jira] [Commented] (GUACAMOLE-1920) When the cumulative number of user connections reaches a certain amount, guacd will report an error. "RDP server closed/refused connection: Security negotiation fai
[
https://issues.apache.org/jira/browse/GUACAMOLE-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17835700#comment-17835700
]
Nick Couchman commented on GUACAMOLE-1920:
--
[~aylin]: This issue has been closed and fixed, and the version has been
released. Please do not update or reopen these issues.
> When the cumulative number of user connections reaches a certain amount,
> guacd will report an error. "RDP server closed/refused connection: Security
> negotiation failed (wrong security type?)”
> ---
>
> Key: GUACAMOLE-1920
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1920
> Project: Guacamole
> Issue Type: Bug
> Components: guacd
>Affects Versions: 1.5.4
>Reporter: CaoShulin
>Assignee: James Muehlner
>Priority: Minor
> Fix For: 1.5.5
>
>
> ||Local host:|Windows host|
> ||Remote host:|Windows host|
> ||Guacamole version:|1.5.4|
> ||Protocol:|rdp|
> When the cumulative number of user connections reaches a certain amount,
> guacd will report an error: "RDP server closed/refused connection: Security
> negotiation failed (wrong security type?)"
> {code:none}
> Feb 4 16:51:48 guacd[2038]: Creating new client for protocol "rdp"
> Feb 4 16:51:48 guacd[2038]: Connection ID is
> "$514ed1c3-2756-4d9f-8153-6388354873cc"
> Feb 4 16:51:48 guacd[991760]: Security mode: RDP
> Feb 4 16:51:48 guacd[991760]: Resize method: reconnect
> Feb 4 16:51:48 guacd[991760]: No clipboard line-ending normalization
> specified. Defaulting to preserving the format of all line endings.
> Feb 4 16:51:48 guacd[991760]: User "@5259dffd-eb02-42df-9b82-18de1b87457f"
> joined connection "$8ea080a2-1da5-4221-a828-823160906743" (1 users now
> present)
> Feb 4 16:51:48 guacd[991760]: Loading keymap "base"
> Feb 4 16:51:48 guacd[991760]: Loading keymap "en-us-qwerty"
> Feb 4 16:51:48 guacd[991764]: Security mode: RDP
> Feb 4 16:51:48 guacd[991764]: Resize method: reconnect
> Feb 4 16:51:48 guacd[991764]: No clipboard line-ending normalization
> specified. Defaulting to preserving the format of all line endings.
> Feb 4 16:51:48 guacd[991764]: User "@3814f8a9-f362-4b1e-9eb1-30fe6ed7c62b"
> joined connection "$514ed1c3-2756-4d9f-8153-6388354873cc" (1 users now
> present)
> Feb 4 16:51:48 guacd[991764]: Loading keymap "base"
> Feb 4 16:51:48 guacd[991764]: Loading keymap "en-us-qwerty"
> Feb 4 16:51:48 guacd[991764]: RDP server closed/refused connection: Security
> negotiation failed (wrong security type?)
> {code}
> When you try to access again, an error occurs: "segfault at 20 ip
> 7ff86708f848 sp 7ff83affc9c0 error 4 in
> libdl-2.28.so[7ff86708f000+1000]"
> {code:none}
> Feb 4 11:16:51 guacd[2507120]: Creating new client for protocol "rdp"
> Feb 4 11:16:51 guacd[2507120]: Connection ID is
> "$35290a32-8188-4bbb-9d7d-5e181be83e25"
> Feb 4 11:16:51 audit[3804338]: ANOM_ABEND auid=0 uid=0 gid=0 ses=8
> pid=3804338 comm="guacd" exe="/usr/local/sbin/guacd" sig=11 res=1
> Feb 4 11:16:51 kernel: [143626.086546] guacd[3804338]: segfault at 85 ip
> 7f5a1d96a77d sp 7f5951f929c0 error 4 in
> libdl-2.28.so[7f5a1d96a000+1000]
> Feb 4 11:16:51 kernel: [143626.086550] Code: c3 0f 84 96 00 00 00 8b 53 04
> 48 8b 43 18 85 d2 0f 84 9d 00 00 00 48 85 c0 74 1f 48 8d 3d a2 08 00 00 b9 0e
> 00 00 00 48 89 c6 a6 0f 85 7b 01 00 00 48 c7 43 18 00 00 00 00 48 8b 04
> 24 e9 63
> Feb 4 11:16:51 guacd[2507120]: Connection
> "$35290a32-8188-4bbb-9d7d-5e181be83e25" removed.
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (GUACAMOLE-1937) The user is disconnected after a period of time, and the buff/cache is not released
[ https://issues.apache.org/jira/browse/GUACAMOLE-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman closed GUACAMOLE-1937. Resolution: Invalid [~aylin]: Please do not re-open and re-categorize issues like this. Mike closed this specifically with the "Invalid" resolution because it is not a valid issue. > The user is disconnected after a period of time, and the buff/cache is not > released > --- > > Key: GUACAMOLE-1937 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1937 > Project: Guacamole > Issue Type: Bug > Components: guacd >Affects Versions: 1.5.4 >Reporter: CaoShulin >Priority: Minor > Attachments: image-2024-04-03-18-00-25-010.png, > image-2024-04-10-17-10-08-007.png > > > Local host: Windows host > Remote host: Windows host > guacamole version: 1.5.4 > Protocol: rdp > guacd：EulerOS 2.9 64bit | 4vCPUs | 8GiB > To test the guacamole, use free -h to see the initial memory of the guacd > server, as shown in Figure 1. With the continuous access of users, about 100 > people were connected for 2 hours. The memory of the guacd server was > checked, and it was found that the memory of the guacd server was > continuously increased. However, after the connection was disconnected, the > memory occupied by buff/cache was not released, as shown in Figure 2. Please > help analyze whether guacd has memory leakage problem. > Figure 1: > !image-2024-04-10-17-10-08-007.png! > Figure 2: > !image-2024-04-03-18-00-25-010.png! > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GUACAMOLE-1939) After testing guacamole, the number of tcp link states in close_wait exceeds the number of established states
[ https://issues.apache.org/jira/browse/GUACAMOLE-1939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17835698#comment-17835698 ] Nick Couchman commented on GUACAMOLE-1939: -- [~aylin]: The "CLOSED_WAIT" state is not something that Guacamole has any control over. This is a function of the TCP stack in the underlying operating system (Linux, in the case of Guacamole), and how long it leaves closed sessions around before cleaning them up. Also, in the future, if you have questions about Guacamole's behavior, performance, etc., please post them to the mailing list, first rather than opening Jira issues. After a discussion on the mailing list, if a bug or required feature is identified you can proceed to open a Jira ticket, but it would be better for these types of questions and discussions to be held on the mailing list, first. > After testing guacamole, the number of tcp link states in close_wait exceeds > the number of established states > - > > Key: GUACAMOLE-1939 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1939 > Project: Guacamole > Issue Type: Bug >Reporter: CaoShulin >Priority: Major > Attachments: 1.png > > > Local host: Windows host > Remote host: Windows host > guacamole version: 1.5.4 > Protocol: rdp > guacd：EulerOS 2.9 64bit | 4vCPUs | 8GiB > Pressure test guacamole with jmeter. After the pressure test is stopped, the > guacd server will have a close_wait tcp link state. Close_wait exceeds the > number established. And the close_wait number will not be reduced, but will > accumulate. See the attached picture.. Is the code not robust enough? > !image-2024-04-10-17-56-47-729.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (GUACAMOLE-1939) After testing guacamole, the number of tcp link states in close_wait exceeds the number of established states
[ https://issues.apache.org/jira/browse/GUACAMOLE-1939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman closed GUACAMOLE-1939. Resolution: Invalid > After testing guacamole, the number of tcp link states in close_wait exceeds > the number of established states > - > > Key: GUACAMOLE-1939 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1939 > Project: Guacamole > Issue Type: Bug >Reporter: CaoShulin >Priority: Major > Attachments: 1.png > > > Local host: Windows host > Remote host: Windows host > guacamole version: 1.5.4 > Protocol: rdp > guacd：EulerOS 2.9 64bit | 4vCPUs | 8GiB > Pressure test guacamole with jmeter. After the pressure test is stopped, the > guacd server will have a close_wait tcp link state. Close_wait exceeds the > number established. And the close_wait number will not be reduced, but will > accumulate. See the attached picture.. Is the code not robust enough? > !image-2024-04-10-17-56-47-729.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (GUACAMOLE-1937) The user is disconnected after a period of time, and the buff/cache is not released
[ https://issues.apache.org/jira/browse/GUACAMOLE-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman reopened GUACAMOLE-1937: -- > The user is disconnected after a period of time, and the buff/cache is not > released > --- > > Key: GUACAMOLE-1937 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1937 > Project: Guacamole > Issue Type: Bug > Components: guacd >Affects Versions: 1.5.4 >Reporter: CaoShulin >Priority: Minor > Attachments: image-2024-04-03-18-00-25-010.png, > image-2024-04-10-17-10-08-007.png > > > Local host: Windows host > Remote host: Windows host > guacamole version: 1.5.4 > Protocol: rdp > guacd：EulerOS 2.9 64bit | 4vCPUs | 8GiB > To test the guacamole, use free -h to see the initial memory of the guacd > server, as shown in Figure 1. With the continuous access of users, about 100 > people were connected for 2 hours. The memory of the guacd server was > checked, and it was found that the memory of the guacd server was > continuously increased. However, after the connection was disconnected, the > memory occupied by buff/cache was not released, as shown in Figure 2. Please > help analyze whether guacd has memory leakage problem. > Figure 1: > !image-2024-04-10-17-10-08-007.png! > Figure 2: > !image-2024-04-03-18-00-25-010.png! > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GUACAMOLE-1658) Unable to compile guacamole server with --enable-ssh-agent
[ https://issues.apache.org/jira/browse/GUACAMOLE-1658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
[jira] [Commented] (GUACAMOLE-1289) Update guacamole-auth-duo to "Duo Web v4 SDK"
[
https://issues.apache.org/jira/browse/GUACAMOLE-1289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17835574#comment-17835574
]
Nick Couchman commented on GUACAMOLE-1289:
--
Alexander has finished up the code changes for this, and it has been merged.
There's some documentation left to do, now, but should be ready to ship with
1.6.0 release.
> Update guacamole-auth-duo to "Duo Web v4 SDK"
> -
>
> Key: GUACAMOLE-1289
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1289
> Project: Guacamole
> Issue Type: Task
> Components: Documentation, guacamole-auth-duo
>Reporter: Mike Jumper
>Assignee: Alexander Leitner
>Priority: Major
> Fix For: 1.6.0
>
> Attachments: bGVZLZv.png
>
>
> It looks like there have been some changes to the Duo API/SDK which require
> updates to the guacamole-auth-duo extension. As reported by Ralph on the
> user@ mailing list:
> {quote}
> So we're setting up Duo for use on our Guacamole system, and whilst setting
> up the web SDK I noticed this message (see screenshot link): [^bGVZLZv.png]
> This states that there are some changes needed on the web application (The
> Duo Extension in this case). I'm by no means a developer, so I hope this is
> being posted in the correct place, and someone can work on getting the
> extension updated with the requested changes moving forward. Below is a link
> to Duo's Documentation for these changes.
> Thanks!
> https://duo.com/docs/duoweb-v4
> {quote}
> See:
> https://lists.apache.org/thread.html/r707e962d6f856234964e9a51c94d0719b1a5b116bfe9b78e787013b2%40%3Cuser.guacamole.apache.org%3E
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (GUACAMOLE-1325) Apache Tomcat 10.0 Servlet API incompatibility
[ https://issues.apache.org/jira/browse/GUACAMOLE-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-1325: - Fix Version/s: 2.0.0 > Apache Tomcat 10.0 Servlet API incompatibility > -- > > Key: GUACAMOLE-1325 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1325 > Project: Guacamole > Issue Type: Improvement > Components: guacamole, guacamole-common, guacamole-ext >Reporter: Mathias >Assignee: Nick Couchman >Priority: Major > Fix For: 2.0.0 > > > Guacamole client 1.3.0 is not working with Apache Tomcat 10. Apache Tomcat > 10.0.x requires a new Servlet 5.0 API. The Java package has changed from > javax.servlet to jakarta.servlet. > [Migrating from Tomcat 9.0 to 10.0|http://tomcat.apache.org/migration-10.html] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GUACAMOLE-1085) Consider migrating web application from AngularJS
[ https://issues.apache.org/jira/browse/GUACAMOLE-1085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-1085: - Fix Version/s: 2.0.0 > Consider migrating web application from AngularJS > - > > Key: GUACAMOLE-1085 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1085 > Project: Guacamole > Issue Type: Improvement > Components: guacamole >Reporter: Alfred Egger >Priority: Major > Fix For: 2.0.0 > > > [AngularJS is in an LTS period until June 30, > 2021|https://blog.angular.io/stable-angularjs-and-long-term-support-7e077635ee9c]. > Unless resurrected as a community-driven project, it will be cease being > maintained after that date. Assuming no such project surfaces, we should look > into migrate the web application to another framework. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GUACAMOLE-1325) Apache Tomcat 10.0 Servlet API incompatibility
[ https://issues.apache.org/jira/browse/GUACAMOLE-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-1325: - Affects Version/s: (was: 1.3.0) (was: 1.4.0) > Apache Tomcat 10.0 Servlet API incompatibility > -- > > Key: GUACAMOLE-1325 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1325 > Project: Guacamole > Issue Type: Improvement > Components: guacamole, guacamole-common, guacamole-ext >Reporter: Mathias >Assignee: Nick Couchman >Priority: Major > > Guacamole client 1.3.0 is not working with Apache Tomcat 10. Apache Tomcat > 10.0.x requires a new Servlet 5.0 API. The Java package has changed from > javax.servlet to jakarta.servlet. > [Migrating from Tomcat 9.0 to 10.0|http://tomcat.apache.org/migration-10.html] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (GUACAMOLE-1325) Apache Tomcat 10.0 Servlet API incompatibility
[ https://issues.apache.org/jira/browse/GUACAMOLE-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman reassigned GUACAMOLE-1325: Assignee: Nick Couchman > Apache Tomcat 10.0 Servlet API incompatibility > -- > > Key: GUACAMOLE-1325 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1325 > Project: Guacamole > Issue Type: Improvement > Components: guacamole, guacamole-common, guacamole-ext >Affects Versions: 1.3.0, 1.4.0 >Reporter: Mathias >Assignee: Nick Couchman >Priority: Major > > Guacamole client 1.3.0 is not working with Apache Tomcat 10. Apache Tomcat > 10.0.x requires a new Servlet 5.0 API. The Java package has changed from > javax.servlet to jakarta.servlet. > [Migrating from Tomcat 9.0 to 10.0|http://tomcat.apache.org/migration-10.html] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GUACAMOLE-1325) Apache Tomcat 10.0 Servlet API incompatibility
[ https://issues.apache.org/jira/browse/GUACAMOLE-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834746#comment-17834746 ] Nick Couchman commented on GUACAMOLE-1325: -- This may be what is required to get things to run under Tomcat 10.x; however, to fully achieve the swap to Jakarta EE there are quite a few classes that need the javax.* items migrated to their jakarta.* counterparts. [~z0rb]: I'm sure there will be a point at which we freeze the feature set, but I'm not sure that will be immediate - I think we probably want to get the 1.6.0 version released, first, before we make such a freeze - depending on how long that takes we can decide if we want to freeze it. Also, with the strategy we have with our branches - patch, main, and next - we should be able to commit changes like the Jakarta transition and Angular migration into the next branch, while still working on other items - patches or features - in main. Obviously the more changes we make the harder it will be to keep up the required migration, so I think a freeze will make sense at some point. > Apache Tomcat 10.0 Servlet API incompatibility > -- > > Key: GUACAMOLE-1325 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1325 > Project: Guacamole > Issue Type: Improvement > Components: guacamole, guacamole-common, guacamole-ext >Affects Versions: 1.3.0, 1.4.0 >Reporter: Mathias >Priority: Major > > Guacamole client 1.3.0 is not working with Apache Tomcat 10. Apache Tomcat > 10.0.x requires a new Servlet 5.0 API. The Java package has changed from > javax.servlet to jakarta.servlet. > [Migrating from Tomcat 9.0 to 10.0|http://tomcat.apache.org/migration-10.html] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (GUACAMOLE-1916) Provide notification, jump-to-top of page for a clone operation
[ https://issues.apache.org/jira/browse/GUACAMOLE-1916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman closed GUACAMOLE-1916. Resolution: Implemented > Provide notification, jump-to-top of page for a clone operation > --- > > Key: GUACAMOLE-1916 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1916 > Project: Guacamole > Issue Type: Improvement > Components: guacamole >Affects Versions: 1.5.4 >Reporter: sbcbus >Assignee: Nick Couchman >Priority: Trivial > Fix For: 1.6.0 > > > Minor thing, but think it would be more user friendly to know if a "clone" of > an object was successful before editing the fields if perhaps a notification > "toast" could say something like "clone successful" and jump to the top of > the page. At least on my systems using Chrome, clicking clone changes the URL > but otherwise doesn't change anything else so it can be a bit confusing > without checking. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (GUACAMOLE-1084) Open a not published RemoteApp isn’t blocked
[ https://issues.apache.org/jira/browse/GUACAMOLE-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman reassigned GUACAMOLE-1084: Assignee: Nick Couchman > Open a not published RemoteApp isn’t blocked > > > Key: GUACAMOLE-1084 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1084 > Project: Guacamole > Issue Type: Bug >Affects Versions: 1.1.0 > Environment: the RDS deployment is running on MS-Server 2016. >Reporter: Robert Bloch >Assignee: Nick Couchman >Priority: Minor > > If open a not published RemoteApp I get logged on and see blackscreen. > Expected behavior is an Error Message and direct logoff. We had that probem > in the passt with older version too. > In single freerdp cleint its working like expected. Error is there > [06:02:21:465] [2460:2466] [ERROR][com.freerdp.client.x11] - RAIL exec error: > execResult=RAIL_EXEC_E_NOT_IN_ALLOWLIST NtError=0x15 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (GUACAMOLE-1267) Add option to the vnc protocol to disable remote input
[ https://issues.apache.org/jira/browse/GUACAMOLE-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman reassigned GUACAMOLE-1267: Assignee: Nick Couchman > Add option to the vnc protocol to disable remote input > -- > > Key: GUACAMOLE-1267 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1267 > Project: Guacamole > Issue Type: New Feature > Components: Documentation, VNC >Reporter: Stefan Feenstra >Assignee: Nick Couchman >Priority: Minor > > For security reasons it can be a required feature to have remote input > disabled when using the VNC protocol (e.g. on remote costumer facing > terminals, self service terminals etc). > > Suggested solution is to add a setting "disable-server-input" which when set > will send a message to the VNC client asking to disable the input. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GUACAMOLE-1289) Update guacamole-auth-duo to "Duo Web v4 SDK"
[
https://issues.apache.org/jira/browse/GUACAMOLE-1289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman updated GUACAMOLE-1289:
-
Component/s: Documentation
> Update guacamole-auth-duo to "Duo Web v4 SDK"
> -
>
> Key: GUACAMOLE-1289
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1289
> Project: Guacamole
> Issue Type: Task
> Components: Documentation, guacamole-auth-duo
>Reporter: Mike Jumper
>Assignee: Alexander Leitner
>Priority: Major
> Fix For: 1.6.0
>
> Attachments: bGVZLZv.png
>
>
> It looks like there have been some changes to the Duo API/SDK which require
> updates to the guacamole-auth-duo extension. As reported by Ralph on the
> user@ mailing list:
> {quote}
> So we're setting up Duo for use on our Guacamole system, and whilst setting
> up the web SDK I noticed this message (see screenshot link): [^bGVZLZv.png]
> This states that there are some changes needed on the web application (The
> Duo Extension in this case). I'm by no means a developer, so I hope this is
> being posted in the correct place, and someone can work on getting the
> extension updated with the requested changes moving forward. Below is a link
> to Duo's Documentation for these changes.
> Thanks!
> https://duo.com/docs/duoweb-v4
> {quote}
> See:
> https://lists.apache.org/thread.html/r707e962d6f856234964e9a51c94d0719b1a5b116bfe9b78e787013b2%40%3Cuser.guacamole.apache.org%3E
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (GUACAMOLE-1916) Provide notification, jump-to-top of page for a clone operation
[ https://issues.apache.org/jira/browse/GUACAMOLE-1916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-1916: - Fix Version/s: 1.6.0 > Provide notification, jump-to-top of page for a clone operation > --- > > Key: GUACAMOLE-1916 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1916 > Project: Guacamole > Issue Type: Improvement > Components: guacamole >Affects Versions: 1.5.4 >Reporter: sbcbus >Assignee: Nick Couchman >Priority: Trivial > Fix For: 1.6.0 > > > Minor thing, but think it would be more user friendly to know if a "clone" of > an object was successful before editing the fields if perhaps a notification > "toast" could say something like "clone successful" and jump to the top of > the page. At least on my systems using Chrome, clicking clone changes the URL > but otherwise doesn't change anything else so it can be a bit confusing > without checking. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (GUACAMOLE-1840) Focus the password field for RDP connections with NLA
[ https://issues.apache.org/jira/browse/GUACAMOLE-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman closed GUACAMOLE-1840. Resolution: Duplicate > Focus the password field for RDP connections with NLA > - > > Key: GUACAMOLE-1840 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1840 > Project: Guacamole > Issue Type: Improvement >Affects Versions: 1.5.2 >Reporter: Aram Akhavan >Priority: Minor > > When connecting to a host with RDP using NLA, when the authentication pops > up, the input field isn't focused. In my case, I have the username set in the > connection settings, so it's just the password. Nonetheless, it's an annoying > extra click! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (GUACAMOLE-1582) Prevent accidential tab closing
[
https://issues.apache.org/jira/browse/GUACAMOLE-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman closed GUACAMOLE-1582.
Resolution: Duplicate
> Prevent accidential tab closing
> ---
>
> Key: GUACAMOLE-1582
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1582
> Project: Guacamole
> Issue Type: Wish
> Components: guacamole
> Environment: Current Firefox on Linux or Windows
>Reporter: Fabio Zuber
>Priority: Minor
>
> Heya{*}{*}
> I'm using the Guacamole website to control a remote machine. Sometimes when
> I'm typing in a terminal, my muscle memory kicks in and I press CTRL+W to
> delete a word. Instead of deleting the word, it closes the guacamole tab.
> I see two ways to improve this:
> * Forward CTRL + W to the remote machine (not sure if possible)
> * Add a onbeforeunload listener to prevent accidental closures via shortcut.
> Example: [https://www.w3schools.com/jsref/event_onbeforeunload.asp]
> Please let me know how you feel about this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (GUACAMOLE-1361) Docker for ARM arch
[ https://issues.apache.org/jira/browse/GUACAMOLE-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman closed GUACAMOLE-1361. Resolution: Duplicate > Docker for ARM arch > --- > > Key: GUACAMOLE-1361 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1361 > Project: Guacamole > Issue Type: Wish > Components: guacamole-docker, guacd-docker >Reporter: PIERRE PINTARIC >Priority: Trivial > > Currently, Docker for Guacamole is distributed only for AMD64 arch > Do you plan to make a portage to ARM64 or ARM32 for all Guacamole components? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (GUACAMOLE-1866) Improvements to the "Recent connections" section
[ https://issues.apache.org/jira/browse/GUACAMOLE-1866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman reassigned GUACAMOLE-1866: Assignee: Nick Couchman > Improvements to the "Recent connections" section > > > Key: GUACAMOLE-1866 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1866 > Project: Guacamole > Issue Type: New Feature > Components: guacamole-client >Reporter: Julien Lejeune >Assignee: Nick Couchman >Priority: Trivial > Fix For: 1.6.0 > > > The "Recent Connections" section takes some place on the Guacamole homepage, > but I have the feeling that it is not useful for all users, only for those > who mostly connect to the same few connections. > This comes from the assumption that the "Recent Connections" section only > shows the five last connections, which is what I have seen so far. Let me > know if I am wrong. > So, I would suggest either of those : > * Allow a user or an administrator to remove or hide the "Recent > Connections" section. > * Improve the usefulness of the "Recent Connections" section so it is useful > to more users. For example, it would be nice to allow a user to remove a > connection showing in the "Recent Connections" section if the user does not > need this suggestion anymore. Also, when a connection is removed that way, > the sixth last connection could come back again in the "Recent Connections" > section. > I am not a developer, so I am not sure how to implement it myself, but I > would be open to try. > First, I would like to read what you all think of those suggestions and where > the discussion goes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (GUACAMOLE-1876) History Recording Player should indicate points of interest
[ https://issues.apache.org/jira/browse/GUACAMOLE-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman reassigned GUACAMOLE-1876: Assignee: James Muehlner (was: Nick Couchman) > History Recording Player should indicate points of interest > --- > > Key: GUACAMOLE-1876 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1876 > Project: Guacamole > Issue Type: Improvement > Components: Documentation, guacamole >Reporter: James Muehlner >Assignee: James Muehlner >Priority: Major > Fix For: 1.6.0 > > > Currently, it's hard to tell where things are happening in a session > recording, other than by playing the whole recording and watching, which can > take a long time. > At load time we have information about when > * Frames were rendered > * Key events occurred > * Mouse events occurred > And a few other data streams to boot. We should expose these in an easy to > read way to the user so they can tell at a glance where the interesting parts > of a recording are. We could consider displaying a histogram / heatmap like > many video players (e.g. youtube) do. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (GUACAMOLE-1876) History Recording Player should indicate points of interest
[ https://issues.apache.org/jira/browse/GUACAMOLE-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman reassigned GUACAMOLE-1876: Assignee: Nick Couchman (was: James Muehlner) > History Recording Player should indicate points of interest > --- > > Key: GUACAMOLE-1876 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1876 > Project: Guacamole > Issue Type: Improvement > Components: Documentation, guacamole >Reporter: James Muehlner >Assignee: Nick Couchman >Priority: Major > Fix For: 1.6.0 > > > Currently, it's hard to tell where things are happening in a session > recording, other than by playing the whole recording and watching, which can > take a long time. > At load time we have information about when > * Frames were rendered > * Key events occurred > * Mouse events occurred > And a few other data streams to boot. We should expose these in an easy to > read way to the user so they can tell at a glance where the interesting parts > of a recording are. We could consider displaying a histogram / heatmap like > many video players (e.g. youtube) do. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GUACAMOLE-1866) Improvements to the "Recent connections" section
[ https://issues.apache.org/jira/browse/GUACAMOLE-1866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-1866: - Fix Version/s: 1.6.0 > Improvements to the "Recent connections" section > > > Key: GUACAMOLE-1866 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1866 > Project: Guacamole > Issue Type: New Feature > Components: guacamole-client >Reporter: Julien Lejeune >Priority: Trivial > Fix For: 1.6.0 > > > The "Recent Connections" section takes some place on the Guacamole homepage, > but I have the feeling that it is not useful for all users, only for those > who mostly connect to the same few connections. > This comes from the assumption that the "Recent Connections" section only > shows the five last connections, which is what I have seen so far. Let me > know if I am wrong. > So, I would suggest either of those : > * Allow a user or an administrator to remove or hide the "Recent > Connections" section. > * Improve the usefulness of the "Recent Connections" section so it is useful > to more users. For example, it would be nice to allow a user to remove a > connection showing in the "Recent Connections" section if the user does not > need this suggestion anymore. Also, when a connection is removed that way, > the sixth last connection could come back again in the "Recent Connections" > section. > I am not a developer, so I am not sure how to implement it myself, but I > would be open to try. > First, I would like to read what you all think of those suggestions and where > the discussion goes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GUACAMOLE-1866) Improvements to the "Recent connections" section
[ https://issues.apache.org/jira/browse/GUACAMOLE-1866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-1866: - Affects Version/s: (was: 1.5.3) > Improvements to the "Recent connections" section > > > Key: GUACAMOLE-1866 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1866 > Project: Guacamole > Issue Type: New Feature > Components: guacamole-client >Reporter: Julien Lejeune >Priority: Trivial > > The "Recent Connections" section takes some place on the Guacamole homepage, > but I have the feeling that it is not useful for all users, only for those > who mostly connect to the same few connections. > This comes from the assumption that the "Recent Connections" section only > shows the five last connections, which is what I have seen so far. Let me > know if I am wrong. > So, I would suggest either of those : > * Allow a user or an administrator to remove or hide the "Recent > Connections" section. > * Improve the usefulness of the "Recent Connections" section so it is useful > to more users. For example, it would be nice to allow a user to remove a > connection showing in the "Recent Connections" section if the user does not > need this suggestion anymore. Also, when a connection is removed that way, > the sixth last connection could come back again in the "Recent Connections" > section. > I am not a developer, so I am not sure how to implement it myself, but I > would be open to try. > First, I would like to read what you all think of those suggestions and where > the discussion goes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (GUACAMOLE-1916) Provide notification, jump-to-top of page for a clone operation
[ https://issues.apache.org/jira/browse/GUACAMOLE-1916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman reassigned GUACAMOLE-1916: Assignee: Nick Couchman > Provide notification, jump-to-top of page for a clone operation > --- > > Key: GUACAMOLE-1916 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1916 > Project: Guacamole > Issue Type: Improvement > Components: guacamole >Affects Versions: 1.5.4 >Reporter: sbcbus >Assignee: Nick Couchman >Priority: Trivial > > Minor thing, but think it would be more user friendly to know if a "clone" of > an object was successful before editing the fields if perhaps a notification > "toast" could say something like "clone successful" and jump to the top of > the page. At least on my systems using Chrome, clicking clone changes the URL > but otherwise doesn't change anything else so it can be a bit confusing > without checking. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GUACAMOLE-1686) extend wol-intelligence
[ https://issues.apache.org/jira/browse/GUACAMOLE-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-1686: - Fix Version/s: 1.6.0 > extend wol-intelligence > --- > > Key: GUACAMOLE-1686 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1686 > Project: Guacamole > Issue Type: Wish > Components: guacamole >Reporter: Karsten >Assignee: Nick Couchman >Priority: Trivial > Fix For: 1.6.0 > > > It would be nice to make the wol-feature more flexible and intelligent: > > * wol-wait-time is appended to the connection process even if the machine is > running > * just try simple connect to the machine and only if this fails send a > wol-event and add the wol-wait-time to the whole process > With these little changes it would be less frustrating in reconnect-events to > not wait untill the wol-wait-time is over... -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (GUACAMOLE-1456) Support configurable "seeAlso" attribute name
[ https://issues.apache.org/jira/browse/GUACAMOLE-1456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman closed GUACAMOLE-1456. Resolution: Won't Fix > Support configurable "seeAlso" attribute name > - > > Key: GUACAMOLE-1456 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1456 > Project: Guacamole > Issue Type: Improvement > Components: guacamole-auth-ldap >Affects Versions: 1.3.0 >Reporter: Florian Best >Priority: Trivial > > The "seeAlso" LDAP attribute name at guacomole config objects seems to be > hardcoded and cannot be configured. > > With a posix based schema we are storing LDAP group memberships in the > "uniqueMember" attribute, e.g.: > > ``` > objectClass ( 1.3.6.1.4.1.38971.1.2.1 NAME 'guacConfigGroup' > DESC 'Guacamole configuration' > STRUCTURAL > MUST ( cn $ guacConfigProtocol ) > MAY ( > description $ > uniqueMember $ > guacConfigParameter > ) > ) > ``` > > with > ``` > dn: cn=SSH,cn=guacamole,dc=mole,dc=test > guacConfigProtocol: ssh > guacConfigParameter: hostname=10.200.72.16 > cn: SSH > objectClass: top > objectClass: guacConfigGroup > uniqueMember: cn=Domain Admins,cn=groups,dc=mole,dc=test > uniqueMember: cn=Domain Users,cn=groups,dc=mole,dc=test > uniqueMember: uid=Administrator,cn=users,dc=mole,dc=test > ``` > > Your code: > ``` > extensions/guacamole-auth-ldap/src/main/java/org/apache/guacamole/auth/ldap/connection/ConnectionService.java: > public static final String LDAP_ATTRIBUTE_NAME_GROUPS = "seeAlso"; > > extensions/guacamole-auth-ldap/src/main/java/org/apache/guacamole/auth/ldap/connection/ConnectionService.java: > LDAP_ATTRIBUTE_NAME_GROUPS > > extensions/guacamole-auth-ldap/src/main/java/org/apache/guacamole/auth/ldap/connection/ConnectionService.java: > groupFilter.addNode(new > EqualityNode(LDAP_ATTRIBUTE_NAME_GROUPS,entry.getDn().toString())) > ``` > > All other LDAP attribute names seem to be configurable in > `~/.guacamole/guacamole.properties` except for `seeAlso`. > Please make it configurable as well! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GUACAMOLE-990) Enforce rate limit on authentication attempts
[ https://issues.apache.org/jira/browse/GUACAMOLE-990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17833727#comment-17833727 ] Nick Couchman commented on GUACAMOLE-990: - [~mjumper]: I think most of the "real" work is done on this, but just some documentation, correct? > Enforce rate limit on authentication attempts > - > > Key: GUACAMOLE-990 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-990 > Project: Guacamole > Issue Type: Improvement > Components: guacamole-auth-totp >Reporter: Graham >Assignee: Mike Jumper >Priority: Trivial > Fix For: 1.6.0 > > > Google's [libpam > module|https://github.com/google/google-authenticator-libpam/blob/master/man/google-authenticator.1.md] > has a rate limit option to prevent brute forcing. > Does Guacamole's TOTP have anything built-in that's introducing any > sleep/delay in the code input loop? > It _seems_ like it doesn't from my clumsy attempts at testing this by just > hammering the keyboard :) > If that's true then it seems like this would potentially be easier to bypass > than even the password itself. I might be butchering the napkin math here, > but with a possible number range of 1 million (6 digits) and 30 seconds, > assuming a WAN latency per attempt of 7ms, that would mean that on average, > once a hacker broke a password, they could then break through the TOTP > segment over a scripted 233 login attempts or so. > If there was even a plain old unconfigurable 1 second sleep/delay (or better > yet, a continually increasing delay of n*1second based on past failure count > in the current cycle) built in to the code input loop between attempts > without even any added guacamole.properties options being introduced, I think > this would basically handle the problem by pushing the possible average > breakthrough time into unreasonable timelines. > Also, though this would be another issue, it seemed that incrementing > totp-digits with v1.1.0 to 8 didn't result in 8 digits being displayed when I > scanned the resulting barcode in google authenticator. The introductory user > bit did specify 8 digits - just not the resulting google authenticator entry. > That may just be a bug in google authenticator however - not sure as I > haven't tested any other TOTP apps, but I thought I'd mention it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
