[
https://issues.apache.org/jira/browse/SSHD-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17268668#comment-17268668
]
Lyor Goldstein commented on SSHD-1119:
--------------------------------------
{quote}
it may be writing to different location in packet which is correct according
new standards and lastest clients like Filezilla and WinScp are able to get the
proper message, may be Putty and other SSH clients are failing as they are
reading the buffer from wrong location on data packets.
{quote}
I doubt that very much as this packet structure has not changed since v3.0. In
any case, even if you are right (which is doubtful) it is still not a bug -
maybe a feature request. In which case, please provide documentation of the
expected format.
{quote}
Maverick commercial library works fine in propagating the message back to the
Putty
{quote}
Maverick is a +non-standard+ library - we have encountered issues with it in
the past and up until now it turned out it was doing something that is not
documented or not according to the standard. If you can extract the code that
you claim works from it then please provide it and we'll see.
> SftpErrorStatusDataHandler resolveErrorMessage is not propagating back the
> custom message to the SSH client
> -----------------------------------------------------------------------------------------------------------
>
> Key: SSHD-1119
> URL: https://issues.apache.org/jira/browse/SSHD-1119
> Project: MINA SSHD
> Issue Type: Bug
> Reporter: Susmit Sarkar
> Priority: Major
> Attachments: image-2021-01-19-10-29-49-958.png,
> image-2021-01-19-14-01-55-257.png
>
>
> SftpErrorStatusDataHandler resolveErrorMessage() is not propagating back the
> custom message to the SSH client like PUTY, although it works fine with
> FileZilla or WinScp. Am I doing anything wrong or is it a bug in the lilbrary
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
