[jira] [Commented] (GUACAMOLE-96) Two factor authentication with Google Authenticator
[ https://issues.apache.org/jira/browse/GUACAMOLE-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16495983#comment-16495983 ] Todd James commented on GUACAMOLE-96: - This seems to be working pretty well, but I'd love to see an additional property: a configurable property (say "totp-disable-enrollment") that allows the administrator to disable TOTP enrollment via Guacamole. Suppose a user is logging into an internet-exposed instance of Guacamole for the first time. They will be prompted to enroll in 2FA with TOTP. If the person that logged in is not the actual user (phished password, for example), they will still gain control of the Guacamole account. This almost defeats the purpose of 2FA for first-time users. I would love to provide my users with an alternative TOTP enrollment method (which may tie into other systems, as well as modify the Guacamole database with the TOTP secret). If such an option was to be set to false by the administrator, the user might be prompted with a custom message (as a second property, say "totp-disable-enrollment-message"). Any thoughts on this? Should I open a separate issue at this point? I'm willing to write the code myself, but I'd like to hear whether or not this would be a welcomed addition. > Two factor authentication with Google Authenticator > --- > > Key: GUACAMOLE-96 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-96 > Project: Guacamole > Issue Type: New Feature > Components: Documentation, guacamole-client >Reporter: L.J. van Ruiten >Assignee: Michael Jumper >Priority: Major > Fix For: 1.0.0 > > Attachments: guacamole-auth-totp-01-enroll-01-details-hidden.png, > guacamole-auth-totp-01-enroll-02-details-shown.png, > guacamole-auth-totp-01-enroll.png, guacamole-auth-totp-02-verify.png > > > We have a few critical systems that are accessible through Guacamole and we > have had some clients requesting a safer way to login. Two factor > authentication is probably the best and easiest way to improve on the current > username/password login, and I can imagine that this is something that other > companies using Guacamole would also be interesting in this feature. > I already did some tinkering myself and I found that Google Auhtenticator is > simple to use, does not require any configuration (like you would with SMS > codes) easy to implement and the "client" side of the authentication (the > part that generates the codes) is easily integrated into existing apps. > So far I have got Google Authenticator "kinda working". What I did is: > - Started with guacamole-auth-jdbc as base > - Added a secret key to a user account that is randomly generated upon > creation. Also added a boolean field to indicate wether TFA is required for > loggin in. > - Used the GuacamoleInsufficientCredentialsException to redirect the user the > a second screen asking for a TFA code after loggin in with the username and > password. > However as said before this only "kinda works" because: > I have only gotten the TFA enable button to appear in the user's managing > page, so it can only be enabled by administrators and that's also where I put > the secret key shows up, so users can't find it themself. > For as far as I could find the previous point cannot be done with just the > guacamole-ext api. Even with the new API that enables you to insert HTML > parts, you would also need an API endpoint to provide the secret key or > ideally generate a QR code that Google Auhtenticator can read to bind a > device to the account (I would like it to appear in the user's preference > page). > So in summary if other people are interested I would be willing to contribute > this, but I would need some directions and I have a few questions: > - Am I right that it is currently not possible to add an API endpoint just > using guacamole-ext to provide the QR codes? > - What would be the way to implement this? Personally I thought that adding > these options to the user's page would be the easiest. > - Is this a feature you would like me to work on and contribute? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (GUACAMOLE-441) guacd ssh plugin segfault when copy text to clipboard
[
https://issues.apache.org/jira/browse/GUACAMOLE-441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16495480#comment-16495480
]
Nick Couchman edited comment on GUACAMOLE-441 at 5/30/18 5:44 PM:
--
I'm able to reproduce this using the method you suggested - hold left mouse
button down while scrolling to select data from several parts of the screen. I
get the same "double free or corruption" error.
Here's my backtrace from guacd, built from one of the git repos (reasonably
up-to-date):
{code}
*** Error in `/opt/guacssh/sbin/guacd': double free or corruption (!prev):
0x7f300c000ba0 ***
=== Backtrace: =
/lib64/libc.so.6(+0x7c619)[0x7f302c192619]
/opt/guacssh/lib/libguac-client-ssh.so(guac_terminal_send_mouse+0x1ae)[0x7f30261414ae]
/opt/guacssh/lib/libguac-client-ssh.so(guac_ssh_user_mouse_handler+0x46)[0x7f3026135f36]
/opt/guacssh/lib/libguac.so.12(+0xdec9)[0x7f302e4e1ec9]
/lib64/libpthread.so.0(+0x7e25)[0x7f302d913e25]
/lib64/libc.so.6(clone+0x6d)[0x7f302c20e34d]
{code}
was (Author: nick.couch...@yahoo.com):
I'm able to reproduce this using the method you suggested - hold left mouse
button down while scrolling to select data from several parts of the screen. I
get the same "double free or corruption" error.
> guacd ssh plugin segfault when copy text to clipboard
> -
>
> Key: GUACAMOLE-441
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-441
> Project: Guacamole
> Issue Type: Bug
> Components: SSH, Terminal
>Affects Versions: 0.9.13-incubating, 0.9.14, 1.0.0
> Environment: GNU Linux x86_64
>Reporter: James He
>Priority: Minor
>
> This segfault can be replicated each time when do the below steps.
> - Login to any SSH server from guacamole.
> - Try a command with much output e.g. "ps aux".
> - Select the output text of the above command.
> - SSH connection will be terminated immediately.
> - Core dump of guacd will be generated.
> {code:none}
> Core was generated by `/sbin/guacd -f'.
> Program terminated with signal SIGABRT, Aborted.
> #0 0x2bca8437 in raise () from /lib64/libc.so.6
> (gdb) bt
> #0 0x2bca8437 in raise () from /lib64/libc.so.6
> #1 0x2bca9818 in abort () from /lib64/libc.so.6
> #2 0x2bce6574 in ?? () from /lib64/libc.so.6
> #3 0x2bcebdae in ?? () from /lib64/libc.so.6
> #4 0x2bcecab6 in ?? () from /lib64/libc.so.6
> #5 0x2db6b160 in __guac_terminal_send_mouse (term=0x2aaab401bf60,
> user=0x2aaab0002920, x=703, y=921,
> mask=0) at terminal.c:1715
> #6 0x2db6b2b5 in guac_terminal_send_mouse (term=0x2aaab401bf60,
> user=0x2aaab0002920, x=703, y=921, mask=0)
> at terminal.c:1753
> #7 0x2db5c532 in guac_ssh_user_mouse_handler (user=0x2aaab0002920,
> x=703, y=921, mask=0) at input.c:41
> #8 0x2af4dc2e in __guac_handle_mouse (user=0x2aaab0002920, argc=3,
> argv=0x2aaab000adc0)
> at user-handlers.c:134
> #9 0x2af4d3ea in guac_user_handle_instruction (user=0x2aaab0002920,
> opcode=0x2aaab0012b29 "mouse", argc=3,
> argv=0x2aaab000adc0) at user.c:178
> #10 0x004055e7 in guacd_user_input_thread (data=0x2f353d20) at
> user.c:127
> #11 0x2b8521a4 in start_thread (arg=0x2aab0d029700) at
> pthread_create.c:309
> #12 0x2bd5965d in clone () from /lib64/libc.so.6
> (gdb) frame 5
> #5 0x2db6b160 in __guac_terminal_send_mouse (term=0x2aaab401bf60,
> user=0x2aaab0002920, x=703, y=921,
> mask=0) at terminal.c:1715
> warning: Source file is more recent than executable.
> 1715guac_common_clipboard_reset(term->clipboard,
> "text/plain");
> (gdb) p term->clipboard->length
> $6 = 9500
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GUACAMOLE-441) guacd ssh plugin segfault when copy text to clipboard
[
https://issues.apache.org/jira/browse/GUACAMOLE-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman updated GUACAMOLE-441:
Component/s: Terminal
> guacd ssh plugin segfault when copy text to clipboard
> -
>
> Key: GUACAMOLE-441
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-441
> Project: Guacamole
> Issue Type: Bug
> Components: SSH, Terminal
>Affects Versions: 0.9.13-incubating, 0.9.14, 1.0.0
> Environment: GNU Linux x86_64
>Reporter: James He
>Priority: Minor
>
> This segfault can be replicated each time when do the below steps.
> - Login to any SSH server from guacamole.
> - Try a command with much output e.g. "ps aux".
> - Select the output text of the above command.
> - SSH connection will be terminated immediately.
> - Core dump of guacd will be generated.
> {code:none}
> Core was generated by `/sbin/guacd -f'.
> Program terminated with signal SIGABRT, Aborted.
> #0 0x2bca8437 in raise () from /lib64/libc.so.6
> (gdb) bt
> #0 0x2bca8437 in raise () from /lib64/libc.so.6
> #1 0x2bca9818 in abort () from /lib64/libc.so.6
> #2 0x2bce6574 in ?? () from /lib64/libc.so.6
> #3 0x2bcebdae in ?? () from /lib64/libc.so.6
> #4 0x2bcecab6 in ?? () from /lib64/libc.so.6
> #5 0x2db6b160 in __guac_terminal_send_mouse (term=0x2aaab401bf60,
> user=0x2aaab0002920, x=703, y=921,
> mask=0) at terminal.c:1715
> #6 0x2db6b2b5 in guac_terminal_send_mouse (term=0x2aaab401bf60,
> user=0x2aaab0002920, x=703, y=921, mask=0)
> at terminal.c:1753
> #7 0x2db5c532 in guac_ssh_user_mouse_handler (user=0x2aaab0002920,
> x=703, y=921, mask=0) at input.c:41
> #8 0x2af4dc2e in __guac_handle_mouse (user=0x2aaab0002920, argc=3,
> argv=0x2aaab000adc0)
> at user-handlers.c:134
> #9 0x2af4d3ea in guac_user_handle_instruction (user=0x2aaab0002920,
> opcode=0x2aaab0012b29 "mouse", argc=3,
> argv=0x2aaab000adc0) at user.c:178
> #10 0x004055e7 in guacd_user_input_thread (data=0x2f353d20) at
> user.c:127
> #11 0x2b8521a4 in start_thread (arg=0x2aab0d029700) at
> pthread_create.c:309
> #12 0x2bd5965d in clone () from /lib64/libc.so.6
> (gdb) frame 5
> #5 0x2db6b160 in __guac_terminal_send_mouse (term=0x2aaab401bf60,
> user=0x2aaab0002920, x=703, y=921,
> mask=0) at terminal.c:1715
> warning: Source file is more recent than executable.
> 1715guac_common_clipboard_reset(term->clipboard,
> "text/plain");
> (gdb) p term->clipboard->length
> $6 = 9500
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GUACAMOLE-441) guacd ssh plugin segfault when copy text to clipboard
[
https://issues.apache.org/jira/browse/GUACAMOLE-441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16495480#comment-16495480
]
Nick Couchman commented on GUACAMOLE-441:
-
I'm able to reproduce this using the method you suggested - hold left mouse
button down while scrolling to select data from several parts of the screen. I
get the same "double free or corruption" error.
> guacd ssh plugin segfault when copy text to clipboard
> -
>
> Key: GUACAMOLE-441
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-441
> Project: Guacamole
> Issue Type: Bug
> Components: SSH
>Affects Versions: 0.9.13-incubating, 0.9.14, 1.0.0
> Environment: GNU Linux x86_64
>Reporter: James He
>Priority: Minor
>
> This segfault can be replicated each time when do the below steps.
> - Login to any SSH server from guacamole.
> - Try a command with much output e.g. "ps aux".
> - Select the output text of the above command.
> - SSH connection will be terminated immediately.
> - Core dump of guacd will be generated.
> {code:none}
> Core was generated by `/sbin/guacd -f'.
> Program terminated with signal SIGABRT, Aborted.
> #0 0x2bca8437 in raise () from /lib64/libc.so.6
> (gdb) bt
> #0 0x2bca8437 in raise () from /lib64/libc.so.6
> #1 0x2bca9818 in abort () from /lib64/libc.so.6
> #2 0x2bce6574 in ?? () from /lib64/libc.so.6
> #3 0x2bcebdae in ?? () from /lib64/libc.so.6
> #4 0x2bcecab6 in ?? () from /lib64/libc.so.6
> #5 0x2db6b160 in __guac_terminal_send_mouse (term=0x2aaab401bf60,
> user=0x2aaab0002920, x=703, y=921,
> mask=0) at terminal.c:1715
> #6 0x2db6b2b5 in guac_terminal_send_mouse (term=0x2aaab401bf60,
> user=0x2aaab0002920, x=703, y=921, mask=0)
> at terminal.c:1753
> #7 0x2db5c532 in guac_ssh_user_mouse_handler (user=0x2aaab0002920,
> x=703, y=921, mask=0) at input.c:41
> #8 0x2af4dc2e in __guac_handle_mouse (user=0x2aaab0002920, argc=3,
> argv=0x2aaab000adc0)
> at user-handlers.c:134
> #9 0x2af4d3ea in guac_user_handle_instruction (user=0x2aaab0002920,
> opcode=0x2aaab0012b29 "mouse", argc=3,
> argv=0x2aaab000adc0) at user.c:178
> #10 0x004055e7 in guacd_user_input_thread (data=0x2f353d20) at
> user.c:127
> #11 0x2b8521a4 in start_thread (arg=0x2aab0d029700) at
> pthread_create.c:309
> #12 0x2bd5965d in clone () from /lib64/libc.so.6
> (gdb) frame 5
> #5 0x2db6b160 in __guac_terminal_send_mouse (term=0x2aaab401bf60,
> user=0x2aaab0002920, x=703, y=921,
> mask=0) at terminal.c:1715
> warning: Source file is more recent than executable.
> 1715guac_common_clipboard_reset(term->clipboard,
> "text/plain");
> (gdb) p term->clipboard->length
> $6 = 9500
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GUACAMOLE-441) guacd ssh plugin segfault when copy text to clipboard
[
https://issues.apache.org/jira/browse/GUACAMOLE-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman updated GUACAMOLE-441:
Affects Version/s: 1.0.0
0.9.14
> guacd ssh plugin segfault when copy text to clipboard
> -
>
> Key: GUACAMOLE-441
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-441
> Project: Guacamole
> Issue Type: Bug
> Components: SSH
>Affects Versions: 0.9.13-incubating, 0.9.14, 1.0.0
> Environment: GNU Linux x86_64
>Reporter: James He
>Priority: Minor
>
> This segfault can be replicated each time when do the below steps.
> - Login to any SSH server from guacamole.
> - Try a command with much output e.g. "ps aux".
> - Select the output text of the above command.
> - SSH connection will be terminated immediately.
> - Core dump of guacd will be generated.
> {code:none}
> Core was generated by `/sbin/guacd -f'.
> Program terminated with signal SIGABRT, Aborted.
> #0 0x2bca8437 in raise () from /lib64/libc.so.6
> (gdb) bt
> #0 0x2bca8437 in raise () from /lib64/libc.so.6
> #1 0x2bca9818 in abort () from /lib64/libc.so.6
> #2 0x2bce6574 in ?? () from /lib64/libc.so.6
> #3 0x2bcebdae in ?? () from /lib64/libc.so.6
> #4 0x2bcecab6 in ?? () from /lib64/libc.so.6
> #5 0x2db6b160 in __guac_terminal_send_mouse (term=0x2aaab401bf60,
> user=0x2aaab0002920, x=703, y=921,
> mask=0) at terminal.c:1715
> #6 0x2db6b2b5 in guac_terminal_send_mouse (term=0x2aaab401bf60,
> user=0x2aaab0002920, x=703, y=921, mask=0)
> at terminal.c:1753
> #7 0x2db5c532 in guac_ssh_user_mouse_handler (user=0x2aaab0002920,
> x=703, y=921, mask=0) at input.c:41
> #8 0x2af4dc2e in __guac_handle_mouse (user=0x2aaab0002920, argc=3,
> argv=0x2aaab000adc0)
> at user-handlers.c:134
> #9 0x2af4d3ea in guac_user_handle_instruction (user=0x2aaab0002920,
> opcode=0x2aaab0012b29 "mouse", argc=3,
> argv=0x2aaab000adc0) at user.c:178
> #10 0x004055e7 in guacd_user_input_thread (data=0x2f353d20) at
> user.c:127
> #11 0x2b8521a4 in start_thread (arg=0x2aab0d029700) at
> pthread_create.c:309
> #12 0x2bd5965d in clone () from /lib64/libc.so.6
> (gdb) frame 5
> #5 0x2db6b160 in __guac_terminal_send_mouse (term=0x2aaab401bf60,
> user=0x2aaab0002920, x=703, y=921,
> mask=0) at terminal.c:1715
> warning: Source file is more recent than executable.
> 1715guac_common_clipboard_reset(term->clipboard,
> "text/plain");
> (gdb) p term->clipboard->length
> $6 = 9500
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (GUACAMOLE-555) recorded file is locked by default.
[ https://issues.apache.org/jira/browse/GUACAMOLE-555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman closed GUACAMOLE-555. --- Resolution: Invalid Closing as invalid - this appears to be either a permission issues or that the file was actually locked during recording. > recorded file is locked by default. > --- > > Key: GUACAMOLE-555 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-555 > Project: Guacamole > Issue Type: Improvement > Components: guacamole >Affects Versions: 0.9.14 >Reporter: Manjeeta Raj >Priority: Minor > > The session recording creates a locked recorded file. Is there any way to > create unlocked file. > If not, can we have this feature implemented. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GUACAMOLE-567) Network connection problem acknowledgement/feedback
[
https://issues.apache.org/jira/browse/GUACAMOLE-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16495262#comment-16495262
]
emma commented on GUACAMOLE-567:
Hi,
today i just build from github the release 1.0.0 with new improvements,
patches, bug fixes on my Ubuntu Server 16.04.3 LTS (GNU/Linux 4.4.0-62-generic
x86_64) with Tomcat8 and that's it, nothing more, nothing less.
This server is my test server and previously i was running github 1.0.0.
version builded March the 3rd.
So i test connection on my differents servers (2003/2008/2012) and for most of
them i notice i get during the first connection the message with logo about
"Network connection unstable" despite the fact i am testing on my local
network, not on remote through internet.
Then once im connected and Windows session is opened, i disconnect from my
Windows server and the closing session seems to hang few seconds then i get
connection error screen.
!Network_Connection1.png!
!Network_Connection2.png!
If i reconnect on the same server, this kind of message disappeared and
disconnection seems to works fine on 2003 and 2008 servers. On my 2012 server i
almost always get "Network connection unstable" and "error connection" message
on disconnect !
It looks like, if there is a long time you didn't initiate a connection on a
server, then you get "network connection unstable" message with logo, once you
made at least one successful connection then disconnect works normally without
any "connection error" screen, except on 2012 server where i almost always
encounter this "problem" and message.
Or it is like at the very first connection on a server you get message during
disconnection process
!Network_Connection4.png!
then you get the message
!Network_Connection5.png!
If i wait or click Reconnect and then cancel without logging for example, the
disconnection works fine
!Network_Connection6.png!
Made another test with a 2003 Server and first time i am connecting on with
that new version of guacamole, then i get the same behavior
!Network_Connection7.png!
!Network_Connection8.png!
It is just a test but before that "Network connection problem
acknowledgement/feedback" case, i never have this behavior during disconnection
screen !
Don't know if other testers can confirm that fact ?
Many thanks for your great job, Guacamole rocks !
> Network connection problem acknowledgement/feedback
> ---
>
> Key: GUACAMOLE-567
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-567
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-client, guacamole-common-js
>Reporter: Michael Jumper
>Assignee: Michael Jumper
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: Network_Connection1.png, Network_Connection2.png,
> Network_Connection4.png, Network_Connection5.png, Network_Connection6.png,
> Network_Connection7.png, Network_Connection8.png,
> image-2018-05-30-16-26-15-928.png, internal-error.png
>
>
> {panel:bgColor=#EE}
> *The description of this issue was copied from
> [GUAC-1055|https://jira.glyptodon.org/browse/GUAC-1055], an issue in the JIRA
> instance used by the Guacamole project prior to its move to the ASF.*
> Comments, attachments, related issues, and history from prior to acceptance
> *may not have been copied* and can be found instead at the original issue.
> {panel}
> When Guacamole detects that the network connection is slow or hanging, it
> should acknowledge this and unobtrusively notify the user. Lacking such
> notification, slow networks or remote desktop failures look like Guacamole
> bugs, and are frequently reported as such.
> Further, the total lack of a network connection is handled within JavaScript,
> but the error code is not recognized by the Guacamole client. The unknown
> error is thus translated into a generic "An internal error has occurred ..."
> message, which is obviously incorrect:
> !internal-error.png|width=320!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GUACAMOLE-567) Network connection problem acknowledgement/feedback
[
https://issues.apache.org/jira/browse/GUACAMOLE-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
emma updated GUACAMOLE-567:
---
Attachment: Network_Connection8.png
> Network connection problem acknowledgement/feedback
> ---
>
> Key: GUACAMOLE-567
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-567
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-client, guacamole-common-js
>Reporter: Michael Jumper
>Assignee: Michael Jumper
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: Network_Connection1.png, Network_Connection2.png,
> Network_Connection4.png, Network_Connection5.png, Network_Connection6.png,
> Network_Connection7.png, Network_Connection8.png,
> image-2018-05-30-16-26-15-928.png, internal-error.png
>
>
> {panel:bgColor=#EE}
> *The description of this issue was copied from
> [GUAC-1055|https://jira.glyptodon.org/browse/GUAC-1055], an issue in the JIRA
> instance used by the Guacamole project prior to its move to the ASF.*
> Comments, attachments, related issues, and history from prior to acceptance
> *may not have been copied* and can be found instead at the original issue.
> {panel}
> When Guacamole detects that the network connection is slow or hanging, it
> should acknowledge this and unobtrusively notify the user. Lacking such
> notification, slow networks or remote desktop failures look like Guacamole
> bugs, and are frequently reported as such.
> Further, the total lack of a network connection is handled within JavaScript,
> but the error code is not recognized by the Guacamole client. The unknown
> error is thus translated into a generic "An internal error has occurred ..."
> message, which is obviously incorrect:
> !internal-error.png|width=320!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GUACAMOLE-567) Network connection problem acknowledgement/feedback
[
https://issues.apache.org/jira/browse/GUACAMOLE-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
emma updated GUACAMOLE-567:
---
Attachment: Network_Connection7.png
> Network connection problem acknowledgement/feedback
> ---
>
> Key: GUACAMOLE-567
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-567
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-client, guacamole-common-js
>Reporter: Michael Jumper
>Assignee: Michael Jumper
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: Network_Connection1.png, Network_Connection2.png,
> Network_Connection4.png, Network_Connection5.png, Network_Connection6.png,
> Network_Connection7.png, Network_Connection8.png,
> image-2018-05-30-16-26-15-928.png, internal-error.png
>
>
> {panel:bgColor=#EE}
> *The description of this issue was copied from
> [GUAC-1055|https://jira.glyptodon.org/browse/GUAC-1055], an issue in the JIRA
> instance used by the Guacamole project prior to its move to the ASF.*
> Comments, attachments, related issues, and history from prior to acceptance
> *may not have been copied* and can be found instead at the original issue.
> {panel}
> When Guacamole detects that the network connection is slow or hanging, it
> should acknowledge this and unobtrusively notify the user. Lacking such
> notification, slow networks or remote desktop failures look like Guacamole
> bugs, and are frequently reported as such.
> Further, the total lack of a network connection is handled within JavaScript,
> but the error code is not recognized by the Guacamole client. The unknown
> error is thus translated into a generic "An internal error has occurred ..."
> message, which is obviously incorrect:
> !internal-error.png|width=320!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GUACAMOLE-567) Network connection problem acknowledgement/feedback
[
https://issues.apache.org/jira/browse/GUACAMOLE-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
emma updated GUACAMOLE-567:
---
Attachment: Network_Connection6.png
> Network connection problem acknowledgement/feedback
> ---
>
> Key: GUACAMOLE-567
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-567
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-client, guacamole-common-js
>Reporter: Michael Jumper
>Assignee: Michael Jumper
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: Network_Connection1.png, Network_Connection2.png,
> Network_Connection4.png, Network_Connection5.png, Network_Connection6.png,
> image-2018-05-30-16-26-15-928.png, internal-error.png
>
>
> {panel:bgColor=#EE}
> *The description of this issue was copied from
> [GUAC-1055|https://jira.glyptodon.org/browse/GUAC-1055], an issue in the JIRA
> instance used by the Guacamole project prior to its move to the ASF.*
> Comments, attachments, related issues, and history from prior to acceptance
> *may not have been copied* and can be found instead at the original issue.
> {panel}
> When Guacamole detects that the network connection is slow or hanging, it
> should acknowledge this and unobtrusively notify the user. Lacking such
> notification, slow networks or remote desktop failures look like Guacamole
> bugs, and are frequently reported as such.
> Further, the total lack of a network connection is handled within JavaScript,
> but the error code is not recognized by the Guacamole client. The unknown
> error is thus translated into a generic "An internal error has occurred ..."
> message, which is obviously incorrect:
> !internal-error.png|width=320!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GUACAMOLE-567) Network connection problem acknowledgement/feedback
[
https://issues.apache.org/jira/browse/GUACAMOLE-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
emma updated GUACAMOLE-567:
---
Attachment: Network_Connection5.png
> Network connection problem acknowledgement/feedback
> ---
>
> Key: GUACAMOLE-567
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-567
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-client, guacamole-common-js
>Reporter: Michael Jumper
>Assignee: Michael Jumper
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: Network_Connection1.png, Network_Connection2.png,
> Network_Connection4.png, Network_Connection5.png, Network_Connection6.png,
> image-2018-05-30-16-26-15-928.png, internal-error.png
>
>
> {panel:bgColor=#EE}
> *The description of this issue was copied from
> [GUAC-1055|https://jira.glyptodon.org/browse/GUAC-1055], an issue in the JIRA
> instance used by the Guacamole project prior to its move to the ASF.*
> Comments, attachments, related issues, and history from prior to acceptance
> *may not have been copied* and can be found instead at the original issue.
> {panel}
> When Guacamole detects that the network connection is slow or hanging, it
> should acknowledge this and unobtrusively notify the user. Lacking such
> notification, slow networks or remote desktop failures look like Guacamole
> bugs, and are frequently reported as such.
> Further, the total lack of a network connection is handled within JavaScript,
> but the error code is not recognized by the Guacamole client. The unknown
> error is thus translated into a generic "An internal error has occurred ..."
> message, which is obviously incorrect:
> !internal-error.png|width=320!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GUACAMOLE-567) Network connection problem acknowledgement/feedback
[
https://issues.apache.org/jira/browse/GUACAMOLE-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
emma updated GUACAMOLE-567:
---
Attachment: Network_Connection4.png
> Network connection problem acknowledgement/feedback
> ---
>
> Key: GUACAMOLE-567
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-567
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-client, guacamole-common-js
>Reporter: Michael Jumper
>Assignee: Michael Jumper
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: Network_Connection1.png, Network_Connection2.png,
> Network_Connection4.png, image-2018-05-30-16-26-15-928.png, internal-error.png
>
>
> {panel:bgColor=#EE}
> *The description of this issue was copied from
> [GUAC-1055|https://jira.glyptodon.org/browse/GUAC-1055], an issue in the JIRA
> instance used by the Guacamole project prior to its move to the ASF.*
> Comments, attachments, related issues, and history from prior to acceptance
> *may not have been copied* and can be found instead at the original issue.
> {panel}
> When Guacamole detects that the network connection is slow or hanging, it
> should acknowledge this and unobtrusively notify the user. Lacking such
> notification, slow networks or remote desktop failures look like Guacamole
> bugs, and are frequently reported as such.
> Further, the total lack of a network connection is handled within JavaScript,
> but the error code is not recognized by the Guacamole client. The unknown
> error is thus translated into a generic "An internal error has occurred ..."
> message, which is obviously incorrect:
> !internal-error.png|width=320!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GUACAMOLE-567) Network connection problem acknowledgement/feedback
[
https://issues.apache.org/jira/browse/GUACAMOLE-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
emma updated GUACAMOLE-567:
---
Attachment: Network_Connection2.png
> Network connection problem acknowledgement/feedback
> ---
>
> Key: GUACAMOLE-567
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-567
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-client, guacamole-common-js
>Reporter: Michael Jumper
>Assignee: Michael Jumper
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: Network_Connection1.png, Network_Connection2.png,
> image-2018-05-30-16-26-15-928.png, internal-error.png
>
>
> {panel:bgColor=#EE}
> *The description of this issue was copied from
> [GUAC-1055|https://jira.glyptodon.org/browse/GUAC-1055], an issue in the JIRA
> instance used by the Guacamole project prior to its move to the ASF.*
> Comments, attachments, related issues, and history from prior to acceptance
> *may not have been copied* and can be found instead at the original issue.
> {panel}
> When Guacamole detects that the network connection is slow or hanging, it
> should acknowledge this and unobtrusively notify the user. Lacking such
> notification, slow networks or remote desktop failures look like Guacamole
> bugs, and are frequently reported as such.
> Further, the total lack of a network connection is handled within JavaScript,
> but the error code is not recognized by the Guacamole client. The unknown
> error is thus translated into a generic "An internal error has occurred ..."
> message, which is obviously incorrect:
> !internal-error.png|width=320!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GUACAMOLE-567) Network connection problem acknowledgement/feedback
[
https://issues.apache.org/jira/browse/GUACAMOLE-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
emma updated GUACAMOLE-567:
---
Attachment: image-2018-05-30-16-26-15-928.png
> Network connection problem acknowledgement/feedback
> ---
>
> Key: GUACAMOLE-567
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-567
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-client, guacamole-common-js
>Reporter: Michael Jumper
>Assignee: Michael Jumper
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: Network_Connection1.png,
> image-2018-05-30-16-26-15-928.png, internal-error.png
>
>
> {panel:bgColor=#EE}
> *The description of this issue was copied from
> [GUAC-1055|https://jira.glyptodon.org/browse/GUAC-1055], an issue in the JIRA
> instance used by the Guacamole project prior to its move to the ASF.*
> Comments, attachments, related issues, and history from prior to acceptance
> *may not have been copied* and can be found instead at the original issue.
> {panel}
> When Guacamole detects that the network connection is slow or hanging, it
> should acknowledge this and unobtrusively notify the user. Lacking such
> notification, slow networks or remote desktop failures look like Guacamole
> bugs, and are frequently reported as such.
> Further, the total lack of a network connection is handled within JavaScript,
> but the error code is not recognized by the Guacamole client. The unknown
> error is thus translated into a generic "An internal error has occurred ..."
> message, which is obviously incorrect:
> !internal-error.png|width=320!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GUACAMOLE-567) Network connection problem acknowledgement/feedback
[
https://issues.apache.org/jira/browse/GUACAMOLE-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
emma updated GUACAMOLE-567:
---
Attachment: Network_Connection1.png
> Network connection problem acknowledgement/feedback
> ---
>
> Key: GUACAMOLE-567
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-567
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-client, guacamole-common-js
>Reporter: Michael Jumper
>Assignee: Michael Jumper
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: Network_Connection1.png, internal-error.png
>
>
> {panel:bgColor=#EE}
> *The description of this issue was copied from
> [GUAC-1055|https://jira.glyptodon.org/browse/GUAC-1055], an issue in the JIRA
> instance used by the Guacamole project prior to its move to the ASF.*
> Comments, attachments, related issues, and history from prior to acceptance
> *may not have been copied* and can be found instead at the original issue.
> {panel}
> When Guacamole detects that the network connection is slow or hanging, it
> should acknowledge this and unobtrusively notify the user. Lacking such
> notification, slow networks or remote desktop failures look like Guacamole
> bugs, and are frequently reported as such.
> Further, the total lack of a network connection is handled within JavaScript,
> but the error code is not recognized by the Guacamole client. The unknown
> error is thus translated into a generic "An internal error has occurred ..."
> message, which is obviously incorrect:
> !internal-error.png|width=320!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
