[
https://issues.apache.org/jira/browse/GSHELL-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541963
]
Jason Dillon commented on GSHELL-16:
------------------------------------
I'm a little bit confused on the functionality of this patch and how it relates
to the issue context.
The idea was to implement a {{ssh}} command that would function very similarly
to using {{ssh}} from a unix shell... so one could connect to a normal {{sshd}}
server from inside of GShell.
What it looks like this patch does is sets up a port-formward using a {{sshd}}
server, then uses the GShell {{rsh}} bits to make a _TCP_ connection to the
GShell {{rshd}} listener which is secured by the {{ssh}} port forwarding.
I'm not sure that is all that helpful or friendly. You can already use a _SSL_
connection to a GShell {{rshd}} listener and get a secure channel w/o needing
to involve a 3rdparty {{sshd}} server.
Having commands to setup manage {{ssh}} port forwarding may be useful, and may
well be part of the functionality provided by the general {{ssh}} command...
but simply using port-forwarding to make a {{ssh}}-secured _TCP_ connection to
a GShell {{rshd}} listener is IMO, not very useful.
Perhaps the description (or lack of a more detailed description for this issue)
was confusing?
> New command: ssh
> ----------------
>
> Key: GSHELL-16
> URL: https://issues.apache.org/jira/browse/GSHELL-16
> Project: GShell
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: Commands
> Reporter: Jason Dillon
> Assignee: Jason Dillon
> Priority: Minor
> Fix For: 1.0-alpha-2
>
> Attachments: GSHELL-16.patch
>
>
> Can wrap the Jsch API to make a ssh command
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
