[jira] [Commented] (GUACAMOLE-745) Add support for OpenSSH private key format
[
https://issues.apache.org/jira/browse/GUACAMOLE-745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16919898#comment-16919898
]
Nick Couchman commented on GUACAMOLE-745:
-
[~catheyc]: It's minor because the number of people demanding it is low,
relatively speaking. The project has other things that have bubbled to the top
to focus on.
We would welcome your contributions if it's something you or someone on your
team would like to help with - I love closing out tasks/issues, so I certainly
wouldn't turn down the help :-). Contribution guidelines, including style
guidelines, are on the web site, here: http://guacamole.apache.org/open-source/.
Thanks!!
> Add support for OpenSSH private key format
> --
>
> Key: GUACAMOLE-745
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-745
> Project: Guacamole
> Issue Type: Improvement
> Components: guacd, SSH
> Environment: Docker official images 1.0.0
>Reporter: Julien Nicoulaud
>Priority: Minor
>
> Since OpenSSH 7.8, {{ssh-keygen}} does not generate keys in PEM format by
> default anymore: [https://www.openssh.com/txt/release-7.8]
> Attempting to use keys in the new format in Guacamole does not work, and does
> not print any helpful error message even in debug mode:
> {code:java}
> guacd_1 | guacd[296]: DEBUG: Attempting private key import
> (WITHOUT passphrase)
> guacd_1 | guacd[296]: DEBUG: Initial import failed: (null)
> guacd_1 | guacd[296]: DEBUG: Re-attempting private key import
> (WITH passphrase)
> guacd_1 | guacd[296]: ERROR: Auth key import failed: (null){code}
> It would be nice if keys in OpenSSH new format were supported. At least a
> more helpful error message should be printed (like "unrecognized key format").
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Comment Edited] (GUACAMOLE-745) Add support for OpenSSH private key format
[
https://issues.apache.org/jira/browse/GUACAMOLE-745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16919861#comment-16919861
]
Charles LeConte Cathey edited comment on GUACAMOLE-745 at 8/30/19 8:18 PM:
---
Like [~nicoulaj], I agree that the modifications to the format headers are
necessary. I notice that this is listed as a Minor improvement but it
prohibits the use of FIPS=1 enabled hosts to generate {{BEGIN RSA PRIVATE
KEY}} keys (PKCS#5 vs PKCS#8 keys). This is presently blocking some of our
progress using 1.0.0. I see the ticket is unassigned. Has anyone already
worked this? If not we may take it on.
was (Author: catheyc):
Like [~nicoulaj], I agree that the modifications to the format headers are
necessary. I notice that this is listed as a Minor improvement but it
prohibits the use of FIPS=1 enabled hosts to generate {{-BEGIN RSA PRIVATE
KEY-}} keys (PKCS#5 vs PKCS#8 keys). This is presently blocking some of
our progress using 1.0.0. I see the ticket is unassigned. Has anyone already
worked this? If not we may take it on.
> Add support for OpenSSH private key format
> --
>
> Key: GUACAMOLE-745
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-745
> Project: Guacamole
> Issue Type: Improvement
> Components: guacd, SSH
> Environment: Docker official images 1.0.0
>Reporter: Julien Nicoulaud
>Priority: Minor
>
> Since OpenSSH 7.8, {{ssh-keygen}} does not generate keys in PEM format by
> default anymore: [https://www.openssh.com/txt/release-7.8]
> Attempting to use keys in the new format in Guacamole does not work, and does
> not print any helpful error message even in debug mode:
> {code:java}
> guacd_1 | guacd[296]: DEBUG: Attempting private key import
> (WITHOUT passphrase)
> guacd_1 | guacd[296]: DEBUG: Initial import failed: (null)
> guacd_1 | guacd[296]: DEBUG: Re-attempting private key import
> (WITH passphrase)
> guacd_1 | guacd[296]: ERROR: Auth key import failed: (null){code}
> It would be nice if keys in OpenSSH new format were supported. At least a
> more helpful error message should be printed (like "unrecognized key format").
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Comment Edited] (GUACAMOLE-745) Add support for OpenSSH private key format
[
https://issues.apache.org/jira/browse/GUACAMOLE-745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16919861#comment-16919861
]
Charles LeConte Cathey edited comment on GUACAMOLE-745 at 8/30/19 8:17 PM:
---
Like [~nicoulaj], I agree that the modifications to the format headers are
necessary. I notice that this is listed as a Minor improvement but it
prohibits the use of FIPS=1 enabled hosts to generate {{-BEGIN RSA PRIVATE
KEY-}} keys (PKCS#5 vs PKCS#8 keys). This is presently blocking some of
our progress using 1.0.0. I see the ticket is unassigned. Has anyone already
worked this? If not we may take it on.
was (Author: catheyc):
Like [~nicoulaj], I agree that the modifications to the format headers are
necessary. I notice that this is listed as a Minor improvement but it
prohibits the use of FIPS=1 enabled hosts to generate -BEGIN RSA PRIVATE
KEY- keys (PKCS#1 vs PKCS#8 keys). This is presently blocking some of our
progress using 1.0.0. I see the ticket is unassigned. Has anyone already
worked this? If not we may take it on.
> Add support for OpenSSH private key format
> --
>
> Key: GUACAMOLE-745
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-745
> Project: Guacamole
> Issue Type: Improvement
> Components: guacd, SSH
> Environment: Docker official images 1.0.0
>Reporter: Julien Nicoulaud
>Priority: Minor
>
> Since OpenSSH 7.8, {{ssh-keygen}} does not generate keys in PEM format by
> default anymore: [https://www.openssh.com/txt/release-7.8]
> Attempting to use keys in the new format in Guacamole does not work, and does
> not print any helpful error message even in debug mode:
> {code:java}
> guacd_1 | guacd[296]: DEBUG: Attempting private key import
> (WITHOUT passphrase)
> guacd_1 | guacd[296]: DEBUG: Initial import failed: (null)
> guacd_1 | guacd[296]: DEBUG: Re-attempting private key import
> (WITH passphrase)
> guacd_1 | guacd[296]: ERROR: Auth key import failed: (null){code}
> It would be nice if keys in OpenSSH new format were supported. At least a
> more helpful error message should be printed (like "unrecognized key format").
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (GUACAMOLE-745) Add support for OpenSSH private key format
[
https://issues.apache.org/jira/browse/GUACAMOLE-745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16919861#comment-16919861
]
Charles LeConte Cathey commented on GUACAMOLE-745:
--
Like [~nicoulaj], I agree that the modifications to the format headers are
necessary. I notice that this is listed as a Minor improvement but it
prohibits the use of FIPS=1 enabled hosts to generate -BEGIN RSA PRIVATE
KEY- keys (PKCS#1 vs PKCS#8 keys). This is presently blocking some of our
progress using 1.0.0. I see the ticket is unassigned. Has anyone already
worked this? If not we may take it on.
> Add support for OpenSSH private key format
> --
>
> Key: GUACAMOLE-745
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-745
> Project: Guacamole
> Issue Type: Improvement
> Components: guacd, SSH
> Environment: Docker official images 1.0.0
>Reporter: Julien Nicoulaud
>Priority: Minor
>
> Since OpenSSH 7.8, {{ssh-keygen}} does not generate keys in PEM format by
> default anymore: [https://www.openssh.com/txt/release-7.8]
> Attempting to use keys in the new format in Guacamole does not work, and does
> not print any helpful error message even in debug mode:
> {code:java}
> guacd_1 | guacd[296]: DEBUG: Attempting private key import
> (WITHOUT passphrase)
> guacd_1 | guacd[296]: DEBUG: Initial import failed: (null)
> guacd_1 | guacd[296]: DEBUG: Re-attempting private key import
> (WITH passphrase)
> guacd_1 | guacd[296]: ERROR: Auth key import failed: (null){code}
> It would be nice if keys in OpenSSH new format were supported. At least a
> more helpful error message should be printed (like "unrecognized key format").
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (GUACAMOLE-867) Text field on iOS does not bring up keyboard
[ https://issues.apache.org/jira/browse/GUACAMOLE-867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-867: Priority: Minor (was: Major) > Text field on iOS does not bring up keyboard > > > Key: GUACAMOLE-867 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-867 > Project: Guacamole > Issue Type: Bug >Reporter: Wesley Bresson >Priority: Minor > > Logging into Guacamole, connecting to an RDP session, and clicking in a text > field in the RDP session does not bring up the iOS keyboard. It doesn't > recognize the box as a text field. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Closed] (GUACAMOLE-867) Text field on iOS does not bring up keyboard
[ https://issues.apache.org/jira/browse/GUACAMOLE-867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman closed GUACAMOLE-867. --- Resolution: Duplicate > Text field on iOS does not bring up keyboard > > > Key: GUACAMOLE-867 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-867 > Project: Guacamole > Issue Type: Bug >Reporter: Wesley Bresson >Priority: Minor > > Logging into Guacamole, connecting to an RDP session, and clicking in a text > field in the RDP session does not bring up the iOS keyboard. It doesn't > recognize the box as a text field. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (GUACAMOLE-867) Text field on iOS does not bring up keyboard
[ https://issues.apache.org/jira/browse/GUACAMOLE-867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16919573#comment-16919573 ] Wesley Bresson commented on GUACAMOLE-867: -- Possible dupe of 380 > Text field on iOS does not bring up keyboard > > > Key: GUACAMOLE-867 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-867 > Project: Guacamole > Issue Type: Bug >Reporter: Wesley Bresson >Priority: Major > > Logging into Guacamole, connecting to an RDP session, and clicking in a text > field in the RDP session does not bring up the iOS keyboard. It doesn't > recognize the box as a text field. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (GUACAMOLE-867) Text field on iOS does not bring up keyboard
Wesley Bresson created GUACAMOLE-867: Summary: Text field on iOS does not bring up keyboard Key: GUACAMOLE-867 URL: https://issues.apache.org/jira/browse/GUACAMOLE-867 Project: Guacamole Issue Type: Bug Reporter: Wesley Bresson Logging into Guacamole, connecting to an RDP session, and clicking in a text field in the RDP session does not bring up the iOS keyboard. It doesn't recognize the box as a text field. -- This message was sent by Atlassian Jira (v8.3.2#803003)
