[jira] [Updated] (GUACAMOLE-865) Missing libfreerdp-dev for Server Docker Build

2019-08-19 Thread Nick Couchman (Jira)


 [ 
https://issues.apache.org/jira/browse/GUACAMOLE-865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nick Couchman updated GUACAMOLE-865:

Priority: Minor  (was: Major)

> 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.2#803003)


[jira] [Created] (GUACAMOLE-865) Missing libfreerdp-dev for Server Docker Build

2019-08-19 Thread Matt Grochowalski (Jira)
Matt Grochowalski created GUACAMOLE-865:
---

 Summary: 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


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.2#803003)


[jira] [Commented] (GUACAMOLE-221) Parameter prompting within client interface

2019-08-19 Thread Joseph Gullo (Jira)


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

Joseph Gullo commented on GUACAMOLE-221:


My install is compiled from source, if you have a patch that enables that 
feature and you need testing please let me know, I'd be happy to test!  My 
reading above was that you may have had a solution for username and password, 
hence thinking there may be something patchable.

Thank you for your work!

> Parameter prompting within client interface
> ---
>
> Key: GUACAMOLE-221
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-221
> Project: Guacamole
>  Issue Type: New Feature
>  Components: guacamole
>Reporter: Michael Jumper
>Assignee: Nick Couchman
>Priority: Major
>
> {panel:bgColor=#EE}
> *The description of this issue was copied from 
> [GUAC-335|https://glyptodon.org/jira/browse/GUAC-335], an issue in the JIRA 
> instance used by the Guacamole project prior to its acceptance into the 
> Apache Incubator.*
> Comments, attachments, related issues, and history from prior to acceptance 
> *have not been copied* and can be found instead at the original issue.
> {panel}
> Some parameters, such as the username/password for VNC or RDP, are better 
> entered manually within the client when connecting rather than stored on the 
> server in MySQL or {{user-mapping.xml}}.
> Storing secure data within parameters on the server side has security 
> implications that don't fit well with all use cases.
> Further, some connections would benefit if their settings can be modified 
> locally before connecting. A user could change the color depth or screen size 
> of their RDP session, for example, for the sake of a slower connection.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Commented] (GUACAMOLE-221) Parameter prompting within client interface

2019-08-19 Thread Nick Couchman (Jira)


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

Nick Couchman commented on GUACAMOLE-221:
-

{quote}
3) I see a connection to a domain controller, I want to connect to that session 
with a separate domain admin account.  I'd like to be able to enter credentials.
{quote}

This would require prompting to be implemented.

{quote}
4) I see a connection to a switch.  I want to connect to that session with 
separate network admin credentials.
{quote}

Presumably this is either SSH or Telnet, which already implement prompting 
within the Guacamole terminal.

{quote}
5) I see a connection to a server, I want to connect to that session with 
separate server admin credentials.
{quote}

For SSH or Telnet, this should work okay - for RDP or VNC, you'll need to wait 
for prompting to be implemented.

> Parameter prompting within client interface
> ---
>
> Key: GUACAMOLE-221
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-221
> Project: Guacamole
>  Issue Type: New Feature
>  Components: guacamole
>Reporter: Michael Jumper
>Assignee: Nick Couchman
>Priority: Major
>
> {panel:bgColor=#EE}
> *The description of this issue was copied from 
> [GUAC-335|https://glyptodon.org/jira/browse/GUAC-335], an issue in the JIRA 
> instance used by the Guacamole project prior to its acceptance into the 
> Apache Incubator.*
> Comments, attachments, related issues, and history from prior to acceptance 
> *have not been copied* and can be found instead at the original issue.
> {panel}
> Some parameters, such as the username/password for VNC or RDP, are better 
> entered manually within the client when connecting rather than stored on the 
> server in MySQL or {{user-mapping.xml}}.
> Storing secure data within parameters on the server side has security 
> implications that don't fit well with all use cases.
> Further, some connections would benefit if their settings can be modified 
> locally before connecting. A user could change the color depth or screen size 
> of their RDP session, for example, for the sake of a slower connection.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Commented] (GUACAMOLE-221) Parameter prompting within client interface

2019-08-19 Thread Joseph Gullo (Jira)


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

Joseph Gullo commented on GUACAMOLE-221:


Awesome, I hadn't seen that.

 

Still, the workflow I'm thinking of is the following:

1) I authenticate into guacamole as my regular user account

2) I connect to my normal desktop using a parameter, no issue.

3) I see a connection to a domain controller, I want to connect to that session 
with a separate domain admin account.  I'd like to be able to enter credentials.

4) I see a connection to a switch.  I want to connect to that session with 
separate network admin credentials.

5) I see a connection to a server, I want to connect to that session with 
separate server admin credentials.

 

In theory, the only possible credentials that can successfully authenticate 
from the internet are my un-privileged ones, then you would need to know 
additional credentials once inside the network.  I don't like the idea of 
storing my admin credentials, and I don't like the idea of my admin accounts 
accessible to a WAN login.  I know I can bounce from RDP once inside my regular 
session, but RDP-through-RDP starts to feel sloppy. 

> Parameter prompting within client interface
> ---
>
> Key: GUACAMOLE-221
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-221
> Project: Guacamole
>  Issue Type: New Feature
>  Components: guacamole
>Reporter: Michael Jumper
>Assignee: Nick Couchman
>Priority: Major
>
> {panel:bgColor=#EE}
> *The description of this issue was copied from 
> [GUAC-335|https://glyptodon.org/jira/browse/GUAC-335], an issue in the JIRA 
> instance used by the Guacamole project prior to its acceptance into the 
> Apache Incubator.*
> Comments, attachments, related issues, and history from prior to acceptance 
> *have not been copied* and can be found instead at the original issue.
> {panel}
> Some parameters, such as the username/password for VNC or RDP, are better 
> entered manually within the client when connecting rather than stored on the 
> server in MySQL or {{user-mapping.xml}}.
> Storing secure data within parameters on the server side has security 
> implications that don't fit well with all use cases.
> Further, some connections would benefit if their settings can be modified 
> locally before connecting. A user could change the color depth or screen size 
> of their RDP session, for example, for the sake of a slower connection.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)