Greetings all,
I'm a little bit confused.
I've created an elementary sshd server*.
Deployed it to openBSD device.
Connected to it through putty, successfully logged in.
And then... nothing.
I mean for every symbol I type I'm getting next info on server (
http://prntscr.com/8t1ol
Original Message-
From: Влад Сурагин [mailto:v.sura...@mail.ru]
Sent: Monday, October 19, 2015 21:21
To: dev@mina.apache.org
Subject: SSHD Server
Greetings all,
I'm a little bit confused.
I've created an elementary sshd server*.
Deployed it to openBSD device.
Connected to it through putty, su
Hi,
I have a general Question about the PublickeyAuthenticator - it's an interface
and I haven't found any sample implementation of it.
I have public keys from a client application that should connect to my server.
I can put them in the .ssh/authenticated_keys file or store them separately. If
On Mon, Oct 18, 2010 at 14:24, wrote:
> I have a general Question about the PublickeyAuthenticator - it's an
> interface and I haven't found any sample implementation of it.
> I have public keys from a client application that should connect to my
> server. I can put them in the .ssh/authenticat
Roberto Deandrea created SSHD-1215:
--
Summary: WinsCP transfer failure to Apache SSHD Server
Key: SSHD-1215
URL: https://issues.apache.org/jira/browse/SSHD-1215
Project: MINA SSHD
Issue Type
endo risposta.
Riferimento al Jira https://issues.apache.org/jira/browse/SSHD-1215
> WinsCP transfer failure to Apache SSHD Server
> -
>
> Key: SSHD-1215
> URL: https://issues.apache.org/ji
high bytes of the data length (also
zero, since the full length is 00 00 7f c0).
> WinsCP transfer failure to Apache SSHD Server
> -
>
> Key: SSHD-1215
> URL: https://issues.apache.org/jira/browse/SSHD-1215
&g
tion < 0L) {_
_posTracker.set(curPos);_
_}_
_endBlocking("doWrite", completed);_
_}_
_}_
Can you check the source code and evaluate if you can fix it in a future
release of Apache SSHD or can you suggest us a workaround ?
Thank in advance
Roberto
>
[
https://issues.apache.org/jira/browse/SSHD-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roberto Deandrea updated SSHD-1215:
---
Priority: Blocker (was: Major)
> WinsCP transfer failure to Apache SSHD Ser
that shows this error? A JUnit
test would be great.
> WinsCP transfer failure to Apache SSHD Server
> -
>
> Key: SSHD-1215
> URL: https://issues.apache.org/jira/browse/SSHD-1215
> Project: MINA
d, when WinSCP writea a *NEW* file to Apache SSHD server, it is opening
*ALWAYS* the file in *APPEND* mode (not in WRITE mode which should be the
defualt for a new file).
In this case *channel.size() is ALWAYS 0* because the file is *NEW*, and this
causes the +issue+ I reported,
nside a single Java process.
> WinsCP transfer failure to Apache SSHD Server
> -
>
> Key: SSHD-1215
> URL: https://issues.apache.org/jira/browse/SSHD-1215
> Project: MINA SSHD
> Issu
ing code and WinSCP is working fine.
public boolean isOpenAppend() {
return openOptions.contains(StandardOpenOption.APPEND);
}
I think this is the right code, and it fixes the problem with WinSCP.
Can you comment on this ?
> WinsCP transfer failure to Apache
antime.
> WinsCP transfer failure to Apache SSHD Server
> -
>
> Key: SSHD-1215
> URL: https://issues.apache.org/jira/browse/SSHD-1215
> Project: MINA SSHD
> Issue Type: Bug
&
our front-end SSHD server. There when
theFileHandle.isOpenAppend() is instantiated the file is open in APPEND mode!!!
THIS IS WRONG! The file MUST be opened in WRITE mode as requested by WinSCP
client.
The following implementation is WRONG!!!
*public boolean isOpenAppend()*
*{*
*re
bit more consistent in Apache MINA sshd
would require more tests for the "append" case in our test suite.)
> WinsCP transfer failure to Apache SSHD Server
> -
>
> Key: SSHD-1215
> URL: https://i
have an effect even if SSH_FXF_APPEND_DATA is not set). It's
not clear to me how we should deal with this.
> WinsCP transfer failure to Apache SSHD Server
> -
>
> Key: SSHD-1215
> URL: https:
ND even if
SSH_FXF_APPEND_DATA is specified but always manages the "append" logic itself.
> WinsCP transfer failure to Apache SSHD Server
> -
>
> Key: SSHD-1215
> URL: https://issues.apache
pull/203] is my take on this.
Unresolved: old Apache MINA sshd clients, which send only ACE4_APPEND_DATA in
SFTP version >= 5 without also sending SSH_FXF_APPEND_DATA. Not sure it
matters; seems to me that behavior was broken anyway.
> WinsCP transfer failure to Apache S
tten. Some statements could be right and some
statements could be wrong. This is not so important.
But the issue remains, a WinSCP client cannot put a file onto Apache SSHD
server in the scenario described and you did not give a solution for that.
Bye
Roberto
> WinsCP transfer fai
lure to Apache SSHD Server
> -
>
> Key: SSHD-1215
> URL: https://issues.apache.org/jira/browse/SSHD-1215
> Project: MINA SSHD
> Issue Type: Bug
>Affects Versions: 2.6.0
>
you decide to insert
[https://github.com/apache/mina-sshd/pull/203] code changes into your next
release of Apache SSHD.
Regards
Roberto
> WinsCP transfer failure to Apache SSHD Server
> -
>
> Key: SSHD-1215
>
ould confirm or deny that this
solves the problem.
> WinsCP transfer failure to Apache SSHD Server
> -
>
> Key: SSHD-1215
> URL: https://issues.apache.org/jira/browse/SSHD-1215
> Project: MINA
anks!
Roberto
> WinsCP transfer failure to Apache SSHD Server
> -
>
> Key: SSHD-1215
> URL: https://issues.apache.org/jira/browse/SSHD-1215
> Project: MINA SSHD
> Issue Type: Bug
>
ards
Roberto
> WinsCP transfer failure to Apache SSHD Server
> -
>
> Key: SSHD-1215
> URL: https://issues.apache.org/jira/browse/SSHD-1215
> Project: MINA SSHD
> Issue Type:
[
https://issues.apache.org/jira/browse/SSHD-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Wolf reassigned SSHD-1215:
-
Assignee: Thomas Wolf
> WinsCP transfer failure to Apache SSHD Ser
[
https://issues.apache.org/jira/browse/SSHD-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Wolf resolved SSHD-1215.
---
Fix Version/s: 2.7.1
Resolution: Fixed
> WinsCP transfer failure to Apache SSHD Ser
the right place to ask this kind of question but I did
not find any right place for that.
Do you know when is scheduled the release of next Apache SSHD version (a.k.a
2.7.1) ?
Kind Regards
Roberto
> WinsCP transfer failure to Apache SSHD
vide something for SSHD-1226, but then I think we'd be good to go.
> WinsCP transfer failure to Apache SSHD Server
> -
>
> Key: SSHD-1215
> URL: https://issues.apache.org/jira/browse/SSHD-121
onse!
Bye
Roberto
> WinsCP transfer failure to Apache SSHD Server
> -
>
> Key: SSHD-1215
> URL: https://issues.apache.org/jira/browse/SSHD-1215
> Project: MINA SSHD
> Issue Type:
for SSHD-1226 by the end of next week.
After that, barring any unforeseen issues I have no extra features/bugs that I
am keen on adding to this release, so we might be calling for a vote on a new
release by early December...
> WinsCP transfer failure to Apache SSHD
ards
Roberto
> WinsCP transfer failure to Apache SSHD Server
> -
>
> Key: SSHD-1215
> URL: https://issues.apache.org/jira/browse/SSHD-1215
> Project: MINA SSHD
> Issue Type:
I am setting up a custom SSH server using Apache SSHD which interacts with
web services, and depending on the web service response the file will be
stored or discarded.
Following is my use case:
All users have some limits to upload file into the system.
If user tries to upload a file, i am hitti
1 AM:
--
.
was (Author: roberto.deandrea):
Chiesto supporto ad Apache SSHD. Attendo risposta.
Riferimento al Jira https://issues.apache.org/jira/browse/SSHD-1215
> WinsCP transfer failure to Apache SSHD Server
> -
>
>
WinSCP.
Can you comment on this ?
> WinsCP transfer failure to Apache SSHD Server
> -
>
> Key: SSHD-1215
> URL: https://issues.apache.org/jira/browse/SSHD-1215
> Project: MINA SSHD
>
nfra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 663207)
Remaining Estimate: 0h
Time Spent: 10m
> WinsCP transfer failure to Apache SSHD Server
> -
>
> Key: SSHD-1215
>
Li Fangning created SSHD-722:
Summary: Failed to setting SO_KEEPALIVE option for sshd server
socket
Key: SSHD-722
URL: https://issues.apache.org/jira/browse/SSHD-722
Project: MINA SSHD
Issue
[
https://issues.apache.org/jira/browse/SSHD-722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Goldstein Lyor reassigned SSHD-722:
---
Assignee: Goldstein Lyor
> Failed to setting SO_KEEPALIVE option for sshd server soc
.
> Failed to setting SO_KEEPALIVE option for sshd server socket
>
>
> Key: SSHD-722
> URL: https://issues.apache.org/jira/browse/SSHD-722
> Project: MINA SSHD
>
t; using property '" + property + "' value=" + val
+ ": " + e.getMessage());
}
}
{code}
> Failed to setting SO_KEEPALIVE option for sshd server socket
>
>
>
be resolved in future version.
Best regards.
> Failed to setting SO_KEEPALIVE option for sshd server socket
>
>
> Key: SSHD-722
> URL: https://issues.apache.org/jira/browse/SSHD-722
>
iled to setting SO_KEEPALIVE option for sshd server socket
>
>
> Key: SSHD-722
> URL: https://issues.apache.org/jira/browse/SSHD-722
> Project: MINA SSHD
> Issue Type:
channel
> Failed to setting SO_KEEPALIVE option for sshd server socket
>
>
> Key: SSHD-722
> URL: https://issues.apache.org/jira/browse/SSHD-722
> Project: MINA SSHD
>
EPALIVE option for sshd server socket
>
>
> Key: SSHD-722
> URL: https://issues.apache.org/jira/browse/SSHD-722
> Project: MINA SSHD
> Issue Type: Bug
>
Marcin Kozakiewicz created SSHD-733:
---
Summary: SSHD server creates file symlinks instead of dir symlinks
Key: SSHD-733
URL: https://issues.apache.org/jira/browse/SSHD-733
Project: MINA SSHD
tween file and directory symlinks.
> SSHD server creates file symlinks instead of dir symlinks
> -
>
> Key: SSHD-733
> URL: https://issues.apache.org/jira/browse/SSHD-733
> Project:
[
https://issues.apache.org/jira/browse/SSHD-733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Goldstein Lyor updated SSHD-733:
Priority: Minor (was: Major)
> SSHD server creates file symlinks instead of dir symli
[
https://issues.apache.org/jira/browse/SSHD-733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Goldstein Lyor updated SSHD-733:
Summary: SSHD server displays file symlinks instead of dir symlinks (was:
SSHD server creates file
[
https://issues.apache.org/jira/browse/SSHD-733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Goldstein Lyor updated SSHD-733:
Issue Type: Wish (was: Bug)
> SSHD server creates file symlinks instead of dir symli
H-2.0-OpenSSH_7.4p1 Debian-6
{code}
OpenSSH lists the contents of symlinked directory while mina returns
SSH_FX_NOT_A_DIRECTORY.
The same behavior can be observer using different client (sftp).
I'm not sure which behavior is the correct one though.
> SSHD server displays file symlinks i
} else {
String handle = generateFileHandle(p);
DirectoryHandle dirHandle = new DirectoryHandle(this, p, handle);
handles.put(handle, dirHandle);
return handle;
}
}
{code}
Seems that {{Files.isDirectory(p, options}} returns {{false}}, so I don'
mmit/cccec812bf9a0571da7bffee651e9c741c402e39
Maybe we can just flip it back?
[~kozzakko] can you check, if it would help in your case? You can also try
providing your own FileSystem which will disregard this option.
> SSHD server displays file symlinks instead of dir s
n is whether it is the *right* thing to
do. I am not so sure that we always want to follow symbolic links, nor that it
is in accordance with the letter or spirit of SFTP. Perhaps a configurable
behavior or sub-classed one would be more appropriate.
Any thoughts ?
> SSHD server displays file s
nges server works as expected:
{code}
diff --git
a/sshd-core/src/main/java/org/apache/sshd/server/subsystem/sftp/SftpSubsystem.java
b/sshd-core/src/main/java/org/apache/sshd/server/subsystem/sftp/SftpSubsystem.java
index 120f0c0..1e70f13 100644
---
a/sshd-core/src/main/java/org/apache/sshd/se
blem, but the question remains whether
this fix is good for everybody...
> SSHD server displays file symlinks instead of dir symlinks
> --
>
> Key: SSHD-733
> URL: https://issues.apache.org/j
much more likely that
someone will face regression moving to current Mina version.
> SSHD server displays file symlinks instead of dir symlinks
> --
>
> Key: SSHD-733
> URL: https
d it as a *configurable* option (in
case someone encounters an error and needs to restore the current
implementation) with the default set to follow links,
> SSHD server displays file symlinks instead of dir symlinks
> --
>
>
[
https://issues.apache.org/jira/browse/SSHD-733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Goldstein Lyor reassigned SSHD-733:
---
Assignee: Goldstein Lyor
> SSHD server displays file symlinks instead of dir symli
13|https://tools.ietf.org/html/draft-ietf-secsh-filexfer-13]
{quote}
SSH_FXP_STAT and SSH_FXP_LSTAT only differ in that SSH_FXP_STAT follows
symbolic links on the server, whereas SSH_FXP_LSTAT does not
{quote}
I.e., the configured value will *not* apply to these commands.
> SSHD server displa
[
https://issues.apache.org/jira/browse/SSHD-733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Goldstein Lyor resolved SSHD-733.
-
Resolution: Fixed
Fix Version/s: 1.5.0
> SSHD server displays file symlinks instead of
2 piotrpiotr4096 Apr 3 19:51 a
drwxr-xr-x 2 piotrpiotr4096 Apr 3 19:51 b
{code}
I will try to debug this further if I find the time.
> SSHD server displays file symlinks instead of dir symlinks
> --
>
>
inks as *not* followed on listed
children of a folder - please see if this improves the result.
> SSHD server displays file symlinks instead of dir symlinks
> --
>
> Key: SSHD-733
> URL: https:
for my test cases, i.e.
- directory symlinks are displayed correctly ,
- symlinks follow to correct locations and proper files are downloaded,
- ls displays symlinks with destination they point to.
Thank you.
> SSHD server displays file symlinks instead of dir s
[
https://issues.apache.org/jira/browse/SSHD-733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet updated SSHD-733:
-
Fix Version/s: (was: 1.5.0)
1.6.0
> SSHD server displays file symli
Li Fangning created SSHD-793:
Summary: Continuously connecting to sshd server lead to memory
leaks
Key: SSHD-793
URL: https://issues.apache.org/jira/browse/SSHD-793
Project: MINA SSHD
Issue
[
https://issues.apache.org/jira/browse/SSHD-793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Goldstein Lyor resolved SSHD-793.
-
Resolution: Incomplete
> Continuously connecting to sshd server lead to memory le
the middle. To really declare that SSHD server leaks
you need to run a more realistic scenario over a (much) longer time. There may
be a leak, but this very simple code does not indicate it... closing the issue
- please feel free to re-open if a more realistic scenario can be used to
[
https://issues.apache.org/jira/browse/SSHD-793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Li Fangning updated SSHD-793:
-
Attachment: changes.png
> Continuously connecting to sshd server lead to memory le
e my customer deployed our sshd server behind the
load-balanced device, and the device performs a service availability check
every second. After a few days, our sshd server runs out of memory.
We analyzed the LB device's checking behavior and wrote code to reproduce the
problem, th
[
https://issues.apache.org/jira/browse/SSHD-793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Li Fangning reopened SSHD-793:
--
> Continuously connecting to sshd server lead to memory le
view the code - it would help if you
could explain what was the leak and how your proposed code change fixes it.
> Continuously connecting to sshd server lead to memory leaks
> ---
>
> Key: SSHD-793
>
uest:
https://github.com/apache/mina-sshd/pull/43
[SSHD-793] Fix the memory leak issue of sshd server
[SSHD-793] Fix the memory leak issue of continuing to connect and
disconnect to sshd.
You can merge this pull request into a Git repository by running:
$ git pull https://github
code.
https://github.com/apache/mina-sshd/pull/43
Thanks.
> Continuously connecting to sshd server lead to memory leaks
> ---
>
> Key: SSHD-793
> URL: https://issues.apache.org/jira/browse/SSHD-793
&g
g it - however, it is not clear how the
leak occurs and why this code fixes it... can you elaborate on the scenario you
think is causing the leak ?
Thanks.
> Continuously connecting to sshd server lead to memory leaks
> ---
>
>
session.getId();
sessions.put(sessionId, session);
future.setSession(session);
session.startReading();
{code}
Shouldn't we do the same ?
> Continuously connecting to sshd serve
[
https://issues.apache.org/jira/browse/SSHD-793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Goldstein Lyor reassigned SSHD-793:
---
Assignee: Goldstein Lyor
> Continuously connecting to sshd server lead to memory le
[
https://issues.apache.org/jira/browse/SSHD-793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Goldstein Lyor resolved SSHD-793.
-
Resolution: Fixed
Fix Version/s: 1.7.0
> Continuously connecting to sshd server lead
lion times of connecting/disconnecting with the
new compiled version, the problem is gone.
Thank you.
> Continuously connecting to sshd server lead to memory leaks
> ---
>
> Key: SSHD-793
>
made it "under the wire" - be on the
lookout for it...
> Continuously connecting to sshd server lead to memory leaks
> ---
>
> Key: SSHD-793
> URL: https://issues.ap
uest:
https://github.com/apache/mina-sshd/pull/43
[SSHD-793] Fix the memory leak issue of sshd server
[SSHD-793] Fix the memory leak issue of continuing to connect and
disconnect to sshd.
You can merge this pull request into a Git repository by running:
$ git pull https://github
uest at:
https://github.com/apache/mina-sshd/pull/43
> Continuously connecting to sshd server lead to memory leaks
> ---
>
> Key: SSHD-793
> URL: https://issues.apache.org/j
uest at:
https://github.com/apache/mina-sshd/pull/43
> Continuously connecting to sshd server lead to memory leaks
> ---
>
> Key: SSHD-793
> URL: https://issues.apache.org/j
ting to sshd server lead to memory leaks
> ---
>
> Key: SSHD-793
> URL: https://issues.apache.org/jira/browse/SSHD-793
> Project: MINA SSHD
> Issue Type: Bug
>
[
https://issues.apache.org/jira/browse/SSHD-722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on SSHD-722 started by Goldstein Lyor.
---
> Failed to setting SO_KEEPALIVE option for sshd server soc
[
https://issues.apache.org/jira/browse/SSHD-722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on SSHD-722 stopped by Goldstein Lyor.
---
> Failed to setting SO_KEEPALIVE option for sshd server soc
[
https://issues.apache.org/jira/browse/SSHD-733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on SSHD-733 started by Goldstein Lyor.
---
> SSHD server displays file symlinks instead of dir symli
uote}
SSH_FXP_STAT and SSH_FXP_LSTAT only differ in that SSH_FXP_STAT follows
symbolic links on the server, whereas SSH_FXP_LSTAT does not
{quote}
I.e., the configured value will *not* apply to these commands.
> SSHD server displays file symlinks instead of dir s
Hi, Goldstein
We found this problem because my customer deployed our sshd server behind the
load-balanced device, and the device performs a service availability check
every second. After a few days, our sshd server runs out of memory.
We analyzed the LB device's checking behavior and wrot
isClosing()}} is consulted ?
Thanks.
was (Author: lgoldstein):
Looks fine and I have no problem merging it - however, it is not clear how the
leak occurs and why this code fixes it... can you elaborate on the scenario you
think is causing the leak ?
Thanks.
> Continuously connecting to sshd
[
https://issues.apache.org/jira/browse/SSHD-951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sivanagarajup updated SSHD-951:
---
Summary: Query on how to restart sshd server in single jboss session (was:
Query on "Can not
can say is that if you +absolutely must+ stop the server
then there is no recourse other than creating a +new instance+ of it,
configuring it and then starting it.
> Query on how to restart sshd server in single jboss session
> --
We will try with creating new instance and configuring it.
Thanks
siva
> Query on how to restart sshd server in single jboss session
> ---
>
> Key: SSHD-951
> URL: https://issues.apache.org/j
[
https://issues.apache.org/jira/browse/SSHD-951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lyor Goldstein resolved SSHD-951.
-
Resolution: Workaround
> Query on how to restart sshd server in single jboss sess
ated new sshd instance and configured it, now able to
stop/start sshd server in single jboss session.
But after restarting sshd server not able to connect to it, getting following
error
{code:java}
[root@svc-4-bnsiserv conf]# ssh administrator@localhost -p
nd
then use a {{FileKeyPairProvider}} or {{ClassLoadableResourceKeyPairProvider}}
to point to these files when you call {{setHostKeyProvider}}
> Query on how to restart sshd server in single jboss session
> ---
>
> Key: SSHD-951
&g
onse.
We tried by setting same old keyprovider for new sshd instance, now able to
start ssh session after every restart.
We will post if any other issues on this way.
Regards
Siva
> Query on how to restart sshd server in single jboss
know the use of implementing interface
*org.apache.sshd.server.shell.ShellFactory*
and setting to sshd server like
*sshd.setShellFactory(new ProcessShellFactory(new String[] \{ "/bin/sh", "-i",
"-l" }));*
Thanks
Siva
> Query on how to restar
tive SSH session simply don't provide a shell factory (i.e., don't call
the {{setShellFactory}} method.
> Query on how to restart sshd server in single jboss session
> ---
>
> Key: SSHD-951
>
SSH supported standards for version sshd 2.2.0
like for 2.2.3 ([https://github.com/apache/mina-sshd/blob/sshd-2.3.0/README.md])
Thanks
Siva
> Query on how to restart sshd server in single jboss session
> ---
>
>
the same - see
https://github.com/apache/mina-sshd/blob/master/docs/changes/2.3.0.md for any
extra supported features that were introduced only in 2.3.0
> Query on how to restart sshd server in single jboss session
> ---
>
>
1 - 100 of 169 matches
Mail list logo
