tomaswolf commented on issue #493:
URL: https://github.com/apache/mina-sshd/issues/493#issuecomment-2116149268
OK, thank you. Essentially: arcfour256 works only with the `hmac-*-etm` MACs.
This is a bug; it's caused by wrong block sizes being set. Yes, arcfour128
and arcfour256 are
tomaswolf commented on issue #485:
URL: https://github.com/apache/mina-sshd/issues/485#issuecomment-2115924971
So far I have not enough information to do anything. I have run my own speed
tests, and I see no performance problem. Before I can do anything I need to be
able to reproduce the
benz-ppi commented on issue #485:
URL: https://github.com/apache/mina-sshd/issues/485#issuecomment-2115654272
Even with the changes you have suggested, transferring files with the SFTP
Apache client software is significantly slower (> factor 3) than transferring
files with jsched or
tomaswolf commented on issue #504:
URL: https://github.com/apache/mina-sshd/issues/504#issuecomment-2115324310
Thanks for pointing this out.
> Would ... break anything?
No, it would not. Feel free to provide a PR.
--
This is an automated message from the Apache Git Service.
jtnord commented on issue #502:
URL: https://github.com/apache/mina-sshd/issues/502#issuecomment-2112254784
(of note BouncyCastle also supports ED25519 curves as does JDK > 15)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub
czldb2 commented on issue #493:
URL: https://github.com/apache/mina-sshd/issues/493#issuecomment-2111928811
> No idea. I just tested arcfour128 and arcfour256 against an OpenSSH 7.4
server in CentOS 7.9 (2009), and an Apache MINA SSHD 2.13.0-SNAPSHOT client
works just fine. Maybe try the
On 14.05.24 10:31 , Teki Harsha sesha sai wrote:
We are working on the project using sshd-core dependence version ( 2.12.1
), in this version we came across vulnerabilities. So when can we expect
the lastest version without vulnerabilities.
We need your support advance thanks
This is an
work-around for the reporter might be to set
`CoreModuleProperties.HEARTBEAT_REPLY_WAIT` to zero. That should work if there
is no low-level read timeout (NIO2_READ_TIMEOUT = 0).
But we should re-think this mechanism anyway. I propose to change this to
follow the path t
elecharny commented on code in PR #44:
URL: https://github.com/apache/mina/pull/44#discussion_r1597523524
##
mina-core/src/main/java/org/apache/mina/transport/socket/DefaultSocketSessionConfig.java:
##
@@ -37,7 +37,7 @@ public class DefaultSocketSessionConfig extends
jon-valliere commented on code in PR #44:
URL: https://github.com/apache/mina/pull/44#discussion_r1597516034
##
mina-core/src/main/java/org/apache/mina/transport/socket/DefaultSocketSessionConfig.java:
##
@@ -37,7 +37,7 @@ public class DefaultSocketSessionConfig extends
jon-valliere commented on code in PR #44:
URL: https://github.com/apache/mina/pull/44#discussion_r1597513918
##
mina-core/src/main/java/org/apache/mina/transport/socket/DefaultSocketSessionConfig.java:
##
@@ -37,7 +37,7 @@ public class DefaultSocketSessionConfig extends
elecharny commented on code in PR #44:
URL: https://github.com/apache/mina/pull/44#discussion_r1597513323
##
mina-core/src/main/java/org/apache/mina/transport/socket/DefaultSocketSessionConfig.java:
##
@@ -37,7 +37,7 @@ public class DefaultSocketSessionConfig extends
tomaswolf closed issue #500: Memory Leak When SftpFileSystemProvider
newInputStream get a Exception
URL: https://github.com/apache/mina-sshd/issues/500
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go
tomaswolf merged PR #501:
URL: https://github.com/apache/mina-sshd/pull/501
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
jon-valliere commented on code in PR #44:
URL: https://github.com/apache/mina/pull/44#discussion_r1597475482
##
mina-core/src/main/java/org/apache/mina/transport/socket/DefaultSocketSessionConfig.java:
##
@@ -37,7 +37,7 @@ public class DefaultSocketSessionConfig extends
elecharny commented on code in PR #44:
URL: https://github.com/apache/mina/pull/44#discussion_r1597473106
##
mina-core/src/main/java/org/apache/mina/transport/socket/DefaultSocketSessionConfig.java:
##
@@ -37,7 +37,7 @@ public class DefaultSocketSessionConfig extends
jon-valliere commented on code in PR #44:
URL: https://github.com/apache/mina/pull/44#discussion_r1597451055
##
mina-core/src/main/java/org/apache/mina/transport/socket/DefaultSocketSessionConfig.java:
##
@@ -37,7 +37,7 @@ public class DefaultSocketSessionConfig extends
jon-valliere commented on code in PR #44:
URL: https://github.com/apache/mina/pull/44#discussion_r1597451055
##
mina-core/src/main/java/org/apache/mina/transport/socket/DefaultSocketSessionConfig.java:
##
@@ -37,7 +37,7 @@ public class DefaultSocketSessionConfig extends
tomaswolf merged PR #498:
URL: https://github.com/apache/mina-sshd/pull/498
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
tomaswolf commented on issue #499:
URL: https://github.com/apache/mina-sshd/issues/499#issuecomment-2105658175
I think this was fixed in #476. Please try the 2.13.0-SNAPSHOT version
available from the [Apache
Snapshot](https://repository.apache.org/content/repositories/snapshots) maven
rich7409 commented on issue #497:
URL: https://github.com/apache/mina-sshd/issues/497#issuecomment-2104406846
Thanks for the tip. Excluding core and common and using osgi instead has
stopped it complaining about the modules.
I'll look forward to future versions with full module
rich7409 closed issue #497: Support for Java 9+ modules
URL: https://github.com/apache/mina-sshd/issues/497
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe,
but also in OSGi.
There is the `org.apache.sshd.osgi` artifact; it avoids this split package
problem by re-combining core and common into one. For OSGi that works; it might
also work for Java modules. However, if you use not OSGi with package imports
only but a plain "fat jar" pla
abhikt48 commented on issue #483:
URL: https://github.com/apache/mina-sshd/issues/483#issuecomment-2101048025
Can anyone please update on this ?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to
yaroslavambrozyak closed issue #484: AuthTimeout when connecting to SFTP server
URL: https://github.com/apache/mina-sshd/issues/484
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific
yaroslavambrozyak commented on issue #484:
URL: https://github.com/apache/mina-sshd/issues/484#issuecomment-2100706664
I have found a solution for my case
```
SshClient sshClient = SshClient.setUpDefaultClient();
CoreModuleProperties.PREFERRED_AUTHS.set(sshClient, "password");
ZhouMM92 commented on issue #496:
URL: https://github.com/apache/mina-sshd/issues/496#issuecomment-2099977859
> Look in [the
documentation](https://github.com/apache/mina-sshd/blob/master/docs/server-setup.md)
or in the tests.
Thank you very much. And I want to know which version is
tomaswolf commented on issue #496:
URL: https://github.com/apache/mina-sshd/issues/496#issuecomment-2097803412
Look in [the
documentation](https://github.com/apache/mina-sshd/blob/master/docs/server-setup.md)
or in the tests.
--
This is an automated message from the Apache Git Service.
ZhouMM92 commented on issue #496:
URL: https://github.com/apache/mina-sshd/issues/496#issuecomment-2097766522
> Compared to e.g. an OpenSSH server you will lack certain functionalities
like privilege separation or integration with the OS user management (PAM or
whatever on Linux).
>
tomaswolf commented on issue #496:
URL: https://github.com/apache/mina-sshd/issues/496#issuecomment-2097719149
Compared to e.g. an OpenSSH server you will lack certain functionalities
like privilege separation or integration with the OS user management (PAM or
whatever on Linux).
czldb2 commented on issue #493:
URL: https://github.com/apache/mina-sshd/issues/493#issuecomment-2095153169
> No idea. I just tested arcfour128 and arcfour256 against an OpenSSH 7.4
server in CentOS 7.9 (2009), and an Apache MINA SSHD 2.13.0-SNAPSHOT client
works just fine. Maybe try the
czldb2 commented on issue #493:
URL: https://github.com/apache/mina-sshd/issues/493#issuecomment-2095149600
I tried version 1.21.1 to connect and the problem still exists.
Some other phenomena I have noticed so far:
- Connecting devices on the Intranet will fail, but devices
tomaswolf commented on issue #493:
URL: https://github.com/apache/mina-sshd/issues/493#issuecomment-2094925051
No idea. I just tested arcfour128 and arcfour256 against an OpenSSH 7.4
server in CentOS 7.9 (2009), and an Apache MINA SSHD 2.13.0-SNAPSHOT client
works just fine. Maybe try the
tomaswolf commented on issue #468:
URL: https://github.com/apache/mina-sshd/issues/468#issuecomment-2094915566
I've merged a change that tightens SFTP read requests. If a server sends
back more data than requested, an exception is thrown. If you set
tomaswolf closed issue #468: Wrong content while downloading files >200Mb
URL: https://github.com/apache/mina-sshd/issues/468
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
tomaswolf merged PR #495:
URL: https://github.com/apache/mina-sshd/pull/495
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
tomaswolf commented on issue #297:
URL: https://github.com/apache/mina-sshd/issues/297#issuecomment-2094892046
@abhishekpandey96 : you need to set a `FilePasswordProvider` on the client
or directly on the `FileKeyPairProvider`. Your code just sets a password
identity, which means "use
abhishekpandey96 commented on issue #297:
URL: https://github.com/apache/mina-sshd/issues/297#issuecomment-2094684335
Hi I am trying to add a passphrase with a dsa private key path but I am
getting org.apache.sshd.common.SshException: No more authentication methods
available
at
tomaswolf merged PR #494:
URL: https://github.com/apache/mina-sshd/pull/494
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
tomaswolf commented on PR #494:
URL: https://github.com/apache/mina-sshd/pull/494#issuecomment-2094215306
Thank you, Evgeny! That looks great!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the
tomaswolf merged PR #492:
URL: https://github.com/apache/mina-sshd/pull/492
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
learncourse2024 commented on issue #489:
URL: https://github.com/apache/mina-sshd/issues/489#issuecomment-2088762945
Thank you @tomaswolf for the fix. We verified with snapshot version. It
works!!
Any approximate date when will next release be?
--
This is an automated message from
yaroslavambrozyak commented on issue #484:
URL: https://github.com/apache/mina-sshd/issues/484#issuecomment-2085160941
In the logs, I can see it is trying to use keyboard-interactive auth method
```
tryNext(ClientSessionImpl[u@h/0.0.0.0:0]) attempting
method=keyboard-interactive
czldb2 commented on issue #493:
URL: https://github.com/apache/mina-sshd/issues/493#issuecomment-2084309158
I have tried arcfour128 and other algorithms with higher security to perform
connection operation through mina-sshd component, and the connection can be
normal now.
When
czldb2 commented on issue #493:
URL: https://github.com/apache/mina-sshd/issues/493#issuecomment-2084204139
When I was debugging, I found that the parameter of the
adelel1 commented on issue #487:
URL: https://github.com/apache/mina-sshd/issues/487#issuecomment-2082386175
Hello, I have tested 2.13.0-SNAPSHOT (from Apache snapshots repo) and the
fix worked fine.
--
This is an automated message from the Apache Git Service.
To respond to the message,
czldb2 closed issue #493: I used the arcfour256 algorithm to connect to the
sshserver of mina-sshd and encountered an exception
URL: https://github.com/apache/mina-sshd/issues/493
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub
coderZoe closed issue #482: SSH Client Disconnects on Receiving Keepalive
Requests
URL: https://github.com/apache/mina-sshd/issues/482
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific
coderZoe commented on issue #482:
URL: https://github.com/apache/mina-sshd/issues/482#issuecomment-2081469942
> Basically yes, but see #492. The next version of Apache MINA SSHD will
handle these channel requests and no longer log the warning.
>
> As I wrote, I don't think your
tomaswolf commented on issue #482:
URL: https://github.com/apache/mina-sshd/issues/482#issuecomment-2081403154
Basically yes, but see #492. The next version of Apache MINA SSHD will
handle these channel requests and no longer log the warning.
As I wrote, I don't think your problem is
tomaswolf commented on PR #492:
URL: https://github.com/apache/mina-sshd/pull/492#issuecomment-2081398408
> Not displaying the warning looks weird. Wouldn’t it be cleaner to «
support » them instead and reply with a success or failure ?
Done.
--
This is an automated message from
gnodet commented on PR #492:
URL: https://github.com/apache/mina-sshd/pull/492#issuecomment-2081337561
> OpenSSH server sends keep-alive requests as channel requests if a channel
is open. Do not log a warning about such requests, simply send back a failure
reply. OpenSSH just expects any
coderZoe commented on issue #482:
URL: https://github.com/apache/mina-sshd/issues/482#issuecomment-2081290796
> Setting a "global request" handler for keep-alives has only an effect on
global requests. It has no effect on channel requests. OpenSSH prefers to send
keep-alive messages a
tomaswolf commented on issue #482:
URL: https://github.com/apache/mina-sshd/issues/482#issuecomment-2081169948
Setting a "global request" handler for keep-alives has only an effect on
global requests. It has no effect on channel requests. OpenSSH prefers to send
keep-alive messages a
tomaswolf commented on issue #489:
URL: https://github.com/apache/mina-sshd/issues/489#issuecomment-2081158730
@learncourse2024 : please try the snapshot release from the [Apache
Snapshots](https://repository.apache.org/content/repositories/snapshots)
repository. It should be able to
tomaswolf closed pull request #35: [SSHD-758] Add
OpenSSHGeneratorFileKeyProvider
URL: https://github.com/apache/mina-sshd/pull/35
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific
tomaswolf commented on PR #35:
URL: https://github.com/apache/mina-sshd/pull/35#issuecomment-2081119980
Closing old outdated PRs.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific
tomaswolf commented on PR #73:
URL: https://github.com/apache/mina-sshd/pull/73#issuecomment-2081119733
Closing old outdated PRs.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific
tomaswolf closed pull request #73: [SSHD-851] Last chunk of data lost into
local port forwarding channel
URL: https://github.com/apache/mina-sshd/pull/73
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to
tomaswolf commented on PR #60:
URL: https://github.com/apache/mina-sshd/pull/60#issuecomment-2081119607
Closing old outdated PRs.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific
tomaswolf closed pull request #60: Gc socks timing
URL: https://github.com/apache/mina-sshd/pull/60
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
tomaswolf closed issue #427: DefaultScpClient.upload(InputStream, ...) will
always hit the exit status timeout
URL: https://github.com/apache/mina-sshd/issues/427
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
tomaswolf merged PR #464:
URL: https://github.com/apache/mina-sshd/pull/464
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
tomaswolf merged PR #486:
URL: https://github.com/apache/mina-sshd/pull/486
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
tomaswolf closed issue #489: sshd-sftp - Not able to get files from windows
server
URL: https://github.com/apache/mina-sshd/issues/489
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific
tomaswolf merged PR #491:
URL: https://github.com/apache/mina-sshd/pull/491
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
learncourse2024 commented on issue #489:
URL: https://github.com/apache/mina-sshd/issues/489#issuecomment-2079523538
Thank you @tomaswolf for explaining it.
Will there be any fix for this issue which will be worked on in MINA
--
This is an automated message from the Apache Git
tomaswolf commented on issue #489:
URL: https://github.com/apache/mina-sshd/issues/489#issuecomment-2079135725
> ... its "longname" looks strange. I would have expected it to start with
"-rw-rw-rw-", not with "-rw-rw-rw ". ...
This was mentioned in a [SolarWinds
adelel1 commented on issue #455:
URL: https://github.com/apache/mina-sshd/issues/455#issuecomment-2079134522
Hi @tomaswolf
I should have mentioned I did rebuild and test, and it worked fine. I have
just tried again using the Apache Snapshot Repository and works fine. Thanks,
Would be
tomaswolf commented on issue #489:
URL: https://github.com/apache/mina-sshd/issues/489#issuecomment-2078224203
OK. Findings:
1. This server sends longname as `-rw-rw-rw 1 root root 1944
Apr 24 14:58 demo.csv` (just before offset 288)
2. This is then followed by flags
learncourse2024 commented on issue #489:
URL: https://github.com/apache/mina-sshd/issues/489#issuecomment-2078113498
So here are the details which i found while debugging
LongName - -rw-rw-rw 1 root root 1944 Apr 24 14:58 demo.csv
ByteArrayBuffer[rpos=288, wpos=320,
tomaswolf commented on issue #489:
URL: https://github.com/apache/mina-sshd/issues/489#issuecomment-2077649433
Possibly that SFTP server has a bug?
It's a bit unclear what we could do. Probably the directory scanner should
not return only directories and regular files but also do
learncourse2024 commented on issue #489:
URL: https://github.com/apache/mina-sshd/issues/489#issuecomment-2077389757
SolarWinds Sftp Server
File transfer protocol = SFTP-3
Cryptographic protocol = SSH-2
SSH implementation = WeOnlyDo 2.5.5
Compression = No
--
This is an
tomaswolf commented on issue #489:
URL: https://github.com/apache/mina-sshd/issues/489#issuecomment-2077338195
Yes, if the server doesn't send any of these flags then the file type is
unknown.
What kind of SFTP server is this?
--
This is an automated message from the Apache Git
learncourse2024 commented on issue #489:
URL: https://github.com/apache/mina-sshd/issues/489#issuecomment-2077247442
Its SFTP version 3
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the
merlynee commented on issue #490:
URL: https://github.com/apache/mina-sshd/issues/490#issuecomment-2076677383
> I'm not here to debug your code. I do notice, however, that you call
`shellChannelExec.open()` twice.
Thanks somuch fellow.!!!
--
This is an automated message from the
tomaswolf commented on issue #484:
URL: https://github.com/apache/mina-sshd/issues/484#issuecomment-2076657250
No idea. Try enabling debug logging and see if the log gives any hints.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
tomaswolf closed issue #490: a problem when ChannelExec
warned:handleEof-someInfo-already signalled
URL: https://github.com/apache/mina-sshd/issues/490
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go
tomaswolf commented on issue #490:
URL: https://github.com/apache/mina-sshd/issues/490#issuecomment-2076566405
I'm not here to debug your code. I do notice, however, that you call
`shellChannelExec.open()` twice.
--
This is an automated message from the Apache Git Service.
To respond to
tomaswolf commented on issue #489:
URL: https://github.com/apache/mina-sshd/issues/489#issuecomment-2075910029
Decimal 438 is octal 666 (hex 1B6) and thus reflects the rw-rw-rw-
permissions correctly. But it looks as if the server does not return the file
type flags. It's supposed to
Holger-Benz commented on issue #485:
URL: https://github.com/apache/mina-sshd/issues/485#issuecomment-2072475600
I'm sorry, you're right. We will open a new issue when we have the relevant
debug data.
--
This is an automated message from the Apache Git Service.
To respond to the message,
tomaswolf commented on issue #485:
URL: https://github.com/apache/mina-sshd/issues/485#issuecomment-2072445000
> Any thoughts on my above comment especially on """ Is there any way to
force/override the file upload/download in sftp sessions through put/get
commands to use Files.copy() way
tomaswolf commented on issue #485:
URL: https://github.com/apache/mina-sshd/issues/485#issuecomment-2072436702
> The SSHD-server is also integrated in our communication software.
The original report was about the client side. Whatever this may be, it
would be a new separate issue.
tomaswolf commented on issue #488:
URL: https://github.com/apache/mina-sshd/issues/488#issuecomment-2072420855
Not enough information. Upgrade from what version? Try switching on DEBUG
level logging; maybe that gives some clues.
--
This is an automated message from the Apache Git
leild commented on issue #488:
URL: https://github.com/apache/mina-sshd/issues/488#issuecomment-2072341741
org.apache.sshd.common.SshException: Timeout expired while waiting for id=10
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on
Holger-Benz commented on issue #485:
URL: https://github.com/apache/mina-sshd/issues/485#issuecomment-2072068018
The SSHD-server is also integrated in our communication software.
After updating the server from version 2.4.0 to 2.12.1, the communication of
the server has become
tomaswolf commented on issue #455:
URL: https://github.com/apache/mina-sshd/issues/455#issuecomment-2068139015
@adelel1 : could you please try your application with the 2.13.0-SNAPSHOT
versions available in the [Apache Snapshots
kvlnkarthik commented on issue #485:
URL: https://github.com/apache/mina-sshd/issues/485#issuecomment-2066830425
@tomaswolf ,
Any thoughts on my above comment especially on
"""
Is there any way to force/override the file upload/download in sftp sessions
through put/get commands to
;; Author ***@***.***>
Betreff: Re: [apache/mina-sshd] Perfomance file transfer (Issue #485)
We see same issue in our tests as well. We are using 2.12.1 version.
We executed filetransfer test case using Files.copy() approach for
transferring a file of about 167Mb to a remote server and to
kvlnkarthik commented on issue #485:
URL: https://github.com/apache/mina-sshd/issues/485#issuecomment-2061827392
We see same issue in our tests as well. We are using 2.12.1 version.
We executed filetransfer test case using Files.copy() approach for
transferring a file of about 167Mb
tomaswolf commented on issue #485:
URL: https://github.com/apache/mina-sshd/issues/485#issuecomment-2060039475
After some analysis, here's what's going on:
transferTo/transferFrom, as well as the FileChannel.write() operations, are
_positional_ operations.
tomaswolf commented on issue #485:
URL: https://github.com/apache/mina-sshd/issues/485#issuecomment-2059973935
Interesting: if you change in your code
```
readableChannel.transferTo(0, length, writeableChannel);
```
to
```
writeableChannel.transferFrom(readableChannel, 0,
tomaswolf commented on issue #485:
URL: https://github.com/apache/mina-sshd/issues/485#issuecomment-2059918256
Thank you for this test case. It appears that there is indeed something
wrong with the `FileChannel`s. The following is in my tests much faster (and on
par with OpenSSH or Jsch):
nightman68 commented on PR #477:
URL: https://github.com/apache/mina-sshd/pull/477#issuecomment-2057631021
Sorry, I do not have the time at the moment getting familiar with your test
suite etc.
--
This is an automated message from the Apache Git Service.
To respond to the message, please
adelel1 commented on issue #455:
URL: https://github.com/apache/mina-sshd/issues/455#issuecomment-2051557359
Hello @tomaswolf
Firstly thanks for quickly resolving and fixing this issue. We have also
just hit this issue. We have switched to the LTS version of BC. I am wondering
when
tomaswolf commented on issue #481:
URL: https://github.com/apache/mina-sshd/issues/481#issuecomment-2048214147
Debug time :-)
I've used and tested this only in Eclipse, which uses the NIO2 transport. I
have no idea why the MINA transport doesn't do the write.
--
This is an
Holger-Benz commented on issue #481:
URL: https://github.com/apache/mina-sshd/issues/481#issuecomment-2047445089
I downloaded the JGitSshClient version 2.1.12 and tested the communication
via a proxy and the communication worked!
TThe problem occurs when I configure the IOFactory for
tomaswolf commented on issue #481:
URL: https://github.com/apache/mina-sshd/issues/481#issuecomment-2045884711
I don't have a setup where I could test this with 2.12.1. But with 2.12.0
the JGit way of doing this works fine in Eclipse.
I used `ssh -vvv -D7020 localhost` as local SOCKS
tomaswolf commented on issue #480:
URL: https://github.com/apache/mina-sshd/issues/480#issuecomment-2042182161
No, there are currently no such plans. Also from JEP-444:
> In a future release we may be able to remove the first limitation above,
namely pinning inside synchronized.
tomaswolf merged PR #472:
URL: https://github.com/apache/mina-sshd/pull/472
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
101 - 200 of 11539 matches
Mail list logo
