[jira] [Closed] (GUACAMOLE-976) Apa
[ https://issues.apache.org/jira/browse/GUACAMOLE-976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman closed GUACAMOLE-976. --- Resolution: Invalid > Apa > --- > > Key: GUACAMOLE-976 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-976 > Project: Guacamole > Issue Type: Bug >Reporter: Francisco Alejandro Diaz Damian >Priority: Major > > Utilizando las imágenes de Docker correspondientes a Apache Guacamole 1.1.0, > se produce una desconexión al transcurrir aproximadamente 1 minuto después de > iniciar una sesión RDP a un servidor Windows Version X. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-975) How many concurrent active sessions can Guacamole handle?
[
https://issues.apache.org/jira/browse/GUACAMOLE-975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17049443#comment-17049443
]
Nick Couchman commented on GUACAMOLE-975:
-
{quote}
plus developers would have an answer, customers have only their opinions based
on use
{quote}
There are plenty of developers (like me) who respond on the user mailing list.
It isn't a user (customer) only mailing list, and it's the place to ask your
question.
> How many concurrent active sessions can Guacamole handle?
> -
>
> Key: GUACAMOLE-975
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-975
> Project: Guacamole
> Issue Type: Task
>Reporter: Stewart Alexander
>Priority: Blocker
>
> Where is the information on how many concurrent active sessions can Apache
> Guacamole handle before resource exhaustion?
>
> What are the limiting factors to how many users can actively create unique
> sessions / connections to hosts via Apache?
>
> This is blocking us as we need to understand the limitations and how we can
> avoid them as we potentially have several thousand people who would like to
> use this at once to log on to unique computers in our environment.
>
> Please email us any information on this at:
> stewart.alexan...@alamancecc.edu
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-978) Using the Docker images corresponding to Apache Guacamole 1.1.0, a Windows session is closed after approximately 2 to 3 minutes after starting an RDP session for a “
[ https://issues.apache.org/jira/browse/GUACAMOLE-978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17049482#comment-17049482 ] Nick Couchman commented on GUACAMOLE-978: - Please provide debug logs from guacd. > Using the Docker images corresponding to Apache Guacamole 1.1.0, a Windows > session is closed after approximately 2 to 3 minutes after starting an RDP > session for a “remoteapp” to a Windows Server 2016 server. > - > > Key: GUACAMOLE-978 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-978 > Project: Guacamole > Issue Type: Bug > Components: guacamole >Affects Versions: 1.1.0 >Reporter: Francisco Alejandro Diaz Damian >Priority: Minor > > Using the Docker images corresponding to Apache Guacamole 1.1.0, a Windows > session is closed after approximately 2 to 3 minutes after starting an RDP > session for a “remoteapp” to a Windows Server 2016 server. > This problem does not occur when you start a remote desktop RDP session with > Windows Server 2016. > The operating system of the Docker host is a Red Hat Enterprise Linux 7.5 > (Maipo). > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-975) How many concurrent active sessions can Guacamole handle?
[
https://issues.apache.org/jira/browse/GUACAMOLE-975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17049439#comment-17049439
]
Nick Couchman commented on GUACAMOLE-975:
-
Instructions are on the page that I sent. You need to send an e-mail to:
user-subscr...@guacamole.apache.org
And you'll receive an confirmation e-mail back. If you don't receive the
confirmation, check your junk folder and/or SPAM filter to make sure it isn't
getting filtered out. If that doesn't work you can use the Nabble integration:
http://apache-guacamole-incubating-users.2363388.n4.nabble.com/
and post your question, there.
{quote}
No response to requesting access to the user list, this is blocking us
{quote}
I appreciate that; however, it still is unlikely a bug or issue within the
application, which is what JIRA is for tracking, and JIRA is not to provide
generic support. You need to use the mailing list/forum for that.
> How many concurrent active sessions can Guacamole handle?
> -
>
> Key: GUACAMOLE-975
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-975
> Project: Guacamole
> Issue Type: Task
>Reporter: Stewart Alexander
>Priority: Blocker
>
> Where is the information on how many concurrent active sessions can Apache
> Guacamole handle before resource exhaustion?
>
> What are the limiting factors to how many users can actively create unique
> sessions / connections to hosts via Apache?
>
> This is blocking us as we need to understand the limitations and how we can
> avoid them as we potentially have several thousand people who would like to
> use this at once to log on to unique computers in our environment.
>
> Please email us any information on this at:
> stewart.alexan...@alamancecc.edu
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-978) Using the Docker images corresponding to Apache Guacamole 1.1.0, a Windows session is closed after approximately 2 to 3 minutes after starting an RDP session for a “re
[ https://issues.apache.org/jira/browse/GUACAMOLE-978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-978: Priority: Minor (was: Major) > Using the Docker images corresponding to Apache Guacamole 1.1.0, a Windows > session is closed after approximately 2 to 3 minutes after starting an RDP > session for a “remoteapp” to a Windows Server 2016 server. > - > > Key: GUACAMOLE-978 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-978 > Project: Guacamole > Issue Type: Bug > Components: guacamole >Affects Versions: 1.1.0 >Reporter: Francisco Alejandro Diaz Damian >Priority: Minor > > Using the Docker images corresponding to Apache Guacamole 1.1.0, a Windows > session is closed after approximately 2 to 3 minutes after starting an RDP > session for a “remoteapp” to a Windows Server 2016 server. > This problem does not occur when you start a remote desktop RDP session with > Windows Server 2016. > The operating system of the Docker host is a Red Hat Enterprise Linux 7.5 > (Maipo). > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-980) used tomcat-jre8 Docker-Image seems to be deprecated
[ https://issues.apache.org/jira/browse/GUACAMOLE-980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-980: Component/s: (was: guacamole-client) guacamole-docker > used tomcat-jre8 Docker-Image seems to be deprecated > > > Key: GUACAMOLE-980 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-980 > Project: Guacamole > Issue Type: Improvement > Components: guacamole-docker > Environment: Docker >Reporter: Patrik Heinz >Priority: Minor > Labels: build, security > > I couldn't find any news to that topic, but it seems like all jre8 tomcat > Docker-Images on dockerhub are no longer maintained. The latest build is 10 > months old and contains 8.5.41 which is affected by Ghostcat bug. > old jre8 images: https://hub.docker.com/_/tomcat?tab=tags=1=jre8 > ARG TOMCAT_JRE=jre8 could be changed to jdk8 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-980) used tomcat-jre8 Docker-Image seems to be deprecated
[ https://issues.apache.org/jira/browse/GUACAMOLE-980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-980: Affects Version/s: (was: 1.3.0) (was: 1.2.0) > used tomcat-jre8 Docker-Image seems to be deprecated > > > Key: GUACAMOLE-980 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-980 > Project: Guacamole > Issue Type: Improvement > Components: guacamole-client > Environment: Docker >Reporter: Patrik Heinz >Priority: Minor > Labels: build, security > > I couldn't find any news to that topic, but it seems like all jre8 tomcat > Docker-Images on dockerhub are no longer maintained. The latest build is 10 > months old and contains 8.5.41 which is affected by Ghostcat bug. > old jre8 images: https://hub.docker.com/_/tomcat?tab=tags=1=jre8 > ARG TOMCAT_JRE=jre8 could be changed to jdk8 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-980) used tomcat-jre8 Docker-Image seems to be deprecated
[ https://issues.apache.org/jira/browse/GUACAMOLE-980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-980: Labels: (was: build security) > used tomcat-jre8 Docker-Image seems to be deprecated > > > Key: GUACAMOLE-980 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-980 > Project: Guacamole > Issue Type: Improvement > Components: guacamole-docker > Environment: Docker >Reporter: Patrik Heinz >Priority: Minor > > I couldn't find any news to that topic, but it seems like all jre8 tomcat > Docker-Images on dockerhub are no longer maintained. The latest build is 10 > months old and contains 8.5.41 which is affected by Ghostcat bug. > old jre8 images: https://hub.docker.com/_/tomcat?tab=tags=1=jre8 > ARG TOMCAT_JRE=jre8 could be changed to jdk8 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GUACAMOLE-708) Allow JDBC Users to be Created Automatically
[ https://issues.apache.org/jira/browse/GUACAMOLE-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman reassigned GUACAMOLE-708: --- Assignee: Mike Jumper (was: Nick Couchman) > Allow JDBC Users to be Created Automatically > > > Key: GUACAMOLE-708 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-708 > Project: Guacamole > Issue Type: New Feature > Components: guacamole-auth-jdbc >Reporter: Nick Couchman >Assignee: Mike Jumper >Priority: Minor > Fix For: 1.2.0 > > > A feature common to other applications that store data in one place and can > authenticate from other sources is to enable automatic creation of user > accounts within the database assuming the user is successfully authenticated > elsewhere. > I propose doing something similar with the Guacamole JDBC extension, or, > depending on how the implementation works out, with the other extensions - a > property that, disabled by default, could be enabled that would allow users > authenticated successfully through other extensions to be automatically > created within the JDBC extension. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-708) Allow JDBC Users to be Created Automatically
[ https://issues.apache.org/jira/browse/GUACAMOLE-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053444#comment-17053444 ] Nick Couchman commented on GUACAMOLE-708: - Okay, let's just keep it, here, then. > Allow JDBC Users to be Created Automatically > > > Key: GUACAMOLE-708 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-708 > Project: Guacamole > Issue Type: New Feature > Components: guacamole-auth-jdbc >Reporter: Nick Couchman >Assignee: Nick Couchman >Priority: Minor > Fix For: 1.2.0 > > > A feature common to other applications that store data in one place and can > authenticate from other sources is to enable automatic creation of user > accounts within the database assuming the user is successfully authenticated > elsewhere. > I propose doing something similar with the Guacamole JDBC extension, or, > depending on how the implementation works out, with the other extensions - a > property that, disabled by default, could be enabled that would allow users > authenticated successfully through other extensions to be automatically > created within the JDBC extension. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GUACAMOLE-966) Bump version numbers to 1.2.0
[ https://issues.apache.org/jira/browse/GUACAMOLE-966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman resolved GUACAMOLE-966. - Resolution: Done I believe everything for this has been completed, at least to this point. Slight chance that a couple other components will have to be changed later on, but we'll cross that bridge when we get to it. > Bump version numbers to 1.2.0 > - > > Key: GUACAMOLE-966 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-966 > Project: Guacamole > Issue Type: Task >Reporter: Mike Jumper >Assignee: Nick Couchman >Priority: Major > Fix For: 1.2.0 > > > As [the scope of 1.2.0 has been > finalized|https://lists.apache.org/thread.html/r836c268d545c11512a8647087a28639b71853c849d810479de031d38%40%3Cdev.guacamole.apache.org%3E], > and the release branches have been created, the version numbers of all > modified components need to be bumped to 1.2.0. > I don't believe any changes are planned for libguac in this release, but in > case it's relevant: > In the case of libguac, the SO version (libtool version info) must be > incremented only according to [strict > guidelines|https://www.gnu.org/software/libtool/manual/html_node/Updating-version-info.html]). > It is independent of the project version. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-625) Add Spanish Latam keyboard support
[ https://issues.apache.org/jira/browse/GUACAMOLE-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-625: Affects Version/s: (was: 0.9.9) > Add Spanish Latam keyboard support > -- > > Key: GUACAMOLE-625 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-625 > Project: Guacamole > Issue Type: Improvement > Components: RDP >Reporter: Ciro Iriarte >Priority: Minor > > Currently for RDP setup options, it's not possible to define the keyboard > layout as Spanish Latam -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GUACAMOLE-625) Add Spanish Latam keyboard support
[ https://issues.apache.org/jira/browse/GUACAMOLE-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman resolved GUACAMOLE-625. - Resolution: Implemented > Add Spanish Latam keyboard support > -- > > Key: GUACAMOLE-625 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-625 > Project: Guacamole > Issue Type: Improvement > Components: RDP >Reporter: Ciro Iriarte >Priority: Minor > Fix For: 1.2.0 > > > Currently for RDP setup options, it's not possible to define the keyboard > layout as Spanish Latam -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-940) guacd docker | screen recorder - inserting path that mount by volume in docker break the connection
[ https://issues.apache.org/jira/browse/GUACAMOLE-940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-940: Fix Version/s: (was: 1.1.0) > guacd docker | screen recorder - inserting path that mount by volume in > docker break the connection > --- > > Key: GUACAMOLE-940 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-940 > Project: Guacamole > Issue Type: Bug > Components: guacd-docker >Affects Versions: 1.1.0 >Reporter: Yossi Kishik >Priority: Minor > Labels: docker > Attachments: image-2020-01-26-22-52-05-170.png > > > Hi, > guacd version: 1.1.0-RC1 > > i mounted /tmp directory in guacd to folder in the host. > once i choose in guacamole in screen recorder config that the path is "/tmp" > it's break the connection and guacamole report that "the connection to guacd > is timed out" > if i choose another folder that not mount- it works perfectly. > can you please take a look? > BTW- it reproduced also on 1.0.0 > > docker run: > docker run -ti -v /mnt/lol/guacamole_session_logs/:/tmp/ --name guacd -d > guacamole/guacd:1.1.0-RC1 > > guacamole config: > !image-2020-01-26-22-52-05-170.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-940) guacd docker | screen recorder - inserting path that mount by volume in docker break the connection
[ https://issues.apache.org/jira/browse/GUACAMOLE-940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-940: Priority: Minor (was: Major) > guacd docker | screen recorder - inserting path that mount by volume in > docker break the connection > --- > > Key: GUACAMOLE-940 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-940 > Project: Guacamole > Issue Type: Bug > Components: guacd-docker >Affects Versions: 1.1.0 >Reporter: Yossi Kishik >Priority: Minor > Labels: docker > Fix For: 1.1.0 > > Attachments: image-2020-01-26-22-52-05-170.png > > > Hi, > guacd version: 1.1.0-RC1 > > i mounted /tmp directory in guacd to folder in the host. > once i choose in guacamole in screen recorder config that the path is "/tmp" > it's break the connection and guacamole report that "the connection to guacd > is timed out" > if i choose another folder that not mount- it works perfectly. > can you please take a look? > BTW- it reproduced also on 1.0.0 > > docker run: > docker run -ti -v /mnt/lol/guacamole_session_logs/:/tmp/ --name guacd -d > guacamole/guacd:1.1.0-RC1 > > guacamole config: > !image-2020-01-26-22-52-05-170.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-941) Automate Adding Admin to Bastion stepping stone
[ https://issues.apache.org/jira/browse/GUACAMOLE-941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-941: Priority: Trivial (was: Major) > Automate Adding Admin to Bastion stepping stone > --- > > Key: GUACAMOLE-941 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-941 > Project: Guacamole > Issue Type: Wish > Components: guacamole >Affects Versions: 1.0.0 >Reporter: Hardik Shah >Priority: Trivial > > Hello All, > I am trying to automate ID creation on Bastion stepping stone / Guacamole > using Native API. Unfortunately not succeeded. > Can you guide me to which API to use and how to automate ID creation on > Bastion stepping stone, Create profile and adding server to use profile. > > Thanks, > Hardik Shah -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-940) guacd docker | screen recorder - inserting path that mount by volume in docker break the connection
[ https://issues.apache.org/jira/browse/GUACAMOLE-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023937#comment-17023937 ] Nick Couchman commented on GUACAMOLE-940: - [~yossikishik]: I understand that you're reporting what might appear to be a regression in the Guacamole behavior for screen recording in the upcoming 1.1.0 release. Thanks for testing this release and reporting an issue. In the future it might be better to start this conversation on the mailing list so that we can confirm the presence of an issue before opening a JIRA issue for it. That said, in order to track this down any further, we'll need to get you to enable verbose logging for guacd (which should be doable via the proper Docker variable, and paste the log output so that we can see why guacd is failing. > guacd docker | screen recorder - inserting path that mount by volume in > docker break the connection > --- > > Key: GUACAMOLE-940 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-940 > Project: Guacamole > Issue Type: Bug > Components: guacd-docker >Affects Versions: 1.1.0 >Reporter: Yossi Kishik >Priority: Minor > Labels: docker > Attachments: image-2020-01-26-22-52-05-170.png > > > Hi, > guacd version: 1.1.0-RC1 > > i mounted /tmp directory in guacd to folder in the host. > once i choose in guacamole in screen recorder config that the path is "/tmp" > it's break the connection and guacamole report that "the connection to guacd > is timed out" > if i choose another folder that not mount- it works perfectly. > can you please take a look? > BTW- it reproduced also on 1.0.0 > > docker run: > docker run -ti -v /mnt/lol/guacamole_session_logs/:/tmp/ --name guacd -d > guacamole/guacd:1.1.0-RC1 > > guacamole config: > !image-2020-01-26-22-52-05-170.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-912) Fix Guacamole Docker Documentation to indiciate image does not support LDAP Docker Links
[
https://issues.apache.org/jira/browse/GUACAMOLE-912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman updated GUACAMOLE-912:
Fix Version/s: (was: 1.0.0)
> Fix Guacamole Docker Documentation to indiciate image does not support LDAP
> Docker Links
>
>
> Key: GUACAMOLE-912
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-912
> Project: Guacamole
> Issue Type: Bug
> Components: Documentation
>Affects Versions: 1.0.0
>Reporter: Joe Adams
>Priority: Trivial
>
> Fix Guacamole Docker Documentation to indiciate image does not support Docker
> Links.
>
> The documentation which is published at
> [https://guacamole.apache.org/doc/gug/guacamole-docker.html#guacamole-docker-ldap]
> states
> {quote}To use Guacamole with the LDAP authentication backend, you will need
> network access to an LDAP directory. Unlike MySQL and PostgreSQL, the
> Guacamole Docker image does support Docker links for LDAP; the connection
> information must be specified using environment variables:{quote}
> This should be (without the added emphasis)
> {quote}To use Guacamole with the LDAP authentication backend, you will need
> network access to an LDAP directory. Unlike MySQL and PostgreSQL, the
> Guacamole Docker image does *not* support Docker links for LDAP; the
> connection information must be specified using environment variables:{quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-941) Automate Adding Admin to Bastion stepping stone
[ https://issues.apache.org/jira/browse/GUACAMOLE-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17024084#comment-17024084 ] Nick Couchman commented on GUACAMOLE-941: - [~hardik03]: It looks like, rather than reporting an issue with the project, which is what JIRA is intended for, you are trying to get help with using a component of the system. JIRA is not intended to be a general help forum, but a place to report issues and request features. Please post your question to the mailing list so that the community can help you out. It's a little unclear what you're trying to do, so when you do post to the mailing list, try to be a little more detailed and specific about what your end-goal is, what you've tried, what errors you've received, etc. > Automate Adding Admin to Bastion stepping stone > --- > > Key: GUACAMOLE-941 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-941 > Project: Guacamole > Issue Type: Wish > Components: guacamole >Affects Versions: 1.0.0 >Reporter: Hardik Shah >Priority: Trivial > > Hello All, > I am trying to automate ID creation on Bastion stepping stone / Guacamole > using Native API. Unfortunately not succeeded. > Can you guide me to which API to use and how to automate ID creation on > Bastion stepping stone, Create profile and adding server to use profile. > > Thanks, > Hardik Shah -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-919) An I/O error occurred while sending to the backend
[ https://issues.apache.org/jira/browse/GUACAMOLE-919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-919: Priority: Minor (was: Major) > An I/O error occurred while sending to the backend > -- > > Key: GUACAMOLE-919 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-919 > Project: Guacamole > Issue Type: Bug > Components: guacamole-auth-jdbc-postgresql >Affects Versions: 1.0.0 >Reporter: Mechanix >Assignee: Nick Couchman >Priority: Minor > Attachments: image-2020-01-27-15-19-26-634.png > > > Hi, > we use guacamole with postgresql and openid extension. Guacamole and guacd is > deployed inside a k8s cluster. > For some reason, the authentication doesn't succeed sporadically; there is > only a blank page and this error message in the guacamole log: > *[pool-1-thread-1] WARN o.a.i.d.pooled.PooledDataSource - Execution of ping > query 'SELECT 1' failed: An I/O error occurred while sending to the backend.* > I suspect there is a weird timeout happening between guacamole and postgresql > but could figure out why. > Any hints are much appreciated. Thanks > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GUACAMOLE-919) An I/O error occurred while sending to the backend
[ https://issues.apache.org/jira/browse/GUACAMOLE-919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman reassigned GUACAMOLE-919: --- Assignee: Nick Couchman > An I/O error occurred while sending to the backend > -- > > Key: GUACAMOLE-919 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-919 > Project: Guacamole > Issue Type: Bug > Components: guacamole-auth-jdbc-postgresql >Affects Versions: 1.0.0 >Reporter: Mechanix >Assignee: Nick Couchman >Priority: Major > Attachments: image-2020-01-27-15-19-26-634.png > > > Hi, > we use guacamole with postgresql and openid extension. Guacamole and guacd is > deployed inside a k8s cluster. > For some reason, the authentication doesn't succeed sporadically; there is > only a blank page and this error message in the guacamole log: > *[pool-1-thread-1] WARN o.a.i.d.pooled.PooledDataSource - Execution of ping > query 'SELECT 1' failed: An I/O error occurred while sending to the backend.* > I suspect there is a weird timeout happening between guacamole and postgresql > but could figure out why. > Any hints are much appreciated. Thanks > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-919) An I/O error occurred while sending to the backend
[ https://issues.apache.org/jira/browse/GUACAMOLE-919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17024123#comment-17024123 ] Nick Couchman commented on GUACAMOLE-919: - [~mechanix] [~DouglasHeriot]: Hey, guys, While I do not doubt that you're running into problems, I do not believe the issues you are seeing are a bug in the Guacamole code. I think it's much more likely that they occur somewhere in the JDBC code, and are due to timeout and/or latency issues within the JDBC connections. This seems particularly likely based on [~DouglasHeriot]'s information about the DB being hosted over a DX link between an on-premise install of Guacamole Client (Tomcat) and a cloud-hosted database. That said, it seems like the best course of action would be to re-classify this as a feature request for the ability to configure the JDBC timeout. It looks like the MyBastis code (what handles much of Guacamole Client's JDBC support) allows you to configure timeouts in various ways, and this might help situations where the database is slower to respond than is normally expected. I'll try to see if I can reproduce the issues you are seeing, and put together a PR that you can try out that allows for configuring one or more timeout values. > An I/O error occurred while sending to the backend > -- > > Key: GUACAMOLE-919 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-919 > Project: Guacamole > Issue Type: Bug > Components: guacamole-auth-jdbc-postgresql >Affects Versions: 1.0.0 >Reporter: Mechanix >Priority: Major > Attachments: image-2020-01-27-15-19-26-634.png > > > Hi, > we use guacamole with postgresql and openid extension. Guacamole and guacd is > deployed inside a k8s cluster. > For some reason, the authentication doesn't succeed sporadically; there is > only a blank page and this error message in the guacamole log: > *[pool-1-thread-1] WARN o.a.i.d.pooled.PooledDataSource - Execution of ping > query 'SELECT 1' failed: An I/O error occurred while sending to the backend.* > I suspect there is a weird timeout happening between guacamole and postgresql > but could figure out why. > Any hints are much appreciated. Thanks > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-890) Guacamole/Guacd Docker Process Privilege Drop
[
https://issues.apache.org/jira/browse/GUACAMOLE-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17025946#comment-17025946
]
Nick Couchman commented on GUACAMOLE-890:
-
{quote}
Server processes are usually ment to be run as non-root user, so I think this
report is rather important.
Perhaps it's a minor thing which prevents the guacamole container from starting
using a non-root user ?
In its startup script perhaps ? Some permission issue ?
{quote}
Yes, I understand and agree, and I would not suggest that anyone run something
like Guacamole as a root user. I do not use Docker, but I routinely run as
non-root users in my environment.
My question to you is for you to provide us with more detail on what you're
seeing that prevents you from running as a non-root user? Please help us
understand why this doesn't work, as I believe it should work perfectly fine.
{quote}
If so tiny / non-impacting thing, perhaps we could think about it as a
security improvement for 1.1.0 ?
{quote}
No, the only issues that will be included in 1.1.0 from this point are those
that are considered regressions in functionality. Because we haven't even
determined that there is an issue here, to begin with, let alone what needs to
be changed or the level of effort to change it, we will not alter the 1.1.0
release. The only way this would make it into the 1.1.0 release at this point
is if we determine very quickly that this is a regression due to another change
in 1.1.0. And, even then, it's getting a little late.
> Guacamole/Guacd Docker Process Privilege Drop
> -
>
> Key: GUACAMOLE-890
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-890
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-docker
>Reporter: Anthony Boccia
>Priority: Minor
> Labels: docker, security
>
> Hello,
> I noticed after deploying Guacamole in docker that the processes all run as
> the root user. Are there any plans to add support for specifying a user for
> the processes to drop privs to and run as instead of root? I am currently
> doing this rebuilding the containers for guacamole and guacd adding in my own
> user and using docker compose to exec all processes triggered within the
> container as that user. I feel like the option to specify this should be done
> upstream.
> Thank You
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-890) Guacamole/Guacd Docker Process Privilege Drop
[
https://issues.apache.org/jira/browse/GUACAMOLE-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17025925#comment-17025925
]
Nick Couchman commented on GUACAMOLE-890:
-
{quote}
Unfortunately, this does not work for the guacamole container... We then have
one of the 2 components running as root, which is not really a good thing...
{quote}
Why not?
{quote}
Would be nice to have this fixed for the 1.1.0 release.
{quote}
This will not be fixed or changed in the 1.1.0 release - the release is almost
completed and is in final RC stages, now. *If* any changes need to be made
they will be in a future release.
> Guacamole/Guacd Docker Process Privilege Drop
> -
>
> Key: GUACAMOLE-890
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-890
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-docker
>Reporter: Anthony Boccia
>Priority: Minor
> Labels: docker, security
>
> Hello,
> I noticed after deploying Guacamole in docker that the processes all run as
> the root user. Are there any plans to add support for specifying a user for
> the processes to drop privs to and run as instead of root? I am currently
> doing this rebuilding the containers for guacamole and guacd adding in my own
> user and using docker compose to exec all processes triggered within the
> container as that user. I feel like the option to specify this should be done
> upstream.
> Thank You
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-919) An I/O error occurred while sending to the backend
[ https://issues.apache.org/jira/browse/GUACAMOLE-919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17026455#comment-17026455 ] Nick Couchman commented on GUACAMOLE-919: - [~DouglasHeriot]: For you, yes, this is a show-stopper. The reason it has been classified as minor is that we only have two people reporting it at this time, and we don't really even know exactly what's causing it. We've identified a couple of possibilities for what might fix it, but, as far as Guacamole is concerned, it isn't a bug, it's an enhancement to overcome what we suspect is happening in a couple of specific situations related to timeout/latency between client and DB. It isn't being widely reported throughout the community on either 1.0.0 or 1.1.0, it seems to be pretty limited, so that's my rationale for having classified it as minor. As far as it being a regression - I'm skeptical of that. It is very interesting to me that it works for you in 1.0.0 and not in 1.1.0, but if you look at the original reported issue, it is against version 1.0.0, not 1.1.0-RC1. I don't know exactly what to make of that, but the fact that it is being reported by you and the original reporter in two different versions makes me think that it isn't a regression between those two versions, it's something else. Is your 1.1.0-RC1 deployment running on exactly the same systems as 1.0.0, and using exactly the same Postgres server, so that the only difference between the two is the Guacamole version? And you're saying that, if you go back to 1.0.0 right now (in the environment where 1.1.0-RC1 does ont work), that everything works as expected? > An I/O error occurred while sending to the backend > -- > > Key: GUACAMOLE-919 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-919 > Project: Guacamole > Issue Type: Bug > Components: guacamole-auth-jdbc-postgresql >Affects Versions: 1.0.0 >Reporter: Mechanix >Assignee: Nick Couchman >Priority: Minor > Attachments: image-2020-01-27-15-19-26-634.png > > > Hi, > we use guacamole with postgresql and openid extension. Guacamole and guacd is > deployed inside a k8s cluster. > For some reason, the authentication doesn't succeed sporadically; there is > only a blank page and this error message in the guacamole log: > *[pool-1-thread-1] WARN o.a.i.d.pooled.PooledDataSource - Execution of ping > query 'SELECT 1' failed: An I/O error occurred while sending to the backend.* > I suspect there is a weird timeout happening between guacamole and postgresql > but could figure out why. > Any hints are much appreciated. Thanks > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-852) Support MariaDB JDBC Driver
[ https://issues.apache.org/jira/browse/GUACAMOLE-852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-852: Fix Version/s: 1.2.0 > Support MariaDB JDBC Driver > --- > > Key: GUACAMOLE-852 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-852 > Project: Guacamole > Issue Type: Improvement > Components: guacamole-auth-jdbc-mysql >Reporter: Nick Couchman >Assignee: Nick Couchman >Priority: Minor > Fix For: 1.2.0 > > > The MariaDB JDBC driver implements a different class than the MySQL driver, > so some changes will need to be made to the JDBC module to support that > version of the driver. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-852) Support MariaDB JDBC Driver
[ https://issues.apache.org/jira/browse/GUACAMOLE-852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17028560#comment-17028560 ] Nick Couchman commented on GUACAMOLE-852: - Code merged, just need to update documentation. > Support MariaDB JDBC Driver > --- > > Key: GUACAMOLE-852 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-852 > Project: Guacamole > Issue Type: Improvement > Components: guacamole-auth-jdbc-mysql >Reporter: Nick Couchman >Assignee: Nick Couchman >Priority: Minor > Fix For: 1.2.0 > > > The MariaDB JDBC driver implements a different class than the MySQL driver, > so some changes will need to be made to the JDBC module to support that > version of the driver. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-944) LDAP broken in 1.1.0
[ https://issues.apache.org/jira/browse/GUACAMOLE-944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17029430#comment-17029430 ] Nick Couchman commented on GUACAMOLE-944: - We're going to need more logs than that to figure out what's going on, here - you'll likely need to put the web app into debug mode. Also please specify your environment - beyond Kubernetes, what JRE/JDK, Tomcat, etc., are you deploying into? > LDAP broken in 1.1.0 > > > Key: GUACAMOLE-944 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-944 > Project: Guacamole > Issue Type: Bug > Components: guacamole-auth-ldap >Affects Versions: 1.1.0 > Environment: Kubernetes 1.16.4 >Reporter: Ross >Priority: Major > > On upgrading our Guacamole container from 1.0.0 to 1.1.0, it fails to > authenticate. Error message in logs is: > 03-Feb-2020 13:37:15.136 INFO [main] > org.apache.catalina.startup.Catalina.start Server startup in 3675 > ms13:38:12.579 [http-nio-8080-exec-9] WARN > o.a.g.e.AuthenticationProviderFacade - The "ldap" authentication provider has > encountered an internal error which will halt the authentication process. If > this is unexpected or you are the developer of this authentication provider, > you may wish to enable debug-level logging. If this is expected and you wish > to ignore such failures in the future, please set "skip-if-unavailable: ldap" > within your guacamole.properties.13:38:12.579 [http-nio-8080-exec-9] WARN > o.a.g.r.auth.AuthenticationService - Authentication attempt from > [1.20.211.22, 10.42.4.0] for user "rossg" failed. > Workaround is to switch back to 1.0.0. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-865) Missing libfreerdp-dev for Server Docker Build
[ https://issues.apache.org/jira/browse/GUACAMOLE-865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17028562#comment-17028562 ] Nick Couchman commented on GUACAMOLE-865: - Could someone retry this with the official 1.1.0 release and see if it's still an issue? Since GUACAMOLE-249 is included and upgrades support to FreeRDP 2.0.0, I'm hoping that takes care of this? > Missing libfreerdp-dev for Server Docker Build > -- > > Key: GUACAMOLE-865 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-865 > Project: Guacamole > Issue Type: Bug > Components: guacamole-server >Affects Versions: 1.1.0 >Reporter: Matt Grochowalski >Priority: Minor > > The guacamole-server Docker image fails to build due to the latest stable > version (Buster) no longer including FreeRDP 1.1 > This would be fixed by GUACAMOLE-249, but if that's not ready for the next > Guacamole release the Dockerfile should likely be changed to reference > "stretch" explicitly instead of "stable". Or perhaps one of the Ubuntu > releases. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-939) Read Docker image environment variables from guacamole.properties
[
https://issues.apache.org/jira/browse/GUACAMOLE-939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17028581#comment-17028581
]
Nick Couchman commented on GUACAMOLE-939:
-
{quote}
Yes, docker-compose is possible, but if you put LDAP and Postgres together, I
think guacamole.properties is much easier to handle and better documented.
{quote}
But, I think one of the points Mike is making is that what you're suggesting
results in a very odd behavior. If we read Docker variables from a
guacamole.properties file, essentially what we're doing is guacamole.properties
-> Docker variables -> guacamole.properties - we end up re-writing
guacamole.properties with values provided already in...guacamole.properties.
So, if you just map the guacamole.properties file location (GUACAMOLE_HOME)
through to the container, as Mike suggested, you avoid the need for
reading/translating/rewriting. Yes, you still have to specify some other
properties, like GUACD_HOSTNAME, but its pretty minimal - everything else can
be specified directly in guacamole.properties.
> Read Docker image environment variables from guacamole.properties
> -
>
> Key: GUACAMOLE-939
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-939
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-docker
>Affects Versions: 1.0.0
>Reporter: Thomas Eggers
>Priority: Minor
> Attachments: start.sh
>
>
> Hi,
> I'm not a Software developer,
> but I have linux script and docker experience.
> I startet to enhance the start.sh file in the docker image.
> This new version is pre read required variable from guacamole.properties to
> configure the tomcat web interface. This make it much easier to start the
> docker container without so many options.
> Other things that I like to do is:
> - import certificate for ldaps connections
> - docker container health status
> - and other small things
> Thomas
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-950) segfault in guacd
[ https://issues.apache.org/jira/browse/GUACAMOLE-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17032781#comment-17032781 ] Nick Couchman commented on GUACAMOLE-950: - Yeah, we'll definitely want to see the stack trace. Basically you either need to start gdb, first, and then run guacd from there, or attach to an existing guacd process. You'll also want to "set follow-fork-mode child" so that gdb debugs the child guacd process and not the parent guacd process. After it crashes run "bt" to get the back trace, and send that output. > segfault in guacd > -- > > Key: GUACAMOLE-950 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-950 > Project: Guacamole > Issue Type: Bug > Components: guacamole-server >Affects Versions: 1.1.0 > Environment: Guacamole 1.1.0 under Tomcat8 on Ubuntu 18.04, running > as virtual machine >Reporter: Toby >Priority: Minor > Attachments: trace_connected.txt, trace_segfault.txt > > > Upgraded from 1.0.0 on Ubuntu 16.04 to 1.1.0 on Ubuntu 18.04. Moved from > Tomcat7 to Tomcat8. Config is largely unchanged. > Two Windows 10 Enterprise destinations and a third is 2012R2. One of the two > Windows 10 will cause guacd to segfault on connection. 2012R2 works fine. I > see a mouse pointer in the upper left very briefly and then I get > home/reconnect/logout. I have pared the config down to just domain, > username, password, NLA security, ignore-cert directives for all three > destinations. > Uploaded syslog traces, one of a normal connect to the other windows 10 > device, one as the segmentation fault I get when connecting to the other. > Have also tried rebuilding without webp and websockets to no effect. > I'm happy to build one for gdb and get a core, but I'll need a little help > doing that. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GUACAMOLE-625) Add Spanish Latam keyboard support
[ https://issues.apache.org/jira/browse/GUACAMOLE-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman resolved GUACAMOLE-625. - Resolution: Implemented Fixed whitespace issue. > Add Spanish Latam keyboard support > -- > > Key: GUACAMOLE-625 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-625 > Project: Guacamole > Issue Type: Improvement > Components: RDP >Reporter: Ciro Iriarte >Assignee: Nick Couchman >Priority: Minor > Fix For: 1.2.0 > > > Currently for RDP setup options, it's not possible to define the keyboard > layout as Spanish Latam -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-945) Migrating away from libssh2 dependency?
[ https://issues.apache.org/jira/browse/GUACAMOLE-945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-945: Priority: Minor (was: Major) > Migrating away from libssh2 dependency? > --- > > Key: GUACAMOLE-945 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-945 > Project: Guacamole > Issue Type: Improvement > Components: guacd >Affects Versions: 1.1.0 >Reporter: Joonas Tuomisto >Priority: Minor > > It appears Red Hat / CentOS stopped shipping libssh2 in version 8 which makes > building Guacamole a hassle on those platforms - of course, this has nothing > to do with Guacamole as such, but would it make sense to consider other > libraries? > I didn't look into this in depth so not sure if there's major benefits > feature-wise and how much work this would entail... > > libssh seems to have undergone an external security audit recently so > security could be one consideration. > > re: CentOS, this is discussed here: https://bugs.centos.org/view.php?id=16492 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-945) Migrating away from libssh2 dependency?
[ https://issues.apache.org/jira/browse/GUACAMOLE-945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-945: Affects Version/s: (was: 1.1.0) > Migrating away from libssh2 dependency? > --- > > Key: GUACAMOLE-945 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-945 > Project: Guacamole > Issue Type: Improvement > Components: guacd >Reporter: Joonas Tuomisto >Priority: Minor > > It appears Red Hat / CentOS stopped shipping libssh2 in version 8 which makes > building Guacamole a hassle on those platforms - of course, this has nothing > to do with Guacamole as such, but would it make sense to consider other > libraries? > I didn't look into this in depth so not sure if there's major benefits > feature-wise and how much work this would entail... > > libssh seems to have undergone an external security audit recently so > security could be one consideration. > > re: CentOS, this is discussed here: https://bugs.centos.org/view.php?id=16492 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-945) Migrating away from libssh2 dependency?
[ https://issues.apache.org/jira/browse/GUACAMOLE-945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17029804#comment-17029804 ] Nick Couchman commented on GUACAMOLE-945: - ...and, looks like RHEL8 ships with libssh (vs. libssh2), so not sure how much work it would be to support both of those options. > Migrating away from libssh2 dependency? > --- > > Key: GUACAMOLE-945 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-945 > Project: Guacamole > Issue Type: Improvement > Components: guacd >Reporter: Joonas Tuomisto >Priority: Minor > > It appears Red Hat / CentOS stopped shipping libssh2 in version 8 which makes > building Guacamole a hassle on those platforms - of course, this has nothing > to do with Guacamole as such, but would it make sense to consider other > libraries? > I didn't look into this in depth so not sure if there's major benefits > feature-wise and how much work this would entail... > > libssh seems to have undergone an external security audit recently so > security could be one consideration. > > re: CentOS, this is discussed here: https://bugs.centos.org/view.php?id=16492 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-945) Migrating away from libssh2 dependency?
[ https://issues.apache.org/jira/browse/GUACAMOLE-945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17029801#comment-17029801 ] Nick Couchman commented on GUACAMOLE-945: - Interesting, and a shame. The power of libssh2 is that it's very simple and straight-forward to use - it does a few things very well, and that's pretty much all we need. We could look at adding support for or migrating to the OpenSSH library - I'm guessing that's the most available and popular one - it's just going to take some work to make the switch, and I don't know if there are any licensing issues, although that tends to be less of an issue with guacd since we don't distribute binary code. Thanks for submitting this - definitely good to know for our roadmap. > Migrating away from libssh2 dependency? > --- > > Key: GUACAMOLE-945 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-945 > Project: Guacamole > Issue Type: Improvement > Components: guacd >Reporter: Joonas Tuomisto >Priority: Minor > > It appears Red Hat / CentOS stopped shipping libssh2 in version 8 which makes > building Guacamole a hassle on those platforms - of course, this has nothing > to do with Guacamole as such, but would it make sense to consider other > libraries? > I didn't look into this in depth so not sure if there's major benefits > feature-wise and how much work this would entail... > > libssh seems to have undergone an external security audit recently so > security could be one consideration. > > re: CentOS, this is discussed here: https://bugs.centos.org/view.php?id=16492 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GUACAMOLE-958) Race in guacd client termination
[
https://issues.apache.org/jira/browse/GUACAMOLE-958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman resolved GUACAMOLE-958.
-
Resolution: Fixed
> Race in guacd client termination
>
>
> Key: GUACAMOLE-958
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-958
> Project: Guacamole
> Issue Type: Bug
> Components: guacd
>Affects Versions: 1.1.0
>Reporter: Jonas Zeiger
>Priority: Minor
> Fix For: 1.2.0
>
>
> I observed delays when trying to shutdown guacd cleanly:
> {code:java}
> 2020-02-12 12:20:52.886 [some-app] [0c7bfb7f-c009-4685-8b83-a144aa0bb4f6]
> [140049387599616]: guacd[174]: DEBUG: Client terminated successfully.
> 2020-02-12 12:20:52.887 [some-app] [0c7bfb7f-c009-4685-8b83-a144aa0bb4f6]
> [140049387599616]: guacd[166]: ERROR: Error handling message from VNC
> server.
> 2020-02-12 12:20:52.887 [some-app] [0c7bfb7f-c009-4685-8b83-a144aa0bb4f6]
> [140049387599616]: guacd[166]: INFO:User
> "@e2dac0b0-5e01-4b3e-8898-14d2d351abee" disconnected (0 users remain)
> 2020-02-12 12:20:52.887 [some-app] [0c7bfb7f-c009-4685-8b83-a144aa0bb4f6]
> [140049387599616]: guacd[166]: INFO:Last user of connection
> "$902a4fea-c198-409f-a249-9a5dbaa4bdec" disconnected
> 2020-02-12 12:20:52.887 [some-app] [0c7bfb7f-c009-4685-8b83-a144aa0bb4f6]
> [140049387599616]: guacd[166]: DEBUG: Requesting termination of
> client...
> 2020-02-12 12:20:52.887 [some-app] [0c7bfb7f-c009-4685-8b83-a144aa0bb4f6]
> [140049387599616]: guacd[166]: INFO:Internal VNC client disconnected
> 2020-02-12 12:20:57.887 [some-app] [0c7bfb7f-c009-4685-8b83-a144aa0bb4f6]
> [140049387599616]: guacd[166]: WARNING: Client did not terminate in a
> timely manner. Forcibly terminating client and any child processes.
> {code}
> I suspect the client actually terminated properly (see log message "Internal
> VNC client disconnected").
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-958) Race in guacd client termination
[
https://issues.apache.org/jira/browse/GUACAMOLE-958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman updated GUACAMOLE-958:
Fix Version/s: 1.2.0
> Race in guacd client termination
>
>
> Key: GUACAMOLE-958
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-958
> Project: Guacamole
> Issue Type: Bug
> Components: guacd
>Affects Versions: 1.1.0
>Reporter: Jonas Zeiger
>Priority: Minor
> Fix For: 1.2.0
>
>
> I observed delays when trying to shutdown guacd cleanly:
> {code:java}
> 2020-02-12 12:20:52.886 [some-app] [0c7bfb7f-c009-4685-8b83-a144aa0bb4f6]
> [140049387599616]: guacd[174]: DEBUG: Client terminated successfully.
> 2020-02-12 12:20:52.887 [some-app] [0c7bfb7f-c009-4685-8b83-a144aa0bb4f6]
> [140049387599616]: guacd[166]: ERROR: Error handling message from VNC
> server.
> 2020-02-12 12:20:52.887 [some-app] [0c7bfb7f-c009-4685-8b83-a144aa0bb4f6]
> [140049387599616]: guacd[166]: INFO:User
> "@e2dac0b0-5e01-4b3e-8898-14d2d351abee" disconnected (0 users remain)
> 2020-02-12 12:20:52.887 [some-app] [0c7bfb7f-c009-4685-8b83-a144aa0bb4f6]
> [140049387599616]: guacd[166]: INFO:Last user of connection
> "$902a4fea-c198-409f-a249-9a5dbaa4bdec" disconnected
> 2020-02-12 12:20:52.887 [some-app] [0c7bfb7f-c009-4685-8b83-a144aa0bb4f6]
> [140049387599616]: guacd[166]: DEBUG: Requesting termination of
> client...
> 2020-02-12 12:20:52.887 [some-app] [0c7bfb7f-c009-4685-8b83-a144aa0bb4f6]
> [140049387599616]: guacd[166]: INFO:Internal VNC client disconnected
> 2020-02-12 12:20:57.887 [some-app] [0c7bfb7f-c009-4685-8b83-a144aa0bb4f6]
> [140049387599616]: guacd[166]: WARNING: Client did not terminate in a
> timely manner. Forcibly terminating client and any child processes.
> {code}
> I suspect the client actually terminated properly (see log message "Internal
> VNC client disconnected").
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GUACAMOLE-952) Preconnection Blob Support Broken
Nick Couchman created GUACAMOLE-952: --- Summary: Preconnection Blob Support Broken Key: GUACAMOLE-952 URL: https://issues.apache.org/jira/browse/GUACAMOLE-952 Project: Guacamole Issue Type: Bug Components: RDP Affects Versions: 1.1.0 Reporter: Nick Couchman After the switch to FreeRDP 2, support for setting the Preconnection Blob (to connect to Hyper-V, for example), appearst o be broken. Looks like FreeRDP 2.x code still supports it, but something about the detection on the Guacamole side seems to detect it as missing. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-926) Add connection form CSV
[ https://issues.apache.org/jira/browse/GUACAMOLE-926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-926: Priority: Trivial (was: Major) > Add connection form CSV > --- > > Key: GUACAMOLE-926 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-926 > Project: Guacamole > Issue Type: Wish > Components: guacamole >Affects Versions: 1.0.0 >Reporter: Dinoop >Priority: Trivial > > Is there any options to add all servers from a CSV file or so. Adding one by > one will take too much time. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-917) Key mapping for German keyboards: ~ does not work
[ https://issues.apache.org/jira/browse/GUACAMOLE-917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-917: Priority: Minor (was: Major) > Key mapping for German keyboards: ~ does not work > - > > Key: GUACAMOLE-917 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-917 > Project: Guacamole > Issue Type: Bug > Components: guacamole >Affects Versions: 1.0.0 >Reporter: Stephan von Krawczynski >Priority: Minor > > All hosts on arch linux. Connecting to xrdp from guacamole by rdp shows all > AltGr keys are working except ~ (tilde). I am using firefox as browser. > Connecting with rdesktop to xrdp shows ALL keys working, including ~ (tilde). > So the problem is definitely related with guacamole in some way. > All boxes configured to german and server-layout set to de-de-qwertz. > When pressing "~" a "\ " is shown (backslash space). > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-957) Multiple LDAP servers in ldap-hostname are not parsed correctly
[
https://issues.apache.org/jira/browse/GUACAMOLE-957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman updated GUACAMOLE-957:
Issue Type: Improvement (was: Bug)
> Multiple LDAP servers in ldap-hostname are not parsed correctly
> ---
>
> Key: GUACAMOLE-957
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-957
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-auth-ldap
>Affects Versions: 1.1.0
>Reporter: Robert Wolf
>Priority: Minor
>
> Hello,
> we have configured guacamole with postgresql (for configuration) and LDAP
> (for authentication only) in version 1.0.0. The LDAP server are 3 Windows AD
> servers.
> We have configured guacamole LDAP auth with {noformat}
> ldap-hostname: SERVER1 SERVER2 SERVER3
> {noformat}
> During authentication, guacamole connects to first server. If the connection
> fails, it connectes to seconds server and if this connection fails to, it
> connects to the third server. It works great in guacamole 1.0.0. But the
> version 1.0.0 has problem with LDAP groups.
> So we have updated to 1.1.0. But in this configuration the multiple LDAP
> hosts are incorrectly parsed and login does not work with "Invalid login" on
> login page and following error message in the log {noformat}
> 13:21:24.339 [http-nio-8080-exec-16] ERROR o.a.g.a.ldap.LDAPConnectionService
> - Binding with the LDAP server at "SERVER1 SERVER2 SERVER3" as user "bind-dn"
> failed: ERR_04121_CANNOT_RESOLVE_HOSTNAME Cannot connect to the server,
> Hostname 'SERVER1 SERVER2 SERVER3' could not be resolved.
> 13:21:24.340 [http-nio-8080-exec-16] ERROR
> o.a.g.a.l.AuthenticationProviderService - Unable to bind using search DN
> "bind-dn"
> 13:21:24.342 [http-nio-8080-exec-16] WARN o.a.g.r.auth.AuthenticationService
> - Authentication attempt from [10.0.48.1, 127.0.0.1] for user
> "ad.user@domain" failed.
> {noformat}
> Could you verify this issue? Is there some other possible format for multiple
> hostnames in *ldap-hostname* attribute? I have already tried to use ","
> (comma) instead of space and to use LDAP URI format, but nothing works.
> Thank you for you answer.
> Regards,
> Robert Wolf.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-957) Support configuring multiple LDAP servers
[
https://issues.apache.org/jira/browse/GUACAMOLE-957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman updated GUACAMOLE-957:
Summary: Support configuring multiple LDAP servers (was: Multiple LDAP
servers in ldap-hostname are not parsed correctly)
> Support configuring multiple LDAP servers
> -
>
> Key: GUACAMOLE-957
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-957
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-auth-ldap
>Affects Versions: 1.1.0
>Reporter: Robert Wolf
>Priority: Minor
>
> Hello,
> we have configured guacamole with postgresql (for configuration) and LDAP
> (for authentication only) in version 1.0.0. The LDAP server are 3 Windows AD
> servers.
> We have configured guacamole LDAP auth with {noformat}
> ldap-hostname: SERVER1 SERVER2 SERVER3
> {noformat}
> During authentication, guacamole connects to first server. If the connection
> fails, it connectes to seconds server and if this connection fails to, it
> connects to the third server. It works great in guacamole 1.0.0. But the
> version 1.0.0 has problem with LDAP groups.
> So we have updated to 1.1.0. But in this configuration the multiple LDAP
> hosts are incorrectly parsed and login does not work with "Invalid login" on
> login page and following error message in the log {noformat}
> 13:21:24.339 [http-nio-8080-exec-16] ERROR o.a.g.a.ldap.LDAPConnectionService
> - Binding with the LDAP server at "SERVER1 SERVER2 SERVER3" as user "bind-dn"
> failed: ERR_04121_CANNOT_RESOLVE_HOSTNAME Cannot connect to the server,
> Hostname 'SERVER1 SERVER2 SERVER3' could not be resolved.
> 13:21:24.340 [http-nio-8080-exec-16] ERROR
> o.a.g.a.l.AuthenticationProviderService - Unable to bind using search DN
> "bind-dn"
> 13:21:24.342 [http-nio-8080-exec-16] WARN o.a.g.r.auth.AuthenticationService
> - Authentication attempt from [10.0.48.1, 127.0.0.1] for user
> "ad.user@domain" failed.
> {noformat}
> Could you verify this issue? Is there some other possible format for multiple
> hostnames in *ldap-hostname* attribute? I have already tried to use ","
> (comma) instead of space and to use LDAP URI format, but nothing works.
> Thank you for you answer.
> Regards,
> Robert Wolf.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-957) Multiple LDAP servers in ldap-hostname are not parsed correctly
[
https://issues.apache.org/jira/browse/GUACAMOLE-957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman updated GUACAMOLE-957:
Priority: Minor (was: Major)
> Multiple LDAP servers in ldap-hostname are not parsed correctly
> ---
>
> Key: GUACAMOLE-957
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-957
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole-auth-ldap
>Affects Versions: 1.1.0
>Reporter: Robert Wolf
>Priority: Minor
>
> Hello,
> we have configured guacamole with postgresql (for configuration) and LDAP
> (for authentication only) in version 1.0.0. The LDAP server are 3 Windows AD
> servers.
> We have configured guacamole LDAP auth with {noformat}
> ldap-hostname: SERVER1 SERVER2 SERVER3
> {noformat}
> During authentication, guacamole connects to first server. If the connection
> fails, it connectes to seconds server and if this connection fails to, it
> connects to the third server. It works great in guacamole 1.0.0. But the
> version 1.0.0 has problem with LDAP groups.
> So we have updated to 1.1.0. But in this configuration the multiple LDAP
> hosts are incorrectly parsed and login does not work with "Invalid login" on
> login page and following error message in the log {noformat}
> 13:21:24.339 [http-nio-8080-exec-16] ERROR o.a.g.a.ldap.LDAPConnectionService
> - Binding with the LDAP server at "SERVER1 SERVER2 SERVER3" as user "bind-dn"
> failed: ERR_04121_CANNOT_RESOLVE_HOSTNAME Cannot connect to the server,
> Hostname 'SERVER1 SERVER2 SERVER3' could not be resolved.
> 13:21:24.340 [http-nio-8080-exec-16] ERROR
> o.a.g.a.l.AuthenticationProviderService - Unable to bind using search DN
> "bind-dn"
> 13:21:24.342 [http-nio-8080-exec-16] WARN o.a.g.r.auth.AuthenticationService
> - Authentication attempt from [10.0.48.1, 127.0.0.1] for user
> "ad.user@domain" failed.
> {noformat}
> Could you verify this issue? Is there some other possible format for multiple
> hostnames in *ldap-hostname* attribute? I have already tried to use ","
> (comma) instead of space and to use LDAP URI format, but nothing works.
> Thank you for you answer.
> Regards,
> Robert Wolf.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-918) Guacamole Display not visible under Shadow DOM
[
https://issues.apache.org/jira/browse/GUACAMOLE-918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman updated GUACAMOLE-918:
Priority: Minor (was: Major)
> Guacamole Display not visible under Shadow DOM
> --
>
> Key: GUACAMOLE-918
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-918
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole-common-js
>Affects Versions: 1.1.0
> Environment: guacamole-common-js 1.1.0 on Chromium 78
> org.apache.guacamole:guacamole-common:1.1.0 on OpenJDK 11
>Reporter: Jonas Zeiger
>Priority: Minor
> Attachments: guacamole-display-under-shadow-root.png
>
>
> The Guacamole display doesn't show when inserted under shadow DOM.
> The display is attached like this:
> {code:javascript}
> const wrapper = this.shadowRoot.getElementById('console-screen-wrapper');
> wrapper.style.width = '' + 640 + 'px';
> wrapper.style.height = '' + 480 + 'px';
> this.display = wrapper.appendChild(client.getDisplay().getElement());
> {code}
> The display elements including canvas are present in the DOM (see DOM
> screenshot).
> The reason seems to be the explicit canvas/layer z-index setup here:
> guacamole-common.js, Guacamole.Layer()
> {code:javascript}
> // Explicitly render canvas below other elements in the layer (such as
> // child layers). Chrome and others may fail to render layers properly
> // without this.
> canvas.style.zIndex = -1;
> {code}
> Setting canvas.style.zIndex to 0 instead of -1 makes all layers visible under
> shadow DOM.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-942) MySQL JDBC contains an invalid SQL Query (no RDP Start possible)
[
https://issues.apache.org/jira/browse/GUACAMOLE-942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17034747#comment-17034747
]
Nick Couchman commented on GUACAMOLE-942:
-
So, gathering what I believe are the relevant bits (toward the bottom):
{code:java}
23:01:46.395 [http-nio-8080-exec-7] DEBUG o.a.i.t.jdbc.JdbcTransaction -
Setting autocommit to false on JDBC Connection
[com.mysql.jdbc.JDBC4Connection@3f6d70b6]
23:01:46.395 [http-nio-8080-exec-7] DEBUG o.a.g.a.j.c.C.selectReadable - ==>
Preparing: SELECT guacamole_connection.connection_id,
guacamole_connection.connection_name, parent_id, protocol, max_connections,
max_connections_per_user, proxy_hostname, proxy_port, proxy_encryption_method,
connection_weight, failover_only, MAX(start_date) AS last_active FROM
guacamole_connection JOIN guacamole_connection_permission ON
guacamole_connection_permission.connection_id =
guacamole_connection.connection_id LEFT JOIN guacamole_connection_history ON
guacamole_connection_history.connection_id = guacamole_connection.connection_id
WHERE guacamole_connection.connection_id IN AND (
guacamole_connection_permission.entity_id = ? OR
guacamole_connection_permission.entity_id IN ( SELECT
guacamole_entity.entity_id FROM guacamole_entity JOIN guacamole_user_group ON
guacamole_user_group.entity_id = guacamole_entity.entity_id WHERE type =
'USER_GROUP' AND name IN ( ? ) AND disabled = false ) ) AND permission = 'READ'
GROUP BY guacamole_connection.connection_id; SELECT primary_connection_id,
guacamole_sharing_profile.sharing_profile_id FROM guacamole_sharing_profile
JOIN guacamole_sharing_profile_permission ON
guacamole_sharing_profile_permission.sharing_profile_id =
guacamole_sharing_profile.sharing_profile_id WHERE primary_connection_id IN AND
( entity_id = ? OR entity_id IN ( SELECT guacamole_entity.entity_id FROM
guacamole_entity JOIN guacamole_user_group ON guacamole_user_group.entity_id =
guacamole_entity.entity_id WHERE type = 'USER_GROUP' AND name IN ( ? ) AND
disabled = false ) ) AND permission = 'READ'; SELECT
guacamole_connection_attribute.connection_id, attribute_name, attribute_value
FROM guacamole_connection_attribute JOIN guacamole_connection_permission ON
guacamole_connection_permission.connection_id =
guacamole_connection_attribute.connection_id WHERE
guacamole_connection_attribute.connection_id IN AND ( entity_id = ? OR
entity_id IN ( SELECT guacamole_entity.entity_id FROM guacamole_entity JOIN
guacamole_user_group ON guacamole_user_group.entity_id =
guacamole_entity.entity_id WHERE type = 'USER_GROUP' AND name IN ( ? ) AND
disabled = false ) ) AND permission = 'READ';
23:01:46.395 [http-nio-8080-exec-7] DEBUG o.a.g.a.j.c.C.selectReadable - ==>
Parameters: 7(Integer), Familie(String), 7(Integer), Familie(String),
7(Integer), Familie(String)
23:01:46.402 [http-nio-8080-exec-7] DEBUG o.a.i.t.jdbc.JdbcTransaction -
Resetting autocommit to true on JDBC Connection
[com.mysql.jdbc.JDBC4Connection@3f6d70b6]
23:01:46.406 [http-nio-8080-exec-7] DEBUG o.a.i.t.jdbc.JdbcTransaction -
Closing JDBC Connection [com.mysql.jdbc.JDBC4Connection@3f6d70b6]
23:01:46.406 [http-nio-8080-exec-7] DEBUG o.a.i.d.pooled.PooledDataSource -
Testing connection 1064136886 ...
23:01:46.417 [http-nio-8080-exec-7] DEBUG o.a.i.d.pooled.PooledDataSource -
Connection 1064136886 is GOOD!
23:01:46.417 [http-nio-8080-exec-7] DEBUG o.a.i.d.pooled.PooledDataSource -
Returned connection 1064136886 to pool.
23:01:46.417 [http-nio-8080-exec-7] ERROR o.a.g.rest.RESTExceptionMapper -
Unexpected internal error:
### Error querying database. Cause:
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: You have an error in
your SQL syntax; check the manual that corresponds to your MariaDB server
version for the right syntax to use near 'AND
(
guacamole_connection_permission.entity_id = 7
' at line 19
### The error may exist in
org/apache/guacamole/auth/jdbc/connection/ConnectionMapper.xml
### The error may involve defaultParameterMap
### The error occurred while setting parameters
### SQL: SELECT guacamole_connection.connection_id,
guacamole_connection.connection_name, parent_id,
protocol, max_connections, max_connections_per_user,
proxy_hostname, proxy_port,
proxy_encryption_method, connection_weight,
failover_only, MAX(start_date) AS last_active FROM
guacamole_connection JOIN guacamole_connection_permission ON
guacamole_connection_permission.connection_id =
guacamole_connection.connection_id LEFT JOIN
guacamole_connection_history ON guacamole_connection_history.connection_id =
guacamole_connection.connection_id WHERE
guacamole_connection.connection_id IN AND (
[jira] [Commented] (GUACAMOLE-960) Cannot connect anymore to RDP connections after upgrade to version 1.0.0
[
https://issues.apache.org/jira/browse/GUACAMOLE-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17037126#comment-17037126
]
Nick Couchman commented on GUACAMOLE-960:
-
I think this is the issue...
{code}
Feb 14 14:11:00 eva01 guacd[8641]: Security mode: TLS
...
Feb 14 14:11:04 eva01 guacd[8641]: Protocol Security Negotiation Failure
Feb 14 14:11:04 eva01 guacd[8641]: freerdp_set_last_error
ERRCONNECT_SECURITY_NEGO_CONNECT_FAILED [0x0002000C]
Feb 14 14:11:04 eva01 guacd[8641]: Error: protocol security negotiation or
connection failure
Feb 14 14:11:04 eva01 guacd[8641]: Error connecting to RDP server
{code}
Looks like it's trying to use TLS security, and failing. Maybe try setting
security to NLA?
> Cannot connect anymore to RDP connections after upgrade to version 1.0.0
>
>
> Key: GUACAMOLE-960
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-960
> Project: Guacamole
> Issue Type: Bug
> Components: RDP
>Affects Versions: 1.1.0
> Environment: Ubuntu 18.04
> Guacamole 1.1.0
> Openjdk-8-jdk
>Reporter: Daniele
>Priority: Major
> Fix For: 1.1.0
>
> Attachments: guacd.debug.txt
>
>
> After upgrading from version 1.0.0 to version 1.1.0 I cannot connect to RDP
> connections anymore.
> This is syslog:
> ...
> Feb 14 09:43:26 x guacd[1115]: Creating new client for protocol "rdp"
> Feb 14 09:43:26 x guacd[1115]: Connection ID is
> "$c99fc3da-d103-437c-a956-d13cfaa6dbed"
> Feb 14 09:43:26 x guacd[3451]: Security mode: TLS
> Feb 14 09:43:26 x guacd[3451]: Resize method: none
> Feb 14 09:43:26 x guacd[3451]: User
> "@96d5b096-4f15-4b59-ac2e-937d0a16919d" joined connection
> "$c99fc3da-d103-437c-a956-d13cfaa6dbed" (1 users now present)
> Feb 14 09:43:26 x guacd[3451]: Loading keymap "base"
> Feb 14 09:43:26 x guacd[3451]: Loading keymap "it-it-qwerty"
> Feb 14 09:43:29 x guacd[3451]: Error connecting to RDP server
> Feb 14 09:43:29 x guacd[3451]: User
> "@96d5b096-4f15-4b59-ac2e-937d0a16919d" disconnected (0 users remain)
> Feb 14 09:43:29 x guacd[3451]: Last user of connection
> "$c99fc3da-d103-437c-a956-d13cfaa6dbed" disconnected
> Feb 14 09:43:29 x guacd[1115]: Connection
> "$c99fc3da-d103-437c-a956-d13cfaa6dbed" removed.
> ...
> This is catalina.out:
> ...
> 09:43:26.517 [http-nio-8080-exec-3] INFO o.a.g.tunnel.TunnelRequestService -
> User "xxx" connected to connection "4".
> 09:43:29.639 [http-nio-8080-exec-9] INFO o.a.g.tunnel.TunnelRequestService -
> User "xxx" disconnected from connection "4". Duration: 3108 milliseconds
> 09:45:05.715 [http-nio-8080-exec-8] INFO o.a.g.tunnel.TunnelRequestService -
> User "xxx" connected to connection "4".
> 09:45:08.807 [http-nio-8080-exec-10] INFO o.a.g.tunnel.TunnelRequestService -
> User "xxx" disconnected from connection "4". Duration: 3091 milliseconds
> Exception in thread "Thread-7" java.lang.IllegalStateException: Message will
> not be sent because the WebSocket session has been closed
> at
> org.apache.tomcat.websocket.WsRemoteEndpointImplBase.writeMessagePart(WsRemoteEndpointImplBase.java:425)
> at
> org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendMessageBlock(WsRemoteEndpointImplBase.java:309)
> at
> org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendMessageBlock(WsRemoteEndpointImplBase.java:250)
> at
> org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendString(WsRemoteEndpointImplBase.java:191)
> at
> org.apache.tomcat.websocket.WsRemoteEndpointBasic.sendText(WsRemoteEndpointBasic.java:37)
> at
> org.apache.guacamole.websocket.GuacamoleWebSocketTunnelEndpoint.sendInstruction(GuacamoleWebSocketTunnelEndpoint.java:152)
> at
> org.apache.guacamole.websocket.GuacamoleWebSocketTunnelEndpoint.access$200(GuacamoleWebSocketTunnelEndpoint.java:53)
> at
> org.apache.guacamole.websocket.GuacamoleWebSocketTunnelEndpoint$2.run(GuacamoleWebSocketTunnelEndpoint.java:253)
> ...
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-967) Cannot connect with RDP to QEMU VM running on same host with other ip address
[
https://issues.apache.org/jira/browse/GUACAMOLE-967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman updated GUACAMOLE-967:
Priority: Minor (was: Major)
> Cannot connect with RDP to QEMU VM running on same host with other ip address
> -
>
> Key: GUACAMOLE-967
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-967
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole
>Affects Versions: 1.0.0, 1.1.0
> Environment: Debian 10.1 x64, Tomcat9, nginx reverseproxy
>Reporter: Sebastian Ruff
>Priority: Minor
> Attachments: 2020-02-22
> 15_02_27-rdp_Admin@vm01.misterbit_WinServ19.png
>
>
> I had this issue since I started using Guacamole (v1.0).
> I cannot connect to my Win Server 2019 VM wich is running on the same host
> but with another public IP Adress and vituell MAC Adress.
> I never really cared that uch abut the issue, because I found an workaround,
> running a localhost qemu vnc server for that VM. But I want to get the issue
> fixed so don't have to do that for every VM.
> I thought after upgrading to 1.1 so to FreeRDP 2.0, I could be fixed, but
> that isn't the case.
> But I have to say I can connect to the rdp session with any other software
> tool running on the host machine.
> I attached an Screenshot where you can see the Error Message of the
> Guacamole client.
> {{syslog:}}
> {{}}
> {color:#cc}Feb 22 15:02:27 main-misterbit-debian101-x64 tomcat9[10806]:
> 15:02:27.703 [http-nio-127.0.0.1-8080-exec-13] INFO
> o.a.g.tunnel.TunnelRequestService - User "misterbit" connected to conne$
> Feb 22 15:02:27 main-misterbit-debian101-x64 guacd[15656]: User
> "@39fd665c-77a7-4df9-8535-01418413a889" joined connection
> "$4d7d62b5-0e34-4a3b-920d-e4dc10bbde65" (1 users now present)
> Feb 22 15:02:27 main-misterbit-debian101-x64 guacd[15656]: Loading keymap
> "base"
> Feb 22 15:02:27 main-misterbit-debian101-x64 guacd[15656]: Loading keymap
> "en-us-qwerty"
> Feb 22 15:02:27 main-misterbit-debian101-x64 guacd[15656]: Certificate
> validation failed
> Feb 22 15:02:27 main-misterbit-debian101-x64 guacd[15656]: Error connecting
> to RDP server
> Feb 22 15:02:27 main-misterbit-debian101-x64 guacd[15656]: User
> "@39fd665c-77a7-4df9-8535-01418413a889" disconnected (0 users remain)
> Feb 22 15:02:27 main-misterbit-debian101-x64 guacd[15656]: Last user of
> connection "$4d7d62b5-0e34-4a3b-920d-e4dc10bbde65" disconnected
> Feb 22 15:02:27 main-misterbit-debian101-x64 tomcat9[10806]: Exception in
> thread "Thread-22" 15:02:27.773 [http-nio-127.0.0.1-8080-exec-18] INFO
> o.a.g.tunnel.TunnelRequestService - Use$
> Feb 22 15:02:27 main-misterbit-debian101-x64 tomcat9[10806]:
> java.lang.IllegalStateException: Message will not be sent because the
> WebSocket session has been closed
> Feb 22 15:02:27 main-misterbit-debian101-x64 tomcat9[10806]:{color}
> {color:#cc}at
> org.apache.tomcat.websocket.WsRemoteEndpointImplBase.writeMessagePart(WsRemoteEndpointImplBase.java:425)
> Feb 22 15:02:27 main-misterbit-debian101-x64 tomcat9[10806]:{color}
> {color:#cc}at
> org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendMessageBlock(WsRemoteEndpointImplBase.java:309)
> Feb 22 15:02:27 main-misterbit-debian101-x64 tomcat9[10806]:{color}
> {color:#cc}at
> org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendMessageBlock(WsRemoteEndpointImplBase.java:250)
> Feb 22 15:02:27 main-misterbit-debian101-x64 tomcat9[10806]:{color}
> {color:#cc}at
> org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendString(WsRemoteEndpointImplBase.java:191)
> Feb 22 15:02:27 main-misterbit-debian101-x64 tomcat9[10806]:{color}
> {color:#cc}at
> org.apache.tomcat.websocket.WsRemoteEndpointBasic.sendText(WsRemoteEndpointBasic.java:37)
> Feb 22 15:02:27 main-misterbit-debian101-x64 tomcat9[10806]:{color}
> {color:#cc}at
> org.apache.guacamole.websocket.GuacamoleWebSocketTunnelEndpoint.sendInstruction(GuacamoleWebSocketTunnelEndpoint.java:$
> Feb 22 15:02:27 main-misterbit-debian101-x64 tomcat9[10806]:{color}
> {color:#cc}at
> org.apache.guacamole.websocket.GuacamoleWebSocketTunnelEndpoint.access$200(GuacamoleWebSocketTunnelEndpoint.java:53)
>
> Feb 22 15:02:27 main-misterbit-debian101-x64 tomcat9[10806]:{color}
> {color:#cc}at
> org.apache.guacamole.websocket.GuacamoleWebSocketTunnelEndpoint$2.run(GuacamoleWebSocketTunnelEndpoint.java:253)
>
> Feb 22 15:02:27 main-misterbit-debian101-x64 guacd[11449]: Connection
> "$4d7d62b5-0e34-4a3b-920d-e4dc10bbde65" removed.{color}
> \{{}}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-967) Cannot connect with RDP to QEMU VM running on same host with other ip address
[
https://issues.apache.org/jira/browse/GUACAMOLE-967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17042589#comment-17042589
]
Nick Couchman commented on GUACAMOLE-967:
-
I suspect that you might be running into the same issue that has been reported
by others with the WDDM driver requirement in later versions of Windows. If
you look on the mailing list archives and at the JIRA issues already entered
you may find others who have run into the same issue, and some suggested
work-arounds until we're able to figure out what needs to be done to get
Guacamole to connect correctly to systems that have WDDM enabled.
> Cannot connect with RDP to QEMU VM running on same host with other ip address
> -
>
> Key: GUACAMOLE-967
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-967
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole
>Affects Versions: 1.0.0, 1.1.0
> Environment: Debian 10.1 x64, Tomcat9, nginx reverseproxy
>Reporter: Sebastian Ruff
>Priority: Minor
> Attachments: 2020-02-22
> 15_02_27-rdp_Admin@vm01.misterbit_WinServ19.png
>
>
> I had this issue since I started using Guacamole (v1.0).
> I cannot connect to my Win Server 2019 VM wich is running on the same host
> but with another public IP Adress and vituell MAC Adress.
> I never really cared that uch abut the issue, because I found an workaround,
> running a localhost qemu vnc server for that VM. But I want to get the issue
> fixed so don't have to do that for every VM.
> I thought after upgrading to 1.1 so to FreeRDP 2.0, I could be fixed, but
> that isn't the case.
> But I have to say I can connect to the rdp session with any other software
> tool running on the host machine.
> I attached an Screenshot where you can see the Error Message of the
> Guacamole client.
> {{syslog:}}
> {{}}
> {color:#cc}Feb 22 15:02:27 main-misterbit-debian101-x64 tomcat9[10806]:
> 15:02:27.703 [http-nio-127.0.0.1-8080-exec-13] INFO
> o.a.g.tunnel.TunnelRequestService - User "misterbit" connected to conne$
> Feb 22 15:02:27 main-misterbit-debian101-x64 guacd[15656]: User
> "@39fd665c-77a7-4df9-8535-01418413a889" joined connection
> "$4d7d62b5-0e34-4a3b-920d-e4dc10bbde65" (1 users now present)
> Feb 22 15:02:27 main-misterbit-debian101-x64 guacd[15656]: Loading keymap
> "base"
> Feb 22 15:02:27 main-misterbit-debian101-x64 guacd[15656]: Loading keymap
> "en-us-qwerty"
> Feb 22 15:02:27 main-misterbit-debian101-x64 guacd[15656]: Certificate
> validation failed
> Feb 22 15:02:27 main-misterbit-debian101-x64 guacd[15656]: Error connecting
> to RDP server
> Feb 22 15:02:27 main-misterbit-debian101-x64 guacd[15656]: User
> "@39fd665c-77a7-4df9-8535-01418413a889" disconnected (0 users remain)
> Feb 22 15:02:27 main-misterbit-debian101-x64 guacd[15656]: Last user of
> connection "$4d7d62b5-0e34-4a3b-920d-e4dc10bbde65" disconnected
> Feb 22 15:02:27 main-misterbit-debian101-x64 tomcat9[10806]: Exception in
> thread "Thread-22" 15:02:27.773 [http-nio-127.0.0.1-8080-exec-18] INFO
> o.a.g.tunnel.TunnelRequestService - Use$
> Feb 22 15:02:27 main-misterbit-debian101-x64 tomcat9[10806]:
> java.lang.IllegalStateException: Message will not be sent because the
> WebSocket session has been closed
> Feb 22 15:02:27 main-misterbit-debian101-x64 tomcat9[10806]:{color}
> {color:#cc}at
> org.apache.tomcat.websocket.WsRemoteEndpointImplBase.writeMessagePart(WsRemoteEndpointImplBase.java:425)
> Feb 22 15:02:27 main-misterbit-debian101-x64 tomcat9[10806]:{color}
> {color:#cc}at
> org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendMessageBlock(WsRemoteEndpointImplBase.java:309)
> Feb 22 15:02:27 main-misterbit-debian101-x64 tomcat9[10806]:{color}
> {color:#cc}at
> org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendMessageBlock(WsRemoteEndpointImplBase.java:250)
> Feb 22 15:02:27 main-misterbit-debian101-x64 tomcat9[10806]:{color}
> {color:#cc}at
> org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendString(WsRemoteEndpointImplBase.java:191)
> Feb 22 15:02:27 main-misterbit-debian101-x64 tomcat9[10806]:{color}
> {color:#cc}at
> org.apache.tomcat.websocket.WsRemoteEndpointBasic.sendText(WsRemoteEndpointBasic.java:37)
> Feb 22 15:02:27 main-misterbit-debian101-x64 tomcat9[10806]:{color}
> {color:#cc}at
> org.apache.guacamole.websocket.GuacamoleWebSocketTunnelEndpoint.sendInstruction(GuacamoleWebSocketTunnelEndpoint.java:$
> Feb 22 15:02:27 main-misterbit-debian101-x64 tomcat9[10806]:{color}
> {color:#cc}at
> org.apache.guacamole.websocket.GuacamoleWebSocketTunnelEndpoint.access$200(GuacamoleWebSocketTunnelEndpoint.java:53)
>
> Feb 22 15:02:27 main-misterbit-debian101-x64 tomcat9[10806]:{color}
> {color:#cc}at
>
[jira] [Updated] (GUACAMOLE-962) Support relaxed order checking for VirtualBox RDP
[
https://issues.apache.org/jira/browse/GUACAMOLE-962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman updated GUACAMOLE-962:
Priority: Minor (was: Major)
> Support relaxed order checking for VirtualBox RDP
> -
>
> Key: GUACAMOLE-962
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-962
> Project: Guacamole
> Issue Type: Improvement
> Components: RDP
>Affects Versions: 1.1.0
>Reporter: Gilbert Shih
>Priority: Minor
>
> After upgrading from 1.0.0 (docker) to 1.1.0 (docker), the guacamole cannot
> connect to virtual box VMs with virtualbox RDP.
>
> Below is the error logs I got while trying to connect to a virtual box client
> through VRDP.
> {code:java}
> guacd[248]: INFO: No security mode specified. Defaulting to security mode
> negotiation with server.
> guacd[248]: INFO: Resize method: none
> guacd[248]: INFO: User "@92a830f3-f271-4cf8-b99e-0d72ec3f301d" joined
> connection "$41973560-facd-4ea4-890f-94916c2f03ae" (1 users now present)
> guacd[248]: INFO: Loading keymap "base"
> guacd[248]: INFO: Loading keymap "en-us-qwerty"
> guacd[248]: INFO: Accepted format: 16-bit PCM with 2 channels at 22050 Hz
> guacd[248]: INFO: Connected to RDPDR 1.12 as client 0x000a
> guacd[248]: ERROR: Connection closed.
> guacd[248]: INFO: User "@92a830f3-f271-4cf8-b99e-0d72ec3f301d" disconnected
> (0 users remain)
> guacd[248]: INFO: Last user of connection
> "$41973560-facd-4ea4-890f-94916c2f03ae" disconnected
> guacd[248]: INFO: Internal RDP client disconnected
> guacd[6]: INFO: Connection "$41973560-facd-4ea4-890f-94916c2f03ae" removed.
> {code}
>
> On the contrary, there is no problem for guacamole to connect to a machine
> with the windows built-in RDP.
>
>
> {code:java}
> guacd[2011]: INFO: Security mode: NLA
> guacd[2011]: INFO: Resize method: none
> guacd[2011]: INFO: User "@23bf8d8d-840d-49a3-8716-d2232f51d6fd" joined
> connection "$35ebd7dd-b99c-423c-b6b2-03a6ad5b584b" (1 users now present)
> guacd[2011]: INFO: Loading keymap "base"
> guacd[2011]: INFO: Loading keymap "en-us-qwerty"
> guacd[2011]: INFO: Connected to RDPDR 1.13 as client 0x0003
> guacd[2011]: INFO: Connected to RDPDR 1.13 as client 0x0002
> guacd[2011]: INFO: RDPDR user logged on
>
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-962) Support relaxed order checking for VirtualBox RDP
[
https://issues.apache.org/jira/browse/GUACAMOLE-962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman updated GUACAMOLE-962:
Issue Type: Improvement (was: Bug)
> Support relaxed order checking for VirtualBox RDP
> -
>
> Key: GUACAMOLE-962
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-962
> Project: Guacamole
> Issue Type: Improvement
> Components: RDP
>Affects Versions: 1.1.0
>Reporter: Gilbert Shih
>Priority: Major
>
> After upgrading from 1.0.0 (docker) to 1.1.0 (docker), the guacamole cannot
> connect to virtual box VMs with virtualbox RDP.
>
> Below is the error logs I got while trying to connect to a virtual box client
> through VRDP.
> {code:java}
> guacd[248]: INFO: No security mode specified. Defaulting to security mode
> negotiation with server.
> guacd[248]: INFO: Resize method: none
> guacd[248]: INFO: User "@92a830f3-f271-4cf8-b99e-0d72ec3f301d" joined
> connection "$41973560-facd-4ea4-890f-94916c2f03ae" (1 users now present)
> guacd[248]: INFO: Loading keymap "base"
> guacd[248]: INFO: Loading keymap "en-us-qwerty"
> guacd[248]: INFO: Accepted format: 16-bit PCM with 2 channels at 22050 Hz
> guacd[248]: INFO: Connected to RDPDR 1.12 as client 0x000a
> guacd[248]: ERROR: Connection closed.
> guacd[248]: INFO: User "@92a830f3-f271-4cf8-b99e-0d72ec3f301d" disconnected
> (0 users remain)
> guacd[248]: INFO: Last user of connection
> "$41973560-facd-4ea4-890f-94916c2f03ae" disconnected
> guacd[248]: INFO: Internal RDP client disconnected
> guacd[6]: INFO: Connection "$41973560-facd-4ea4-890f-94916c2f03ae" removed.
> {code}
>
> On the contrary, there is no problem for guacamole to connect to a machine
> with the windows built-in RDP.
>
>
> {code:java}
> guacd[2011]: INFO: Security mode: NLA
> guacd[2011]: INFO: Resize method: none
> guacd[2011]: INFO: User "@23bf8d8d-840d-49a3-8716-d2232f51d6fd" joined
> connection "$35ebd7dd-b99c-423c-b6b2-03a6ad5b584b" (1 users now present)
> guacd[2011]: INFO: Loading keymap "base"
> guacd[2011]: INFO: Loading keymap "en-us-qwerty"
> guacd[2011]: INFO: Connected to RDPDR 1.13 as client 0x0003
> guacd[2011]: INFO: Connected to RDPDR 1.13 as client 0x0002
> guacd[2011]: INFO: RDPDR user logged on
>
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-962) Support relaxed order checking for VirtualBox RDP
[
https://issues.apache.org/jira/browse/GUACAMOLE-962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman updated GUACAMOLE-962:
Summary: Support relaxed order checking for VirtualBox RDP (was: Version
1.1.0 doesn't work with virtualbox RDP)
> Support relaxed order checking for VirtualBox RDP
> -
>
> Key: GUACAMOLE-962
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-962
> Project: Guacamole
> Issue Type: Bug
> Components: RDP
>Affects Versions: 1.1.0
>Reporter: Gilbert Shih
>Priority: Major
>
> After upgrading from 1.0.0 (docker) to 1.1.0 (docker), the guacamole cannot
> connect to virtual box VMs with virtualbox RDP.
>
> Below is the error logs I got while trying to connect to a virtual box client
> through VRDP.
> {code:java}
> guacd[248]: INFO: No security mode specified. Defaulting to security mode
> negotiation with server.
> guacd[248]: INFO: Resize method: none
> guacd[248]: INFO: User "@92a830f3-f271-4cf8-b99e-0d72ec3f301d" joined
> connection "$41973560-facd-4ea4-890f-94916c2f03ae" (1 users now present)
> guacd[248]: INFO: Loading keymap "base"
> guacd[248]: INFO: Loading keymap "en-us-qwerty"
> guacd[248]: INFO: Accepted format: 16-bit PCM with 2 channels at 22050 Hz
> guacd[248]: INFO: Connected to RDPDR 1.12 as client 0x000a
> guacd[248]: ERROR: Connection closed.
> guacd[248]: INFO: User "@92a830f3-f271-4cf8-b99e-0d72ec3f301d" disconnected
> (0 users remain)
> guacd[248]: INFO: Last user of connection
> "$41973560-facd-4ea4-890f-94916c2f03ae" disconnected
> guacd[248]: INFO: Internal RDP client disconnected
> guacd[6]: INFO: Connection "$41973560-facd-4ea4-890f-94916c2f03ae" removed.
> {code}
>
> On the contrary, there is no problem for guacamole to connect to a machine
> with the windows built-in RDP.
>
>
> {code:java}
> guacd[2011]: INFO: Security mode: NLA
> guacd[2011]: INFO: Resize method: none
> guacd[2011]: INFO: User "@23bf8d8d-840d-49a3-8716-d2232f51d6fd" joined
> connection "$35ebd7dd-b99c-423c-b6b2-03a6ad5b584b" (1 users now present)
> guacd[2011]: INFO: Loading keymap "base"
> guacd[2011]: INFO: Loading keymap "en-us-qwerty"
> guacd[2011]: INFO: Connected to RDPDR 1.13 as client 0x0003
> guacd[2011]: INFO: Connected to RDPDR 1.13 as client 0x0002
> guacd[2011]: INFO: RDPDR user logged on
>
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-962) Support relaxed order checking for VirtualBox RDP
[
https://issues.apache.org/jira/browse/GUACAMOLE-962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17042681#comment-17042681
]
Nick Couchman commented on GUACAMOLE-962:
-
Ah, okay - I wasn't sure if we should consider it a regression, since the
regression isn't in our code, but in the upstream library. I can mark it back
as a bug, though, that's fine.
> Support relaxed order checking for VirtualBox RDP
> -
>
> Key: GUACAMOLE-962
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-962
> Project: Guacamole
> Issue Type: Improvement
> Components: RDP
>Affects Versions: 1.1.0
>Reporter: Gilbert Shih
>Priority: Minor
>
> After upgrading from 1.0.0 (docker) to 1.1.0 (docker), the guacamole cannot
> connect to virtual box VMs with virtualbox RDP.
>
> Below is the error logs I got while trying to connect to a virtual box client
> through VRDP.
> {code:java}
> guacd[248]: INFO: No security mode specified. Defaulting to security mode
> negotiation with server.
> guacd[248]: INFO: Resize method: none
> guacd[248]: INFO: User "@92a830f3-f271-4cf8-b99e-0d72ec3f301d" joined
> connection "$41973560-facd-4ea4-890f-94916c2f03ae" (1 users now present)
> guacd[248]: INFO: Loading keymap "base"
> guacd[248]: INFO: Loading keymap "en-us-qwerty"
> guacd[248]: INFO: Accepted format: 16-bit PCM with 2 channels at 22050 Hz
> guacd[248]: INFO: Connected to RDPDR 1.12 as client 0x000a
> guacd[248]: ERROR: Connection closed.
> guacd[248]: INFO: User "@92a830f3-f271-4cf8-b99e-0d72ec3f301d" disconnected
> (0 users remain)
> guacd[248]: INFO: Last user of connection
> "$41973560-facd-4ea4-890f-94916c2f03ae" disconnected
> guacd[248]: INFO: Internal RDP client disconnected
> guacd[6]: INFO: Connection "$41973560-facd-4ea4-890f-94916c2f03ae" removed.
> {code}
>
> On the contrary, there is no problem for guacamole to connect to a machine
> with the windows built-in RDP.
>
>
> {code:java}
> guacd[2011]: INFO: Security mode: NLA
> guacd[2011]: INFO: Resize method: none
> guacd[2011]: INFO: User "@23bf8d8d-840d-49a3-8716-d2232f51d6fd" joined
> connection "$35ebd7dd-b99c-423c-b6b2-03a6ad5b584b" (1 users now present)
> guacd[2011]: INFO: Loading keymap "base"
> guacd[2011]: INFO: Loading keymap "en-us-qwerty"
> guacd[2011]: INFO: Connected to RDPDR 1.13 as client 0x0003
> guacd[2011]: INFO: Connected to RDPDR 1.13 as client 0x0002
> guacd[2011]: INFO: RDPDR user logged on
>
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-962) Support relaxed order checking for VirtualBox RDP
[
https://issues.apache.org/jira/browse/GUACAMOLE-962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman updated GUACAMOLE-962:
Issue Type: Bug (was: Improvement)
> Support relaxed order checking for VirtualBox RDP
> -
>
> Key: GUACAMOLE-962
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-962
> Project: Guacamole
> Issue Type: Bug
> Components: RDP
>Affects Versions: 1.1.0
>Reporter: Gilbert Shih
>Priority: Minor
>
> After upgrading from 1.0.0 (docker) to 1.1.0 (docker), the guacamole cannot
> connect to virtual box VMs with virtualbox RDP.
>
> Below is the error logs I got while trying to connect to a virtual box client
> through VRDP.
> {code:java}
> guacd[248]: INFO: No security mode specified. Defaulting to security mode
> negotiation with server.
> guacd[248]: INFO: Resize method: none
> guacd[248]: INFO: User "@92a830f3-f271-4cf8-b99e-0d72ec3f301d" joined
> connection "$41973560-facd-4ea4-890f-94916c2f03ae" (1 users now present)
> guacd[248]: INFO: Loading keymap "base"
> guacd[248]: INFO: Loading keymap "en-us-qwerty"
> guacd[248]: INFO: Accepted format: 16-bit PCM with 2 channels at 22050 Hz
> guacd[248]: INFO: Connected to RDPDR 1.12 as client 0x000a
> guacd[248]: ERROR: Connection closed.
> guacd[248]: INFO: User "@92a830f3-f271-4cf8-b99e-0d72ec3f301d" disconnected
> (0 users remain)
> guacd[248]: INFO: Last user of connection
> "$41973560-facd-4ea4-890f-94916c2f03ae" disconnected
> guacd[248]: INFO: Internal RDP client disconnected
> guacd[6]: INFO: Connection "$41973560-facd-4ea4-890f-94916c2f03ae" removed.
> {code}
>
> On the contrary, there is no problem for guacamole to connect to a machine
> with the windows built-in RDP.
>
>
> {code:java}
> guacd[2011]: INFO: Security mode: NLA
> guacd[2011]: INFO: Resize method: none
> guacd[2011]: INFO: User "@23bf8d8d-840d-49a3-8716-d2232f51d6fd" joined
> connection "$35ebd7dd-b99c-423c-b6b2-03a6ad5b584b" (1 users now present)
> guacd[2011]: INFO: Loading keymap "base"
> guacd[2011]: INFO: Loading keymap "en-us-qwerty"
> guacd[2011]: INFO: Connected to RDPDR 1.13 as client 0x0003
> guacd[2011]: INFO: Connected to RDPDR 1.13 as client 0x0002
> guacd[2011]: INFO: RDPDR user logged on
>
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-962) Support relaxed order checking for VirtualBox RDP
[
https://issues.apache.org/jira/browse/GUACAMOLE-962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17042689#comment-17042689
]
Nick Couchman commented on GUACAMOLE-962:
-
Makes sense - thanks for the guidance. I've re-marked it as a bug.
> Support relaxed order checking for VirtualBox RDP
> -
>
> Key: GUACAMOLE-962
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-962
> Project: Guacamole
> Issue Type: Bug
> Components: RDP
>Affects Versions: 1.1.0
>Reporter: Gilbert Shih
>Priority: Minor
>
> After upgrading from 1.0.0 (docker) to 1.1.0 (docker), the guacamole cannot
> connect to virtual box VMs with virtualbox RDP.
>
> Below is the error logs I got while trying to connect to a virtual box client
> through VRDP.
> {code:java}
> guacd[248]: INFO: No security mode specified. Defaulting to security mode
> negotiation with server.
> guacd[248]: INFO: Resize method: none
> guacd[248]: INFO: User "@92a830f3-f271-4cf8-b99e-0d72ec3f301d" joined
> connection "$41973560-facd-4ea4-890f-94916c2f03ae" (1 users now present)
> guacd[248]: INFO: Loading keymap "base"
> guacd[248]: INFO: Loading keymap "en-us-qwerty"
> guacd[248]: INFO: Accepted format: 16-bit PCM with 2 channels at 22050 Hz
> guacd[248]: INFO: Connected to RDPDR 1.12 as client 0x000a
> guacd[248]: ERROR: Connection closed.
> guacd[248]: INFO: User "@92a830f3-f271-4cf8-b99e-0d72ec3f301d" disconnected
> (0 users remain)
> guacd[248]: INFO: Last user of connection
> "$41973560-facd-4ea4-890f-94916c2f03ae" disconnected
> guacd[248]: INFO: Internal RDP client disconnected
> guacd[6]: INFO: Connection "$41973560-facd-4ea4-890f-94916c2f03ae" removed.
> {code}
>
> On the contrary, there is no problem for guacamole to connect to a machine
> with the windows built-in RDP.
>
>
> {code:java}
> guacd[2011]: INFO: Security mode: NLA
> guacd[2011]: INFO: Resize method: none
> guacd[2011]: INFO: User "@23bf8d8d-840d-49a3-8716-d2232f51d6fd" joined
> connection "$35ebd7dd-b99c-423c-b6b2-03a6ad5b584b" (1 users now present)
> guacd[2011]: INFO: Loading keymap "base"
> guacd[2011]: INFO: Loading keymap "en-us-qwerty"
> guacd[2011]: INFO: Connected to RDPDR 1.13 as client 0x0003
> guacd[2011]: INFO: Connected to RDPDR 1.13 as client 0x0002
> guacd[2011]: INFO: RDPDR user logged on
>
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (GUACAMOLE-954) LDAP Authentication, users require explicit creation in MySQL for connection sharing.
[ https://issues.apache.org/jira/browse/GUACAMOLE-954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman closed GUACAMOLE-954. --- Resolution: Duplicate > LDAP Authentication, users require explicit creation in MySQL for connection > sharing. > - > > Key: GUACAMOLE-954 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-954 > Project: Guacamole > Issue Type: Improvement > Components: guacamole-server >Affects Versions: 1.1.0 >Reporter: Nils >Priority: Major > > Using LDAP for authentication, MySQL to store connection information. > Login works fine, however unable to share connections with other LDAP users > without first explicitly creating these users in MySQL as well. Likewise for > groups, if I share connections with a LDAP Group, users that are a member of > this group will not see any connections that are shared with this group. > I'm pretty sure that at some point, prior to the official 1.1.0 release, this > was working. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-820) Filters containing IP addresses do not match connection properties/parameters
[ https://issues.apache.org/jira/browse/GUACAMOLE-820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-820: Fix Version/s: 1.2.0 > Filters containing IP addresses do not match connection properties/parameters > - > > Key: GUACAMOLE-820 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-820 > Project: Guacamole > Issue Type: Bug > Components: guacamole-client >Affects Versions: 1.0.0 >Reporter: Nicolas CHARREL >Priority: Minor > Fix For: 1.2.0 > > Attachments: image-2019-06-19-17-11-43-136.png, > image-2019-06-19-17-12-53-087.png > > > Hello, > All my connections are named "HOSTNAME - IP". By example "GUAC - 127.0.0.1" > When I'm looking for this entry, I type in the filter 127.0.0.1 and I find > nothing. But when I type 127.0.0. I find my entry. > It's seems when I'm looking for a full IP there is a bug and the search > always return empty list. > First case (with 127.0.0), I find my connection: > !image-2019-06-19-17-11-43-136.png! > > Second case (with all the ip), there is no answer: > !image-2019-06-19-17-12-53-087.png! > Thanks for your help ! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-759) update translation fr.json for guacamole-client
[ https://issues.apache.org/jira/browse/GUACAMOLE-759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-759: Fix Version/s: 1.2.0 > update translation fr.json for guacamole-client > --- > > Key: GUACAMOLE-759 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-759 > Project: Guacamole > Issue Type: Improvement > Components: guacamole-client >Reporter: Fezzi >Priority: Minor > Fix For: 1.2.0 > > > > See > https://github.com/apache/guacamole-client/pull/390 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-903) Improved Chinese internationalization support
[ https://issues.apache.org/jira/browse/GUACAMOLE-903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-903: Fix Version/s: 1.2.0 > Improved Chinese internationalization support > - > > Key: GUACAMOLE-903 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-903 > Project: Guacamole > Issue Type: Improvement > Components: guacamole-auth-jdbc, guacamole-auth-jdbc-mysql, > guacamole-client >Affects Versions: 1.1.0 >Reporter: XYUU >Priority: Minor > Fix For: 1.2.0 > > > Due to the missing content of Chinese internationalization in the new > version, I used English as a template to complete this improvement. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-793) CAS Provider returns Group - like LDAP Provider
[ https://issues.apache.org/jira/browse/GUACAMOLE-793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-793: Fix Version/s: 1.2.0 > CAS Provider returns Group - like LDAP Provider > --- > > Key: GUACAMOLE-793 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-793 > Project: Guacamole > Issue Type: Improvement > Components: guacamole-auth-cas >Affects Versions: 1.0.0 >Reporter: David Young >Priority: Minor > Labels: features > Fix For: 1.2.0 > > > This Improvement would reduce admin for those who use CAS for authentication > with a database provider that will be using Groups to mange connections, if > Groups could be > used somehow. > One possibility... > CAS Servers could be configured to return a Group name that matches a > Group in the database. > In this wishful scenario the CAS provider would then treat the Group name in > the same way the LDAP Provider now appears to be doing with the resolution > of issue 715. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-818) Missing some files in the sftp file system
[ https://issues.apache.org/jira/browse/GUACAMOLE-818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-818: Fix Version/s: 1.2.0 > Missing some files in the sftp file system > -- > > Key: GUACAMOLE-818 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-818 > Project: Guacamole > Issue Type: Bug > Components: guacamole >Affects Versions: 1.0.0 >Reporter: kwangheelee >Priority: Minor > Fix For: 1.2.0 > > Attachments: blob-20190621.json, filesystem1.png, filesystem2.png, > location-of-20190419-within-json.png, missing1.png, missing2.png > > > I am currently developing using Guacamole version 1.0.0. There are some bugs > in uploading/downloading files through the sftp file system. > I checked the source and found that when importing the sftp file structure, > if the number of files and directories is large, it is obtained by dividing > buffer. It does not matter when the number of files is small, but when the > number of files is large, it is confirmed that some files are missing. > For example, when loading a file system with three buffers, two files are > missing. > = > Client : 3.get,1.0,31./home/guacd/guacamole/recording; > Server : > 4.body,1.0,1.0,53.application/vnd.glyptodon.guacamole.stream-index+json,31./home/guacd/guacamole/recording; > Client : 3.ack,1.0,5.Ready,1.0; > Server : 4.blob,1.0,5416.SOME DATA; > Client : 3.ack,1.0,8.Received,1.0; > Server : 4.blob,1.0,3168.SOME DATA;3.end,1.0; > client : 3.ack,1.0,8.Received,1.0; > = > I do not know if it is a guacamole issue or a libssh2 issue, and I would like > to make a correction. > Attachment can not be transferred because of security problem in company > system. > (Please write your email address in Comments and I will send you an > attachment.) > Thanks. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-474) Allow file upload and download to be enabled separately
[ https://issues.apache.org/jira/browse/GUACAMOLE-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-474: Fix Version/s: 1.2.0 > Allow file upload and download to be enabled separately > --- > > Key: GUACAMOLE-474 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-474 > Project: Guacamole > Issue Type: New Feature > Components: guacamole >Reporter: Amarjeet Singh >Assignee: Nick Couchman >Priority: Minor > Fix For: 1.2.0 > > > It would be helpful if file downloads could be disabled while still allowing > file uploads. In a classroom setting, it would be beneficial to allow > students to upload files to a remote VM, but disable download of files like > binary license files. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-465) Guacenc should support more formats and containers
[ https://issues.apache.org/jira/browse/GUACAMOLE-465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-465: Fix Version/s: 1.2.0 > Guacenc should support more formats and containers > -- > > Key: GUACAMOLE-465 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-465 > Project: Guacamole > Issue Type: New Feature > Components: guacenc >Reporter: Sean Reid >Priority: Minor > Fix For: 1.2.0 > > > Guacenc should support more formats than just mpeg4 in an m4v file type. It > should support true media containers with libavformat rather than just > writing the encoded frames into a file. > Because Guacamole is a web-based application, it makes sense that at the very > least its video encoder should support common web video formats (h.264 + mp4). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-728) Docker image unable to connect to MySQL8 docker: Public Key Retrieval Not Allowed
[
https://issues.apache.org/jira/browse/GUACAMOLE-728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman updated GUACAMOLE-728:
Fix Version/s: 1.2.0
> Docker image unable to connect to MySQL8 docker: Public Key Retrieval Not
> Allowed
> -
>
> Key: GUACAMOLE-728
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-728
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole-auth-jdbc-mysql
>Affects Versions: 1.0.0
>Reporter: David
>Priority: Major
> Fix For: 1.2.0
>
>
> When running the guacamole docker image linked to a mysql8 docker image, I'm
> experiencing an error in the logs that says:
> {code:none}
> Fri Feb 08 04:24:15 UTC 2019 WARN: Establishing SSL connection without
> server's identity verification is not recommended. According to MySQL
> 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established
> by default if explicit option isn't set. For compliance with existing
> applications not using SSL the verifyServerCertificate property is set to
> 'false'. You need either to explicitly disable SSL by setting useSSL=false,
> or set useSSL=true and provide truststore for server certificate verification.
> Fri Feb 08 04:24:15 UTC 2019 WARN: Establishing SSL connection without
> server's identity verification is not recommended. According to MySQL
> 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established
> by default if explicit option isn't set. For compliance with existing
> applications not using SSL the verifyServerCertificate property is set to
> 'false'. You need either to explicitly disable SSL by setting useSSL=false,
> or set useSSL=true and provide truststore for server certificate verification.
> 04:24:15.832 [http-nio-8080-exec-7] ERROR o.a.g.rest.RESTExceptionMapper -
> Unexpected internal error:
> ### Error querying database. Cause:
> com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: Public
> Key Retrieval is not allowed
> ### The error may exist in org/apache/guacamole/auth/jdbc/user/UserMapper.xml
> ### The error may involve
> org.apache.guacamole.auth.jdbc.user.UserMapper.selectOne
> ### The error occurred while executing a query
> ### Cause:
> com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: Public
> Key Retrieval is not allowed
> {code}
> I'm not sure how to get around this, but it's keeping me from using
> guacamole. :(
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-883) Touch mouse emulation no longer works as of iOS 13
[ https://issues.apache.org/jira/browse/GUACAMOLE-883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-883: Fix Version/s: 1.2.0 > Touch mouse emulation no longer works as of iOS 13 > -- > > Key: GUACAMOLE-883 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-883 > Project: Guacamole > Issue Type: Bug > Components: guacamole-client >Affects Versions: 1.0.0, 1.1.0 >Reporter: Thomas >Assignee: Mike Jumper >Priority: Minor > Fix For: 1.2.0 > > > With devices running iOS 13, it is no longer possible to interact with remote > desktops using touch-driven mouse emulation. The specific reason for this is > not yet known. Older releases of iOS work correctly. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-942) MySQL JDBC contains an invalid SQL Query (no RDP Start possible)
[
https://issues.apache.org/jira/browse/GUACAMOLE-942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman updated GUACAMOLE-942:
Fix Version/s: 1.2.0
> MySQL JDBC contains an invalid SQL Query (no RDP Start possible)
>
>
> Key: GUACAMOLE-942
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-942
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole-auth-jdbc-mysql
>Affects Versions: 1.1.0
> Environment: CentOS 8
> Tomcat 9.0.30
> Guacamole 1.1.0, freshly upgraded from 0.9.14.
> LDAP backend
> JDBC MySQL connector 5.1.46 to MariaDB.
>Reporter: Stefan Bluhm
>Priority: Major
> Fix For: 1.2.0
>
> Attachments: catalina.zip
>
>
> After logging in and selecting an RDP connection, the connection fails with:
>
> "The remote desktop server is currently not unreachable."...
>
> The catalona.out log shows the following error:
> {code:none}
> 17:02:02.435 [http-nio-8080-exec-3] ERROR o.a.g.rest.RESTExceptionMapper -
> Unexpected internal error:
> ### Error querying database. Cause:
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: You have an error
> in your SQL syntax; check the manual that corresponds to your MariaDB server
> version for the right syntax to use near 'AND
> (
> guacamole_connection_permission.entity_id = 7
> ' at line 19
> ### The error may exist in
> org/apache/guacamole/auth/jdbc/connection/ConnectionMapper.xml
> ### The error may involve defaultParameterMap
> ### The error occurred while setting parameters
> ### SQL: SELECT guacamole_connection.connection_id,
> guacamole_connection.connection_name, parent_id, protocol, max_connections,
> max_connections_per_user, proxy_hostname, proxy_port,
> proxy_encryption_method, connection_weight, failover_only, MAX(start_date) AS
> last_active FROM guacamole_connection JOIN guacamole_connection_permission ON
> guacamole_connection_permission.connection_id =
> guacamole_connection.connection_id LEFT JOIN guacamole_connection_history ON
> guacamole_connection_history.connection_id =
> guacamole_connection.connection_id WHERE guacamole_connection.connection_id
> IN AND ( guacamole_connection_permission.entity_id = ? ) AND permission =
> 'READ' GROUP BY guacamole_connection.connection_id; SELECT
> primary_connection_id, guacamole_sharing_profile.sharing_profile_id FROM
> guacamole_sharing_profile JOIN guacamole_sharing_profile_permission ON
> guacamole_sharing_profile_permission.sharing_profile_id =
> guacamole_sharing_profile.sharing_profile_id WHERE primary_connection_id IN
> AND ( entity_id = ? ) AND permission = 'READ'; SELECT
> guacamole_connection_attribute.connection_id, attribute_name, attribute_value
> FROM guacamole_connection_attribute JOIN guacamole_connection_permission ON
> guacamole_connection_permission.connection_id =
> guacamole_connection_attribute.connection_id WHERE
> guacamole_connection_attribute.connection_id IN AND ( entity_id = ? ) AND
> permission = 'READ';
> ### Cause: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: You
> have an error in your SQL syntax; check the manual that corresponds to your
> MariaDB server version for the right syntax to use near 'AND
> (
> guacamole_connection_permission.entity_id = 7
> ' at line 19
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-917) Key mapping for German keyboards: ~ does not work
[ https://issues.apache.org/jira/browse/GUACAMOLE-917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-917: Fix Version/s: 1.2.0 > Key mapping for German keyboards: ~ does not work > - > > Key: GUACAMOLE-917 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-917 > Project: Guacamole > Issue Type: Bug > Components: guacamole >Affects Versions: 1.0.0 >Reporter: Stephan von Krawczynski >Priority: Minor > Fix For: 1.2.0 > > > All hosts on arch linux. Connecting to xrdp from guacamole by rdp shows all > AltGr keys are working except ~ (tilde). I am using firefox as browser. > Connecting with rdesktop to xrdp shows ALL keys working, including ~ (tilde). > So the problem is definitely related with guacamole in some way. > All boxes configured to german and server-layout set to de-de-qwertz. > When pressing "~" a "\ " is shown (backslash space). > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-708) Allow JDBC Users to be Created Automatically
[ https://issues.apache.org/jira/browse/GUACAMOLE-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-708: Fix Version/s: 1.2.0 > Allow JDBC Users to be Created Automatically > > > Key: GUACAMOLE-708 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-708 > Project: Guacamole > Issue Type: New Feature > Components: guacamole-auth-jdbc >Reporter: Nick Couchman >Assignee: Nick Couchman >Priority: Minor > Fix For: 1.2.0 > > > A feature common to other applications that store data in one place and can > authenticate from other sources is to enable automatic creation of user > accounts within the database assuming the user is successfully authenticated > elsewhere. > I propose doing something similar with the Guacamole JDBC extension, or, > depending on how the implementation works out, with the other extensions - a > property that, disabled by default, could be enabled that would allow users > authenticated successfully through other extensions to be automatically > created within the JDBC extension. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-513) Wake on LAN integration
[ https://issues.apache.org/jira/browse/GUACAMOLE-513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-513: Fix Version/s: 1.2.0 > Wake on LAN integration > --- > > Key: GUACAMOLE-513 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-513 > Project: Guacamole > Issue Type: New Feature >Reporter: Matt Blecha >Assignee: Nick Couchman >Priority: Minor > Fix For: 1.2.0 > > > I'm beating this horse back to life from the old issue tracker as I do > believe this is a rather important feature. > I know it was stated a day or two ago in the old issue tracker that there was > better justification necessary for this to be considered. Seeing as this > appears to be supported by both Microsoft in their RD Gateway and in Citrix's > gateway products since ~2014, there appears to be a fairly reasonable > justification for such a feature already in the business community, as well > as demand (seeing as Citrix made a fairly prominent announcement about it.) > > ===Begin TL;DR=== > > We love Guacamole in terms of performance (even when most of our users opted > to go the VNC route, despite having the RDP option made available to them), > mobile device operation, ease of use and administration and the pure > brain-dead simplicity of implementation and integration. (Thanks to the > developer who wrote that installation script, we were zero to deployed and > operating in less than 15 minutes, VM server spin-up included!) > That being said, we may be forced to abandon the whole infrastructure on > nearly 500 devices (and growing fast) in favor of a solution that is not as > efficient, yet provides one feature that we dearly need. > From my research (not as a coder, but serious DevOps experience) it's > relatively trivial to craft and broadcast a magic packet in Java (A GitHub > search yields several project with examples averaging about ~75 LOC, > including sanity checking.) Adding in a sort of "timeout hold-off" should > yield less than an additional 100 LOC, and user interface adjustments, > probably another few dozen or so. (Semi-educated guess.) All that would be > left then is to add an optional MAC address field to the proper table and > connection form, maybe a checkbox to enable WOL. > If WOL is simply too hard to code into Guacamole, then a more expansive set > of classes in the connection API would go a long way towards being able to > develop an extension. (From what I can see of the API docs, there appears to > be one call that would allow us to start the WOL process, but there are > several others necessary, for example; being able to hold off the connection > timeout while the remote station completes waking up. We do, after all, want > this to be a seamless process to the end user.) > > ===End TL;DR=== > > It seems to me that there are several reasonable use cases for such a > feature, even if it is an extension and not a core component, though it seems > this would probably be easier to merge into core as it would work more > elegantly with some database integration, which I did not see in the API > docs. (Admittedly, might not have looked closely enough, and I don't really > code Java, so I'm not sure what's in that section.) > I do think this would go a long way in scoring a decent amount of points for > this project. It seems like there are others out there who support such a > feature, hacky as it may be in some products. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-823) Empty balancing group does not render as connection
[
https://issues.apache.org/jira/browse/GUACAMOLE-823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman updated GUACAMOLE-823:
Fix Version/s: 1.2.0
> Empty balancing group does not render as connection
> ---
>
> Key: GUACAMOLE-823
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-823
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole
>Reporter: Mike Jumper
>Priority: Minor
> Fix For: 1.2.0
>
> Attachments: connection-group-0.9.9.png, connection-group-latest.png
>
>
> In Guacamole 0.9.9 and older, empty balancing groups render as if they are
> connections. This allows balancing groups to appear to users as if they are
> connections if those users have no direct access to the connections within
> those groups:
> !connection-group-0.9.9.png!
> From 0.9.10-incubating onward (including current {{master}}), such balancing
> groups always render as groups. The "+/-" icon is displayed, albeit grayed
> out for empty groups, and the group is not rendered as a connection:
> !connection-group-latest.png!
> To reproduce:
> # Log in as an administrator.
> # Create an organizational group.
> # Create a balancing group.
> # Create a connection within the balancing group. For the sake of reproducing
> the issue, the content of this connection does not matter.
> # Create a user that has access _only_ to the organizational and balancing
> groups created above. Do not grant this user access to the connection within
> the balancing group.
> # Log out and back in as the newly-created user.
> # Note that the balancing group renders identically to the organizational
> group.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-103) SAML 2.0 support for user authentication
[ https://issues.apache.org/jira/browse/GUACAMOLE-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-103: Fix Version/s: 1.2.0 > SAML 2.0 support for user authentication > > > Key: GUACAMOLE-103 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-103 > Project: Guacamole > Issue Type: New Feature >Reporter: Justin P >Assignee: Nick Couchman >Priority: Minor > Fix For: 1.2.0 > > > It'd be great if Guacamole supported SAML 2.0 so it could integrate with an > organization's single sign-on (SSO) solution (especially popular platforms > like OneLogin, Okta, Bitium, etc.) > This would make authenticating to Guacamole easier for an organization's > users, and it would make organization's IT/IS admins happier being able to > apply authentication security controls to guacamole, such as password > complexity rules, two-factor authentication rules, etc. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-583) SQL Instance Strings
[ https://issues.apache.org/jira/browse/GUACAMOLE-583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-583: Fix Version/s: 1.2.0 > SQL Instance Strings > > > Key: GUACAMOLE-583 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-583 > Project: Guacamole > Issue Type: Bug > Components: guacamole-auth-jdbc-sqlserver >Affects Versions: 0.9.14 >Reporter: Martyn Jarrett >Assignee: Nick Couchman >Priority: Minor > Fix For: 1.2.0 > > > Add a property to the SQL Server module configuration to account for instance > names. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (GUACAMOLE-920) LDAP: Populate groups with membership from Directory Service.
[ https://issues.apache.org/jira/browse/GUACAMOLE-920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman closed GUACAMOLE-920. --- Resolution: Duplicate > LDAP: Populate groups with membership from Directory Service. > - > > Key: GUACAMOLE-920 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-920 > Project: Guacamole > Issue Type: Improvement > Components: guacamole-auth-ldap >Affects Versions: 1.0.0 > Environment: docker >Reporter: Nils >Priority: Major > Labels: ldap, membership > > At the moment I'm using both LDAP and MySQL with Guacamole. MySQL to store > the connection data, LDAP (without the custom schema) to perform the > authentication. > The groups however, which come in from LDAP are empty - this means that > currently I have to select each LDAP user and assign them to the LDAP group > manually. > This defeats the purpose of using LDAP groups in the first place, after all > the entire idea is that you manage your groups & users in one central > location; LDAP. > It would be very helpful if the groups are populated with the members as > defined in the respective LDAP directory, this way when a member is added to > an LDAP group, the access to the connections is automatically granted. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-920) LDAP: Populate groups with membership from Directory Service.
[ https://issues.apache.org/jira/browse/GUACAMOLE-920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17012132#comment-17012132 ] Nick Couchman commented on GUACAMOLE-920: - [~darkl0rd]: You might check out related issues GUACAMOLE-696 and GUACAMOLE-715, as these each cover some use cases that might be similar to what you're seeing. We do not - and will not - automatically populate JDBC groups with LDAP users, or vice-versa; however, we have made changes in the upcoming 1.1.0 release that should make these things work a little more as desired or expected with regarding to mapping users and groups between the different modules. Also, in a future release we will support automatic creation of JDBC users when successfully authenticated against another module (LDAP, SSO, etc.), so that may also address some concerns. if there are further issues you think are not addressed by the ones I mentioned, let us know - otherwise I will close this out as I believe what you're looking for is already covered. > LDAP: Populate groups with membership from Directory Service. > - > > Key: GUACAMOLE-920 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-920 > Project: Guacamole > Issue Type: Improvement > Components: guacamole-auth-ldap >Affects Versions: 1.0.0 > Environment: docker >Reporter: Nils >Priority: Major > Labels: ldap, membership > > At the moment I'm using both LDAP and MySQL with Guacamole. MySQL to store > the connection data, LDAP (without the custom schema) to perform the > authentication. > The groups however, which come in from LDAP are empty - this means that > currently I have to select each LDAP user and assign them to the LDAP group > manually. > This defeats the purpose of using LDAP groups in the first place, after all > the entire idea is that you manage your groups & users in one central > location; LDAP. > It would be very helpful if the groups are populated with the members as > defined in the respective LDAP directory, this way when a member is added to > an LDAP group, the access to the connections is automatically granted. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-926) Add connection form CSV
[ https://issues.apache.org/jira/browse/GUACAMOLE-926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17018439#comment-17018439 ] Nick Couchman commented on GUACAMOLE-926: - No, there is currently no way to do that directly in Guacamole; however, if you are using JDBC authentication, you can easily use SQL commands to copy in data from a CSV. As a side note, JIRA is not intended to be a support forum - please start with your questions on the mailing lists. > Add connection form CSV > --- > > Key: GUACAMOLE-926 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-926 > Project: Guacamole > Issue Type: Wish > Components: guacamole >Affects Versions: 1.0.0 >Reporter: Dinoop >Priority: Major > > Is there any options to add all servers from a CSV file or so. Adding one by > one will take too much time. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-249) Update RDP plugin support to 2.0.0 releases
[ https://issues.apache.org/jira/browse/GUACAMOLE-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17015543#comment-17015543 ] Nick Couchman commented on GUACAMOLE-249: - Way to go [~mjumper]! > Update RDP plugin support to 2.0.0 releases > --- > > Key: GUACAMOLE-249 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-249 > Project: Guacamole > Issue Type: Improvement > Components: RDP >Reporter: Simone Caronni >Assignee: Mike Jumper >Priority: Critical > Fix For: 1.1.0 > > Attachments: Screenshot_2018-09-01_14-48-56.png > > > The planets have aligned, after 2.5 years FreeRDP has released new snapshots: > https://github.com/FreeRDP/FreeRDP/releases > Thanks, > --Simone -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-249) Update RDP plugin support to 2.0.0 releases
[ https://issues.apache.org/jira/browse/GUACAMOLE-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17007527#comment-17007527 ] Nick Couchman commented on GUACAMOLE-249: - [~BenDDD]: The code will follow the normal review/commit process. When Mike is ready, he will submit a pull request. That code will be reviewed by one or more other members of the project team, then committed to the appropriate branches. Because this JIRA issue is slated for the 1.1.0 release, it will go to the staging/1.1.0 branch as well as the master branch. > Update RDP plugin support to 2.0.0 releases > --- > > Key: GUACAMOLE-249 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-249 > Project: Guacamole > Issue Type: Improvement > Components: RDP >Reporter: Simone Caronni >Assignee: Mike Jumper >Priority: Critical > Fix For: 1.1.0 > > Attachments: Screenshot_2018-09-01_14-48-56.png > > > The planets have aligned, after 2.5 years FreeRDP has released new snapshots: > https://github.com/FreeRDP/FreeRDP/releases > Thanks, > --Simone -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-913) Theme/Look and Feel Selector
[ https://issues.apache.org/jira/browse/GUACAMOLE-913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-913: Affects Version/s: (was: 1.0.0) > Theme/Look and Feel Selector > > > Key: GUACAMOLE-913 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-913 > Project: Guacamole > Issue Type: Wish > Components: guacamole-client >Reporter: Mathieu BRUNOT >Priority: Minor > Attachments: guacamole_jira_look_and_feel.png > > > I know it is currently possible to customize theme and branding of Guacamole > through extensions, but my idea is slightly different. > I think it might be nice to have a theme/look and feel selector, accessible > to all users through their settings. For instance, Guacamole could provide > the current (default) theme and a dark theme: > !guacamole_jira_look_and_feel.png! > It would also be nice to allow devs to add more selectable themes to their > Guacamole instance > So it's not really a complete rework / rebranding of Guacamole like we can > currently do, but more like a per user customizable look and feel. > Right now, I'm doing that with a custom [Stylish|https://userstyles.org/] / > [Stylus|https://add0n.com/stylus.html] theme > ([madmath03/dark-guacamole|https://github.com/madmath03/dark-guacamole]) but > having it directly in Guacamole would feel much better. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-914) LDAP sharing profiles
[
https://issues.apache.org/jira/browse/GUACAMOLE-914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman updated GUACAMOLE-914:
Affects Version/s: (was: 1.0.0)
> LDAP sharing profiles
> -
>
> Key: GUACAMOLE-914
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-914
> Project: Guacamole
> Issue Type: Wish
> Components: guacamole-auth-ldap
>Reporter: Mathieu BRUNOT
>Priority: Minor
>
> Currently, we can create connections in an LDAP but we cannot create _Sharing
> Profile(s)_.
> Sharing profile can be really useful for tech support in an organization, so
> I'm wondering if it would be possible to create a "LDAP only" property to
> setup sharing profiles. For instance, maybe we could use something like this:
> {noformat}
> guacConfigParameter: sharingProfile=myprofilename
> guacConfigParameter:
> sharingProfile=myotherprofilewhichisreadonly:read-only{noformat}
> The parameter value could be the name of the profile, with a separator used
> to specify additional parameters (read-only).
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-914) LDAP sharing profiles
[
https://issues.apache.org/jira/browse/GUACAMOLE-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17003684#comment-17003684
]
Nick Couchman commented on GUACAMOLE-914:
-
No reason this can't be done; however, I think some other items would have to
be implemented within the LDAP module, as well - like Active Connection
tracking.
> LDAP sharing profiles
> -
>
> Key: GUACAMOLE-914
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-914
> Project: Guacamole
> Issue Type: Wish
> Components: guacamole-auth-ldap
>Reporter: Mathieu BRUNOT
>Priority: Minor
>
> Currently, we can create connections in an LDAP but we cannot create _Sharing
> Profile(s)_.
> Sharing profile can be really useful for tech support in an organization, so
> I'm wondering if it would be possible to create a "LDAP only" property to
> setup sharing profiles. For instance, maybe we could use something like this:
> {noformat}
> guacConfigParameter: sharingProfile=myprofilename
> guacConfigParameter:
> sharingProfile=myotherprofilewhichisreadonly:read-only{noformat}
> The parameter value could be the name of the profile, with a separator used
> to specify additional parameters (read-only).
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-913) Theme/Look and Feel Selector
[ https://issues.apache.org/jira/browse/GUACAMOLE-913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17003683#comment-17003683 ] Nick Couchman commented on GUACAMOLE-913: - It looks like maybe this is something you have (or someone you know has) already worked on? Care to contribute whatever work you've done? > Theme/Look and Feel Selector > > > Key: GUACAMOLE-913 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-913 > Project: Guacamole > Issue Type: Wish > Components: guacamole-client >Affects Versions: 1.0.0 >Reporter: Mathieu BRUNOT >Priority: Minor > Attachments: guacamole_jira_look_and_feel.png > > > I know it is currently possible to customize theme and branding of Guacamole > through extensions, but my idea is slightly different. > I think it might be nice to have a theme/look and feel selector, accessible > to all users through their settings. For instance, Guacamole could provide > the current (default) theme and a dark theme: > !guacamole_jira_look_and_feel.png! > It would also be nice to allow devs to add more selectable themes to their > Guacamole instance > So it's not really a complete rework / rebranding of Guacamole like we can > currently do, but more like a per user customizable look and feel. > Right now, I'm doing that with a custom [Stylish|https://userstyles.org/] / > [Stylus|https://add0n.com/stylus.html] theme > ([madmath03/dark-guacamole|https://github.com/madmath03/dark-guacamole]) but > having it directly in Guacamole would feel much better. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GUACAMOLE-897) Docker support for restricting authentication to database users only
[ https://issues.apache.org/jira/browse/GUACAMOLE-897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman resolved GUACAMOLE-897. - Fix Version/s: 1.2.0 Resolution: Implemented This was implemented recently in the master branch in the following commit: https://github.com/apache/guacamole-client/commit/062edda07b7759d3a86a9a8b476d03eb8a4aeda1 > Docker support for restricting authentication to database users only > > > Key: GUACAMOLE-897 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-897 > Project: Guacamole > Issue Type: Improvement > Components: Documentation, guacamole-docker >Affects Versions: 1.0.0 >Reporter: Stephen Cluff >Priority: Minor > Fix For: 1.2.0 > > > Add support for the following properties to start.sh: > * mysql-user-required > * postgresql-user-required -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GUACAMOLE-852) Support MariaDB JDBC Driver
[ https://issues.apache.org/jira/browse/GUACAMOLE-852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman reassigned GUACAMOLE-852: --- Assignee: Nick Couchman > Support MariaDB JDBC Driver > --- > > Key: GUACAMOLE-852 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-852 > Project: Guacamole > Issue Type: Improvement > Components: guacamole-auth-jdbc-mysql >Reporter: Nick Couchman >Assignee: Nick Couchman >Priority: Minor > > The MariaDB JDBC driver implements a different class than the MySQL driver, > so some changes will need to be made to the JDBC module to support that > version of the driver. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GUACAMOLE-760) add timezone info using DB Connection string
[ https://issues.apache.org/jira/browse/GUACAMOLE-760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman reassigned GUACAMOLE-760: --- Assignee: Nick Couchman > add timezone info using DB Connection string > > > Key: GUACAMOLE-760 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-760 > Project: Guacamole > Issue Type: Improvement > Components: guacamole-client >Affects Versions: 1.0.0 >Reporter: Not Speedy >Assignee: Nick Couchman >Priority: Minor > > a recent update to with mariadb or its driver prevented guacamole client from > loading. > Cause: java.sql.SQLException: The server time zone value 'CDT' is > unrecognized or represents more than one time zone. You must configure either > the server or JDBC driver (via the serverTimezone configuration property). > loading the timezone table and setting it globally on the mariadb resolved > this, however it might be beneficial to add a system property that will set > within the connection string. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (GUACAMOLE-809) Add documentation for the REST API
[ https://issues.apache.org/jira/browse/GUACAMOLE-809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman closed GUACAMOLE-809. --- Resolution: Duplicate > Add documentation for the REST API > -- > > Key: GUACAMOLE-809 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-809 > Project: Guacamole > Issue Type: Wish > Components: Documentation >Reporter: Parth Mishra >Priority: Minor > > The Java Servlet exposes HTTP endpoints as the basis for REST API calls from > the frontend client. Currently, there is no easy way to know what these > endpoints are without viewing the source code or inspecting the network calls. > I suggest integrating some API documentation tool (e.g. Swagger) to expose > this information in a more accessible manner. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GUACAMOLE-583) SQL Instance Strings
[ https://issues.apache.org/jira/browse/GUACAMOLE-583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman reassigned GUACAMOLE-583: --- Assignee: Nick Couchman > SQL Instance Strings > > > Key: GUACAMOLE-583 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-583 > Project: Guacamole > Issue Type: Bug > Components: guacamole-auth-jdbc-sqlserver >Affects Versions: 0.9.14 >Reporter: Martyn Jarrett >Assignee: Nick Couchman >Priority: Minor > > Add a property to the SQL Server module configuration to account for instance > names. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-583) SQL Instance Strings
[ https://issues.apache.org/jira/browse/GUACAMOLE-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17003762#comment-17003762 ] Nick Couchman commented on GUACAMOLE-583: - [~Jarrett]: I've taken a stab at adding an option, "sqlserver-instance", that configures this. Any chance you could try it out? I don't have a Windows-based SQL Server at the moment to try it on... https://github.com/necouchman/guacamole-client/tree/jira/583 > SQL Instance Strings > > > Key: GUACAMOLE-583 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-583 > Project: Guacamole > Issue Type: Bug > Components: guacamole-auth-jdbc-sqlserver >Affects Versions: 0.9.14 >Reporter: Martyn Jarrett >Priority: Minor > > Add a property to the SQL Server module configuration to account for instance > names. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-604) Add support for Polish keyboard layout
[ https://issues.apache.org/jira/browse/GUACAMOLE-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17003763#comment-17003763 ] Nick Couchman commented on GUACAMOLE-604: - [~krogac]: If you have any familiarity with the layout it would be helpful if you'd be willing to take a stab at it. > Add support for Polish keyboard layout > -- > > Key: GUACAMOLE-604 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-604 > Project: Guacamole > Issue Type: New Feature > Components: RDP >Reporter: krogac >Priority: Minor > > Connection RDP not support Polish keyboard layout. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-614) Infinite loop caused by guac_iconv
[
https://issues.apache.org/jira/browse/GUACAMOLE-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17003764#comment-17003764
]
Nick Couchman commented on GUACAMOLE-614:
-
[~aiden0z]: Can you retry with 1.0.0 and see if you still have the issue?
> Infinite loop caused by guac_iconv
> --
>
> Key: GUACAMOLE-614
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-614
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole-server
>Affects Versions: 0.9.14
> Environment: Guacd 0.9.14 with docker
>Reporter: Aiden Luo
>Priority: Minor
>
> The encoding reader/writer may return zero, but the caller did not check zero
> value. That may cause the infinite loop when handle incorrect bytes.
> See the line starts with {color:#FF}/*** {color}.
> {code:java}
> int guac_iconv(guac_iconv_read* reader, const char** input, int in_remaining,
> guac_iconv_write* writer, char** output, int out_remaining) {
> while (in_remaining > 0 && out_remaining > 0) {
> int value;
> const char* read_start;
> char* write_start;
> /* Read character */
> read_start = *input;
> /*** reader may return value and not change input ***/
> value = reader(input, in_remaining);
> in_remaining -= *input - read_start;
> /* Write character */
> write_start = *output;
> /*** writer may return value and not change output ***/
> writer(output, out_remaining, value);
> out_remaining -= *output - write_start;
> /* Stop if null terminator reached */
> if (value == 0)
> return 1;
> }
> /* Null terminator not reached */
> return 0;
> }
> {code}
>
> *Analysis procedure*
> *1. Find problem thread*
> {code:java}
> [root@jettydocker2 /]# ps -ef
> UID PID PPID C STIME TTY TIME CMD
> root 1 0 0 01:35 ? 00:00:40 /usr/local/sbin/guacd -b 0.0.0.0 -f
> root 464 1 0 02:51 ? 00:00:17 /usr/local/sbin/guacd -b 0.0.0.0 -f
> root 615 1 96 03:12 ? 01:23:39 /usr/local/sbin/guacd -b 0.0.0.0 -f
> root 703 1 0 03:38 ? 00:00:00 /usr/local/sbin/guacd -b 0.0.0.0 -f
> root 712 1 0 03:45 ? 00:00:15 /usr/local/sbin/guacd -b 0.0.0.0 -f
> root 728 1 0 04:01 ? 00:00:02 /usr/local/sbin/guacd -b 0.0.0.0 -f
> root 735 0 0 04:39 ? 00:00:00 bash
> root 747 735 0 04:39 ? 00:00:00 ps -ef
> [root@jettydocker2 /]# top -b -H -p 615
> top - 04:40:08 up 48 days, 2:56, 0 users, load average: 1.01, 1.11, 1.19
> Threads: 3 total, 1 running, 2 sleeping, 0 stopped, 0 zombie
> %Cpu(s): 25.4 us, 0.0 sy, 0.0 ni, 74.6 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
> KiB Mem : 8175596 total, 2269700 free, 1883596 used, 4022300 buff/cache
> KiB Swap: 0 total, 0 free, 0 used. 5914664 avail Mem
> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
> 619 root 20 0 1861008 23848 3444 R 99.9 0.3 83:56.87 guacd
> 615 root 20 0 1861008 23848 3444 S 0.0 0.3 0:00.00 guacd
> 621 root 20 0 1861008 23848 3444 S 0.0 0.3 0:00.02 guacd
> {code}
>
> *2. GDB anaylsis*
> {code:java}
> [root@jettydocker2 /]# gdb /usr/local/sbin/guacd 615
> GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-110.el7
> Copyright (C) 2013 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law. Type "show copying"
> and "show
>
> (gdb) info threads
> Id Target Id Frame
> 3 Thread 0x7efffeffd700 (LWP 619) "guacd" guac_iconv (reader=0x7f00683e22fa
> , input=0x7efffefbc638, in_remaining=2,
> writer=0x7f00683e240f , output=0x7efffefbc630,
> out_remaining=1) at iconv.c:74
> 2 Thread 0x7f0059ffb700 (LWP 621) "guacd" 0x7f00721f9f3d in nanosleep ()
> from /lib64/libpthread.so.0
> * 1 Thread 0x7f0043fff700 (LWP 615) "guacd" 0x7f00721f3f97 in
> pthread_join () from /lib64/libpthread.so.0
> (gdb) t 3
> [Switching to thread 3 (Thread 0x7efffeffd700 (LWP 619))]
> #0 guac_iconv (reader=0x7f00683e22fa , input=0x7efffefbc638,
> in_remaining=2, writer=0x7f00683e240f ,
> output=0x7efffefbc630, out_remaining=1) at iconv.c:74
> 74 read_start = *input;
> (gdb) bt
> #0 guac_iconv (reader=0x7f00683e22fa , input=0x7efffefbc638,
> in_remaining=2, writer=0x7f00683e240f ,
> output=0x7efffefbc630, out_remaining=1) at iconv.c:74
> #1 0x7f00683df11d in guac_vnc_cut_text (client=0x7f007302e010,
> text=0x7f00600019d0 " #", , textlen=5) at
> clipboard.c:135
> #2 0x7f00681c97c7 in HandleRFBServerMessage () from
> /lib64/libvncclient.so.0
> #3 0x7f00683e0c97 in guac_vnc_client_thread (data=0x7f005c00aee0) at
> vnc.c:350
> #4 0x7f00721f2e25 in start_thread () from /lib64/libpthread.so.0
> #5 0x7f0070aeabad in clone () from /lib64/libc.so.6
> (gdb) f 0
> #0 guac_iconv (reader=0x7f00683e22fa , input=0x7efffefbc638,
> in_remaining=2, writer=0x7f00683e240f ,
> output=0x7efffefbc630, out_remaining=1) at iconv.c:79
> 79 write_start = *output;
> (gdb) n [18/1979]
> 80
[jira] [Updated] (GUACAMOLE-882) Add Belgian Dutch Keyboard Support
[ https://issues.apache.org/jira/browse/GUACAMOLE-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-882: Summary: Add Belgian Dutch Keyboard Support (was: Create keymap file) > Add Belgian Dutch Keyboard Support > -- > > Key: GUACAMOLE-882 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-882 > Project: Guacamole > Issue Type: Improvement > Components: Documentation, guacamole-ext, RDP >Affects Versions: 1.0.0 > Environment: debian >Reporter: Lesley Persyn >Priority: Minor > Labels: RDP, keyboard, keymap, layout > > With US keyboard systems no problem. But with "Belgium Dutch keyboard" > (point, not french) still an issue. (if i don't select a keyboard and set the > remote server to US then it works fine but this should work seamlessly) > What are the best practices to create a .keymap file? How to read out the > keyboard keys? > I can do it myself but cannot find where to start. > The current working .keymaps are here: > [github|https://github.com/apache/guacamole-server/tree/master/src/protocols/rdp/keymaps] > And i tried to search for a solution but still doesn't find an anwer in the > quite a lot of search results on different sites/mailinglists. > Best regards. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-903) Improved Chinese internationalization support
[ https://issues.apache.org/jira/browse/GUACAMOLE-903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-903: Affects Version/s: (was: 1.1.0) 1.0.0 > Improved Chinese internationalization support > - > > Key: GUACAMOLE-903 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-903 > Project: Guacamole > Issue Type: Improvement > Components: guacamole-auth-jdbc, guacamole-auth-jdbc-mysql, > guacamole-client >Affects Versions: 1.0.0 >Reporter: XYUU >Priority: Minor > > Due to the missing content of Chinese internationalization in the new > version, I used English as a template to complete this improvement. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-903) Improved Chinese internationalization support
[ https://issues.apache.org/jira/browse/GUACAMOLE-903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-903: Priority: Minor (was: Major) > Improved Chinese internationalization support > - > > Key: GUACAMOLE-903 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-903 > Project: Guacamole > Issue Type: Improvement > Components: guacamole-auth-jdbc, guacamole-auth-jdbc-mysql, > guacamole-client >Affects Versions: 1.1.0 >Reporter: XYUU >Priority: Minor > > Due to the missing content of Chinese internationalization in the new > version, I used English as a template to complete this improvement. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-903) Improved Chinese internationalization support
[ https://issues.apache.org/jira/browse/GUACAMOLE-903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-903: Fix Version/s: (was: 1.1.0) > Improved Chinese internationalization support > - > > Key: GUACAMOLE-903 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-903 > Project: Guacamole > Issue Type: Improvement > Components: guacamole-auth-jdbc, guacamole-auth-jdbc-mysql, > guacamole-client >Affects Versions: 1.1.0 >Reporter: XYUU >Priority: Major > > Due to the missing content of Chinese internationalization in the new > version, I used English as a template to complete this improvement. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-801) Capslock / Shift key passthrough is strange over dual RDP
[ https://issues.apache.org/jira/browse/GUACAMOLE-801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17003086#comment-17003086 ] Nick Couchman commented on GUACAMOLE-801: - Might possibly be related to GUACAMOLE-859? > Capslock / Shift key passthrough is strange over dual RDP > - > > Key: GUACAMOLE-801 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-801 > Project: Guacamole > Issue Type: Bug >Reporter: Robert McGunsterson >Priority: Minor > Labels: input > > I am using guac to get home. > From the guac UI, I open a full screen RDP to my desktop. > From my home desktop, I am then opening /another/ RDP session within my > existing RDP session. > > When I do this, typing out stuff comes out very strange in relation to the > shift key and this seems a consistent fault, specifically causing issues with > passwords utilising the shift key. > > See text below > > thIs is mE TypIng With thE CApS locK ON, iN AN RdP sESsIon > ThiS iS Me HOLdiNg dowN thE riGHT shIFT kEY > THIS IS ME HOLDING DOWN THE LEFT SHIFT KEY > > I do not know the cause of this, it's a pretty obscure problem, but it's > specific to guac. It's like the way guac forwards a shift key is not > persistent? > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GUACAMOLE-550) Add autocomplete attributes to inputs
[ https://issues.apache.org/jira/browse/GUACAMOLE-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman reassigned GUACAMOLE-550: --- Assignee: Nick Couchman > Add autocomplete attributes to inputs > - > > Key: GUACAMOLE-550 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-550 > Project: Guacamole > Issue Type: New Feature >Reporter: Nick Couchman >Assignee: Nick Couchman >Priority: Trivial > Attachments: chrome-autocomplete-warning.png > > > I see this suggestion show up in the Chrome Developer Tools window > periodically, and figured I'd create a JIRA issue for it. We should add > autocomplete to the various input fields to control whether or not we expect > the browsers to keep track of information for those fields, including storing > credentials within the browser's password save function if desired. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GUACAMOLE-557) Transcript/video viewer
[ https://issues.apache.org/jira/browse/GUACAMOLE-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman resolved GUACAMOLE-557. - Resolution: Implemented > Transcript/video viewer > --- > > Key: GUACAMOLE-557 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-557 > Project: Guacamole > Issue Type: Improvement > Components: guacamole-client >Reporter: Guillaume VANNIER >Priority: Trivial > > I suggest the avaibility for admin users to directly view the session while > the user is connected from the session list and after the user is connected > from the history list. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-249) Update RDP plugin support to 2.0.0 releases
[ https://issues.apache.org/jira/browse/GUACAMOLE-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17008350#comment-17008350 ] Nick Couchman commented on GUACAMOLE-249: - I've begun reviewing the code. If any of the other project members can jump in and review that would probably be good, too. > Update RDP plugin support to 2.0.0 releases > --- > > Key: GUACAMOLE-249 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-249 > Project: Guacamole > Issue Type: Improvement > Components: RDP >Reporter: Simone Caronni >Assignee: Mike Jumper >Priority: Critical > Fix For: 1.1.0 > > Attachments: Screenshot_2018-09-01_14-48-56.png > > > The planets have aligned, after 2.5 years FreeRDP has released new snapshots: > https://github.com/FreeRDP/FreeRDP/releases > Thanks, > --Simone -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-125) Sometimes session is not initialised on Full screen
[ https://issues.apache.org/jira/browse/GUACAMOLE-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17009939#comment-17009939 ] Nick Couchman commented on GUACAMOLE-125: - This was actually fixed in the unreleased FreeRDP 1.2 version, I believe, but I was trying to resolve it with earlier FreeRDP versions. I'm more than happy to cross it off the list! > Sometimes session is not initialised on Full screen > > > Key: GUACAMOLE-125 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-125 > Project: Guacamole > Issue Type: Bug >Affects Versions: 0.9.9, 0.9.10-incubating > Environment: Guacamole running on Debian 8.6 > Forwarding a windows 2012 R2 session >Reporter: Frank Giroud >Priority: Minor > Fix For: 1.1.0 > > Attachments: fj1.png, fj2.png, fj3.png, fj4.png, fj5.png, fj6.png, > notepad_size_limit.jpg, notepad_size_limit_detail.jpg > > > Sometimes after logging in (which happens to be Full scren) the windows > session or the RemoteApp is not launched in full screen. > In fact it behaves like there were a pseudo-resolution smaller than the > required one. > The browser (Chrome is open in a 1920*1200) but the screen displayed is > locked to something like 1024*768 or so. > When you click on the Fullscreen button. It open and let a black screen all > around in the web browser. . > -The behavior is the same if you start a windows session , the windows > desktop displayed in the web browser is in a 'smaller display' and what > remains is black.- Haven't succeed to reproduce after all > I have succeeded to find a way to reproduce the behavior "kind of" more often. > In my example i configure notepad++ to be a remoteapp (launch by ||notepad in > guacamole ) > # Launch a session through Guacamole => No probleme guacamole can be set in > fullscreen (on all the browser window) > # Unmaximized the application > # Ctrl-Shift-Alt menu => Disconnect > # On the guacamole option menu (3 choices) => Reconnect > # The result => my screenshot -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-984) RDP Sessions closes after 2'32"
[ https://issues.apache.org/jira/browse/GUACAMOLE-984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17056852#comment-17056852 ] Nick Couchman commented on GUACAMOLE-984: - Are you using a RDP desktop, or are you using RemoteApp (RAIL)? > RDP Sessions closes after 2'32" > --- > > Key: GUACAMOLE-984 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-984 > Project: Guacamole > Issue Type: Bug > Components: guacamole-server >Affects Versions: 1.1.0 > Environment: Frontend: Linux Debian 9 + Tomcat 8 + openjdk 1.8.0_242 > Backend: Linux Debian 9 >Reporter: Saxa Egea >Priority: Major > Fix For: 1.0.0 > > > When using guacd 1.1 I can connect to any RDP session. > But, after 2'32' the session closes automatically. > There is a frontend with the guacamole-client (WAR) and a backend (guacd). I > can see in the logs: > Mar 10 14:15:48 HOSTNAME-BE guacd[9413]: Security mode: RDP > Mar 10 14:15:48 HOSTNAME-BE guacd[9413]: Parameter "client-name" omitted. > Using default value of "Guacamole RDP". > Mar 10 14:15:49 HOSTNAME-BE guacd[9413]: Clipboard data received. Reporting > availability of clipboard data to RDP server. > Mar 10 14:15:49 HOSTNAME-BE guacd[9413]: Clipboard data received. Reporting > availability of clipboard data to RDP server. > Mar 10 14:16:15 HOSTNAME-BE guacd[9413]: Clipboard data received. Reporting > availability of clipboard data to RDP server. > Mar 10 14:18:09 HOSTNAME-BE guacd[9413]: Clipboard data received. Reporting > availability of clipboard data to RDP server. > Mar 10 14:18:20 HOSTNAME-BE guacd[9413]: RDP server closed connection: > Manually logged off. > Mar 10 14:18:20 HOSTNAME-BE guacd[9413]: Internal RDP client disconnected > > Between the backend and the RDP Server the is no Firewall. > > Finnally I get back to guacd 1.0.0 and everything works as expected. Nothing > more changed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (GUACAMOLE-984) RDP Sessions closes after 2'32"
[ https://issues.apache.org/jira/browse/GUACAMOLE-984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman closed GUACAMOLE-984. --- Resolution: Duplicate In that case, this is a duplicate of GUACAMOLE-978, and the fix has already been applied to the code in git, and will be released in 1.2.0. > RDP Sessions closes after 2'32" > --- > > Key: GUACAMOLE-984 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-984 > Project: Guacamole > Issue Type: Bug > Components: guacamole-server >Affects Versions: 1.1.0 > Environment: Frontend: Linux Debian 9 + Tomcat 8 + openjdk 1.8.0_242 > Backend: Linux Debian 9 >Reporter: Saxa Egea >Priority: Major > Fix For: 1.0.0 > > > When using guacd 1.1 I can connect to any RDP session. > But, after 2'32' the session closes automatically. > There is a frontend with the guacamole-client (WAR) and a backend (guacd). I > can see in the logs: > Mar 10 14:15:48 HOSTNAME-BE guacd[9413]: Security mode: RDP > Mar 10 14:15:48 HOSTNAME-BE guacd[9413]: Parameter "client-name" omitted. > Using default value of "Guacamole RDP". > Mar 10 14:15:49 HOSTNAME-BE guacd[9413]: Clipboard data received. Reporting > availability of clipboard data to RDP server. > Mar 10 14:15:49 HOSTNAME-BE guacd[9413]: Clipboard data received. Reporting > availability of clipboard data to RDP server. > Mar 10 14:16:15 HOSTNAME-BE guacd[9413]: Clipboard data received. Reporting > availability of clipboard data to RDP server. > Mar 10 14:18:09 HOSTNAME-BE guacd[9413]: Clipboard data received. Reporting > availability of clipboard data to RDP server. > Mar 10 14:18:20 HOSTNAME-BE guacd[9413]: RDP server closed connection: > Manually logged off. > Mar 10 14:18:20 HOSTNAME-BE guacd[9413]: Internal RDP client disconnected > > Between the backend and the RDP Server the is no Firewall. > > Finnally I get back to guacd 1.0.0 and everything works as expected. Nothing > more changed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
