[jira] [Closed] (SSHD-869) java.security.SignatureException: error decoding signature bytes.
[ https://issues.apache.org/jira/browse/SSHD-869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Goldstein Lyor closed SSHD-869. --- Resolution: Won't Fix > java.security.SignatureException: error decoding signature bytes. > - > > Key: SSHD-869 > URL: https://issues.apache.org/jira/browse/SSHD-869 > Project: MINA SSHD > Issue Type: Bug >Affects Versions: 0.14.0 >Reporter: Aruna Potti >Priority: Major > > Below exception is seen with some ssh keys. I need a fix/workaround in 0.14.0 > version as I can not upgrade the version in my product. > > Exception caught > java.security.SignatureException: error decoding signature bytes. > at > org.bouncycastle.jcajce.provider.asymmetric.dsa.DSASigner.engineVerify(Unknown > Source)[bcprov-jdk15on-1.59.jar:1.59.0] > at > java.security.Signature$Delegate.engineVerify(Signature.java:1219)[:1.8.0_66] > at java.security.Signature.verify(Signature.java:652)[:1.8.0_66] > at > org.apache.sshd.common.signature.AbstractSignatureDSA.verify(AbstractSignatureDSA.java:88)[53:org.apache.sshd.core:0.14.0] > at > org.apache.sshd.client.kex.DHGEX.next(DHGEX.java:163)[53:org.apache.sshd.core:0.14.0] > at > org.apache.sshd.common.session.AbstractSession.doHandleMessage(AbstractSession.java:425)[53:org.apache.sshd.core:0.14.0] > at > org.apache.sshd.common.session.AbstractSession.handleMessage(AbstractSession.java:326)[53:org.apache.sshd.core:0.14.0] > at > org.apache.sshd.client.session.ClientSessionImpl.handleMessage(ClientSessionImpl.java:306)[53:org.apache.sshd.core:0.14.0] > at > org.apache.sshd.common.session.AbstractSession.decode(AbstractSession.java:780)[53:org.apache.sshd.core:0.14.0] > at > org.apache.sshd.common.session.AbstractSession.messageReceived(AbstractSession.java:308)[53:org.apache.sshd.core:0.14.0] > at > org.apache.sshd.common.AbstractSessionIoHandler.messageReceived(AbstractSessionIoHandler.java:54)[53:org.apache.sshd.core:0.14.0] > at > org.apache.sshd.common.io.nio2.Nio2Session$1.onCompleted(Nio2Session.java:184)[53:org.apache.sshd.core:0.14.0] > at > org.apache.sshd.common.io.nio2.Nio2Session$1.onCompleted(Nio2Session.java:170)[53:org.apache.sshd.core:0.14.0] > at > org.apache.sshd.common.io.nio2.Nio2CompletionHandler$1.run(Nio2CompletionHandler.java:32) > at java.security.AccessController.doPrivileged(Native > Method)[:1.8.0_66] > at > org.apache.sshd.common.io.nio2.Nio2CompletionHandler.completed(Nio2CompletionHandler.java:30)[53:org.apache.sshd.core:0.14.0] > at sun.nio.ch.Invoker.invokeUnchecked(Invoker.java:126)[:1.8.0_66] > at sun.nio.ch.Invoker$2.run(Invoker.java:218)[:1.8.0_66] > at > sun.nio.ch.AsynchronousChannelGroupImpl$1.run(AsynchronousChannelGroupImpl.java:112)[:1.8.0_66] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_66] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_66] > at java.lang.Thread.run(Thread.java:745)[:1.8.0_66] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SSHD-869) java.security.SignatureException: error decoding signature bytes.
[
https://issues.apache.org/jira/browse/SSHD-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16692683#comment-16692683
]
Goldstein Lyor commented on SSHD-869:
-
{quote}
I need a fix/workaround in 0.14.0 version as I can not upgrade the version in
my product.
{quote}
I am very sorry :(, but we cannot maintain several versions of the library due
to the extremely limited manpower we have. Furthermore 0.14.0 is an extremely
old version which contains many bugs that have been fixed since. I do strongly
recommend to make the effort and upgrade to 2.1 :) (unless you cannot use JDK
1.8 code, in which case I cannot offer a solution).
> java.security.SignatureException: error decoding signature bytes.
> -
>
> Key: SSHD-869
> URL: https://issues.apache.org/jira/browse/SSHD-869
> Project: MINA SSHD
> Issue Type: Bug
>Affects Versions: 0.14.0
>Reporter: Aruna Potti
>Priority: Major
>
> Below exception is seen with some ssh keys. I need a fix/workaround in 0.14.0
> version as I can not upgrade the version in my product.
>
> Exception caught
> java.security.SignatureException: error decoding signature bytes.
> at
> org.bouncycastle.jcajce.provider.asymmetric.dsa.DSASigner.engineVerify(Unknown
> Source)[bcprov-jdk15on-1.59.jar:1.59.0]
> at
> java.security.Signature$Delegate.engineVerify(Signature.java:1219)[:1.8.0_66]
> at java.security.Signature.verify(Signature.java:652)[:1.8.0_66]
> at
> org.apache.sshd.common.signature.AbstractSignatureDSA.verify(AbstractSignatureDSA.java:88)[53:org.apache.sshd.core:0.14.0]
> at
> org.apache.sshd.client.kex.DHGEX.next(DHGEX.java:163)[53:org.apache.sshd.core:0.14.0]
> at
> org.apache.sshd.common.session.AbstractSession.doHandleMessage(AbstractSession.java:425)[53:org.apache.sshd.core:0.14.0]
> at
> org.apache.sshd.common.session.AbstractSession.handleMessage(AbstractSession.java:326)[53:org.apache.sshd.core:0.14.0]
> at
> org.apache.sshd.client.session.ClientSessionImpl.handleMessage(ClientSessionImpl.java:306)[53:org.apache.sshd.core:0.14.0]
> at
> org.apache.sshd.common.session.AbstractSession.decode(AbstractSession.java:780)[53:org.apache.sshd.core:0.14.0]
> at
> org.apache.sshd.common.session.AbstractSession.messageReceived(AbstractSession.java:308)[53:org.apache.sshd.core:0.14.0]
> at
> org.apache.sshd.common.AbstractSessionIoHandler.messageReceived(AbstractSessionIoHandler.java:54)[53:org.apache.sshd.core:0.14.0]
> at
> org.apache.sshd.common.io.nio2.Nio2Session$1.onCompleted(Nio2Session.java:184)[53:org.apache.sshd.core:0.14.0]
> at
> org.apache.sshd.common.io.nio2.Nio2Session$1.onCompleted(Nio2Session.java:170)[53:org.apache.sshd.core:0.14.0]
> at
> org.apache.sshd.common.io.nio2.Nio2CompletionHandler$1.run(Nio2CompletionHandler.java:32)
> at java.security.AccessController.doPrivileged(Native
> Method)[:1.8.0_66]
> at
> org.apache.sshd.common.io.nio2.Nio2CompletionHandler.completed(Nio2CompletionHandler.java:30)[53:org.apache.sshd.core:0.14.0]
> at sun.nio.ch.Invoker.invokeUnchecked(Invoker.java:126)[:1.8.0_66]
> at sun.nio.ch.Invoker$2.run(Invoker.java:218)[:1.8.0_66]
> at
> sun.nio.ch.AsynchronousChannelGroupImpl$1.run(AsynchronousChannelGroupImpl.java:112)[:1.8.0_66]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_66]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_66]
> at java.lang.Thread.run(Thread.java:745)[:1.8.0_66]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (SSHD-869) java.security.SignatureException: error decoding signature bytes.
Aruna Potti created SSHD-869: Summary: java.security.SignatureException: error decoding signature bytes. Key: SSHD-869 URL: https://issues.apache.org/jira/browse/SSHD-869 Project: MINA SSHD Issue Type: Bug Affects Versions: 0.14.0 Reporter: Aruna Potti Below exception is seen with some ssh keys. I need a fix/workaround in 0.14.0 version as I can not upgrade the version in my product. Exception caught java.security.SignatureException: error decoding signature bytes. at org.bouncycastle.jcajce.provider.asymmetric.dsa.DSASigner.engineVerify(Unknown Source)[bcprov-jdk15on-1.59.jar:1.59.0] at java.security.Signature$Delegate.engineVerify(Signature.java:1219)[:1.8.0_66] at java.security.Signature.verify(Signature.java:652)[:1.8.0_66] at org.apache.sshd.common.signature.AbstractSignatureDSA.verify(AbstractSignatureDSA.java:88)[53:org.apache.sshd.core:0.14.0] at org.apache.sshd.client.kex.DHGEX.next(DHGEX.java:163)[53:org.apache.sshd.core:0.14.0] at org.apache.sshd.common.session.AbstractSession.doHandleMessage(AbstractSession.java:425)[53:org.apache.sshd.core:0.14.0] at org.apache.sshd.common.session.AbstractSession.handleMessage(AbstractSession.java:326)[53:org.apache.sshd.core:0.14.0] at org.apache.sshd.client.session.ClientSessionImpl.handleMessage(ClientSessionImpl.java:306)[53:org.apache.sshd.core:0.14.0] at org.apache.sshd.common.session.AbstractSession.decode(AbstractSession.java:780)[53:org.apache.sshd.core:0.14.0] at org.apache.sshd.common.session.AbstractSession.messageReceived(AbstractSession.java:308)[53:org.apache.sshd.core:0.14.0] at org.apache.sshd.common.AbstractSessionIoHandler.messageReceived(AbstractSessionIoHandler.java:54)[53:org.apache.sshd.core:0.14.0] at org.apache.sshd.common.io.nio2.Nio2Session$1.onCompleted(Nio2Session.java:184)[53:org.apache.sshd.core:0.14.0] at org.apache.sshd.common.io.nio2.Nio2Session$1.onCompleted(Nio2Session.java:170)[53:org.apache.sshd.core:0.14.0] at org.apache.sshd.common.io.nio2.Nio2CompletionHandler$1.run(Nio2CompletionHandler.java:32) at java.security.AccessController.doPrivileged(Native Method)[:1.8.0_66] at org.apache.sshd.common.io.nio2.Nio2CompletionHandler.completed(Nio2CompletionHandler.java:30)[53:org.apache.sshd.core:0.14.0] at sun.nio.ch.Invoker.invokeUnchecked(Invoker.java:126)[:1.8.0_66] at sun.nio.ch.Invoker$2.run(Invoker.java:218)[:1.8.0_66] at sun.nio.ch.AsynchronousChannelGroupImpl$1.run(AsynchronousChannelGroupImpl.java:112)[:1.8.0_66] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_66] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_66] at java.lang.Thread.run(Thread.java:745)[:1.8.0_66] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SSHD-757) Add support for PGP authorized keys usage
[
https://issues.apache.org/jira/browse/SSHD-757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Goldstein Lyor updated SSHD-757:
Description:
[SSH 2.3|http://www.onlamp.com/pub/a/onlamp/excerpt/ssh_8/] seems to have added
the capability to use PGP keys as authorized ones:
{quote}
SSH2 Version 2.0.13 introduced support for PGP authentication. Your
authorization file may also include {{PgpPublicKeyFile, PgpKeyName, PgpKey
Fingerprint}}, and {{PgpKeyId}} lines. A Command line may follow them, just as
it may follow Key:
{noformat}
# SSH2 only
PgpKeyName my-key
Command "/bin/echo PGP authentication was detected"
{noformat}
{quote}
Some examples of how to use _Bouncycastle_ to facilitate this:
* [Sample code|https://github.com/damico/OpenPgp-BounceCastle-Example]
* [jpgpj Library wrapper|https://github.com/justinludwig/jpgpj]
_Python_ [converter
pgp->ssh|https://raw.githubusercontent.com/fincham/ssh-to-pgp/master/ssh-to-pgp]
_openssh-gpg_ [configuration|http://www.red-bean.com/~nemo/openssh-gpg/]
[Calculating PGP key
fingerprint|https://crypto.stackexchange.com/questions/32087/how-to-generate-fingerprint-for-pgp-public-key]
was:
[SSH 2.3|http://www.onlamp.com/pub/a/onlamp/excerpt/ssh_8/] seems to have added
the capability to use PGP keys as authorized ones:
{quote}
SSH2 Version 2.0.13 introduced support for PGP authentication. Your
authorization file may also include {{PgpPublicKeyFile, PgpKeyName, PgpKey
Fingerprint}}, and {{PgpKeyId}} lines. A Command line may follow them, just as
it may follow Key:
{noformat}
# SSH2 only
PgpKeyName my-key
Command "/bin/echo PGP authentication was detected"
{noformat}
{quote}
Some examples of how to use _Bouncycastle_ to facilitate this:
* [Sample code|https://github.com/damico/OpenPgp-BounceCastle-Example]
* [jpgpj Library wrapper|https://github.com/justinludwig/jpgpj]
_Python_ [converter
pgp->ssh|https://raw.githubusercontent.com/fincham/ssh-to-pgp/master/ssh-to-pgp]
_openssh-gpg_ [configuration|http://www.red-bean.com/~nemo/openssh-gpg/]
> Add support for PGP authorized keys usage
> -
>
> Key: SSHD-757
> URL: https://issues.apache.org/jira/browse/SSHD-757
> Project: MINA SSHD
> Issue Type: New Feature
>Affects Versions: 1.6.0
>Reporter: Goldstein Lyor
>Assignee: Goldstein Lyor
>Priority: Minor
> Labels: authorization, key, key-management, pgp, ssh
>
> [SSH 2.3|http://www.onlamp.com/pub/a/onlamp/excerpt/ssh_8/] seems to have
> added the capability to use PGP keys as authorized ones:
> {quote}
> SSH2 Version 2.0.13 introduced support for PGP authentication. Your
> authorization file may also include {{PgpPublicKeyFile, PgpKeyName, PgpKey
> Fingerprint}}, and {{PgpKeyId}} lines. A Command line may follow them, just
> as it may follow Key:
> {noformat}
> # SSH2 only
> PgpKeyName my-key
> Command "/bin/echo PGP authentication was detected"
> {noformat}
> {quote}
> Some examples of how to use _Bouncycastle_ to facilitate this:
> * [Sample code|https://github.com/damico/OpenPgp-BounceCastle-Example]
> * [jpgpj Library wrapper|https://github.com/justinludwig/jpgpj]
> _Python_ [converter
> pgp->ssh|https://raw.githubusercontent.com/fincham/ssh-to-pgp/master/ssh-to-pgp]
> _openssh-gpg_ [configuration|http://www.red-bean.com/~nemo/openssh-gpg/]
> [Calculating PGP key
> fingerprint|https://crypto.stackexchange.com/questions/32087/how-to-generate-fingerprint-for-pgp-public-key]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (SSHD-844) Deadlock detected in Apache SSHD client code
[ https://issues.apache.org/jira/browse/SSHD-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Goldstein Lyor resolved SSHD-844. - Resolution: Not A Problem > Deadlock detected in Apache SSHD client code > > > Key: SSHD-844 > URL: https://issues.apache.org/jira/browse/SSHD-844 > Project: MINA SSHD > Issue Type: Bug >Affects Versions: 2.0.1 > Environment: AIX 7.2 > java version "1.8.0_151" > Java(TM) SE Runtime Environment (build 8.0.5.7 - > pap6480sr5fp7-20171216_01(SR5 FP7)) > IBM J9 VM (build 2.9, JRE 1.8.0 AIX ppc64-64 Compressed References > 20171215_373586 (JIT enabled, AOT enabled) > OpenJ9 - 5aa401f > OMR - 101e793 > IBM - b4a79bf) > JCL - 20171214_01 based on Oracle jdk8u151-b12 >Reporter: Roberto Deandrea >Priority: Critical > Attachments: javacore.20180913.153332.14221746.0001.txt, jca457.jar > > > I found a deadlock in Apache SSHD client code running integration test for a > local port forwarding application. Attached the IBM javacore with information > about the deadlock. > Please run $java -jar jca457.jar to load the javacore file and display thread > stack traces. > [^javacore.20180913.153332.14221746.0001.txt] > [^jca457.jar] > > There are 2 threads in DEADLOCK belonging to client pool's threads, that > blocked the other pool threads from working. > The locks involved are LOCK1 (object ChannelOutputStream) and LOCK2 Object > encodeLock of AbstractSession class. > > The below thread is waiting on LOCK2 and owns LOCK1 (that is > ChannelOutputStream object) > The thread sshd-SshClient[61e9f863]-nio2-thread-6 has the following stack > trace : > > at > org/apache/sshd/common/session/helpers/AbstractSession.doWritePacket(AbstractSession.java:1189(Compiled > Code)) > at > org/apache/sshd/common/session/helpers/AbstractSession.writePacket(AbstractSession.java:1137(Compiled > Code)) > at > org/apache/sshd/common/channel/AbstractChannel.writePacket(AbstractChannel.java:773(Compiled > Code)) > at > org/apache/sshd/common/channel/ChannelOutputStream.flush(ChannelOutputStream.java:227(Compiled > Code)) > at > org/apache/sshd/common/forward/DefaultForwardingFilter$StaticIoHandler.messageReceived(DefaultForwardingFilter.java:1063(Compiled > Code)) > at > org/apache/sshd/common/io/nio2/Nio2Session.handleReadCycleCompletion(Nio2Session.java:339(Compiled > Code)) > at > org/apache/sshd/common/io/nio2/Nio2Session$1.onCompleted(Nio2Session.java:318(Compiled > Code)) > at > org/apache/sshd/common/io/nio2/Nio2Session$1.onCompleted(Nio2Session.java:315(Compiled > Code)) > at > org/apache/sshd/common/io/nio2/Nio2CompletionHandler.lambda$completed$0(Nio2CompletionHandler.java:38(Compiled > Code)) > at > org/apache/sshd/common/io/nio2/Nio2CompletionHandler$$Lambda$254/23F76250.run(Bytecode > PC:12(Compiled Code)) > at > java/security/AccessController.doPrivileged(AccessController.java:638(Compiled > Code)) > at > org/apache/sshd/common/io/nio2/Nio2CompletionHandler.completed(Nio2CompletionHandler.java:37(Compiled > Code)) > at sun/nio/ch/Invoker.invokeUnchecked(Invoker.java:138(Compiled Code)) > at sun/nio/ch/Invoker$2.run(Invoker.java:230(Compiled Code)) > at > sun/nio/ch/AsynchronousChannelGroupImpl$1.run(AsynchronousChannelGroupImpl.java:124(Compiled > Code)) > at > java/util/concurrent/ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1160(Compiled > Code)) > at > java/util/concurrent/ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) > > at java/lang/Thread.run(Thread.java:811) > > This thread is waiting for LOCK1 and owns LOCK2. > The thread sshd-SshClient[61e9f863]-nio2-thread-10 has the following stack > trace: > > at > org/apache/sshd/common/channel/ChannelOutputStream.close(ChannelOutputStream.java:249(Compiled > Code)) > at > org/apache/sshd/common/util/io/IoUtils.closeQuietly(IoUtils.java:151(Compiled > Code)) > at > org/apache/sshd/client/channel/AbstractClientChannel.lambda$getInnerCloseable$1(AbstractClientChannel.java:203(Compiled > Code)) > at > org/apache/sshd/client/channel/AbstractClientChannel$$Lambda$314/252C5370.run(Bytecode > PC:4(Compiled Code)) > at > org/apache/sshd/common/util/closeable/Builder$1.doClose(Builder.java:47(Compiled > Code)) > at > org/apache/sshd/common/util/closeable/SimpleCloseable.close(SimpleCloseable.java:63(Compiled > Code)) > at > org/apache/sshd/common/util/closeable/SequentialCloseable$1.operationComplete(SequentialCloseable.java:56(Compiled > Code)) > at > org/apache/sshd/common/util/closeable/SequentialCloseable$1.operationComplete(SequentialCloseable.java:45(Compiled > Code)) > at > org/apache/sshd/common/future/AbstractSshFuture.notifyListener(AbstractSshFuture.java:159(Compiled > Code)) > at >
[jira] [Resolved] (SSHD-865) Use lazy-loading for keys specified in the HostConfigEntry
[
https://issues.apache.org/jira/browse/SSHD-865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Goldstein Lyor resolved SSHD-865.
-
Resolution: Fixed
Fix Version/s: 2.1.1
> Use lazy-loading for keys specified in the HostConfigEntry
> --
>
> Key: SSHD-865
> URL: https://issues.apache.org/jira/browse/SSHD-865
> Project: MINA SSHD
> Issue Type: Improvement
>Affects Versions: 2.1.1
>Reporter: Goldstein Lyor
>Assignee: Goldstein Lyor
>Priority: Major
> Fix For: 2.1.1
>
>
> Following SSHD-860 key loading occurs lazily - thus encrypted keys password
> is not requested until the key is actually needed. The exception to this rule
> are keys specified as part of a {{HostConfigEntry}} specified in an
> [ssh_config file|http://www.gsp.com/cgi-bin/man.cgi?topic=ssh_config].
> h5. Implementation details
> * Need to change {{SshClient#loadClientIdentities}} to return a
> {{KeyPairProvider}} that is propagated all the way to
> {{SshClient#onConnectOperationComplete}}.
> * The code in {{SshClient#onConnectOperationComplete}} should check after
> {{setupDefaultSessionIdentities}} if there is a non-empty {{KeyPairProvider}}
> propagated and *aggregate* it with any already set such provider on the
> session
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SSHD-863) Add local/remote port forwarding to/from Unix sockets
[ https://issues.apache.org/jira/browse/SSHD-863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16691669#comment-16691669 ] Goldstein Lyor commented on SSHD-863: - Indeed it seems like something that can be done (as a *separate* module - e.g., _sshd-openssh-fwd_). However, I don't see it happening any time soon unless someone that is *not* part of the SSHD project takes it upon him/herself to contribute this code (including unit tests). The other way this can happen is this feature becomes very popular - and even then, my instinct tells me that we would need to rely on the *community* to contribute the code. > Add local/remote port forwarding to/from Unix sockets > - > > Key: SSHD-863 > URL: https://issues.apache.org/jira/browse/SSHD-863 > Project: MINA SSHD > Issue Type: Improvement >Affects Versions: 2.1.0 >Reporter: Björn Kautler >Assignee: Goldstein Lyor >Priority: Minor > Labels: future, wishlist > > Would be nice if MINA SSHD also supports forwarding sockets, not only ports. > Currently you can only forward from port to port, but SSH now can do from > port to socket, from socket to port, from port to port and from port to > socket. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SSHD-863) Add local/remote port forwarding to/from Unix sockets
[ https://issues.apache.org/jira/browse/SSHD-863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Goldstein Lyor updated SSHD-863: Labels: future wishlist (was: ) > Add local/remote port forwarding to/from Unix sockets > - > > Key: SSHD-863 > URL: https://issues.apache.org/jira/browse/SSHD-863 > Project: MINA SSHD > Issue Type: Improvement >Affects Versions: 2.1.0 >Reporter: Björn Kautler >Assignee: Goldstein Lyor >Priority: Minor > Labels: future, wishlist > > Would be nice if MINA SSHD also supports forwarding sockets, not only ports. > Currently you can only forward from port to port, but SSH now can do from > port to socket, from socket to port, from port to port and from port to > socket. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
