[
https://issues.apache.org/jira/browse/NIFI-9509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17463426#comment-17463426
]
ASF subversion and git services commented on NIFI-9509:
-------------------------------------------------------
Commit 9747d6a410441bba6e8a7da6c60041b5b8d7fb3f in nifi's branch
refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=9747d6a ]
NIFI-9509 This closes #5618. Added PatchedSFTPEngine to correct SFTP rename
flags handling
- SSHJ 0.32.0 introduced support for rename flags in SFTP commands without
checking the protocol version
- PatchedSFTPEngine overrides the rename method to check the SFTP protocol
version
Signed-off-by: Joe Witt <[email protected]>
> Upgrade to SSHJ 0.32 introduces a SFTP renaming issue with AWS SFTP Transfer
> Family
> -----------------------------------------------------------------------------------
>
> Key: NIFI-9509
> URL: https://issues.apache.org/jira/browse/NIFI-9509
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.15.0, 1.15.1
> Environment: Apache NIFI Docker image tag 1.15.1.
> Reporter: Steve
> Assignee: David Handermann
> Priority: Major
> Fix For: 1.16.0, 1.15.2
>
> Attachments: error_log.txt
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> We have a NIFI process that uses the SFTP processor to put files to an AWS
> Transfer family SFTP server. The "dot file rename" option is enabled on this
> processor.
> This has been working for some time on NIFI 1.14.0 and following the upgrade
> to 1.15.1 it now continually fails with a read timeout. If the "dot file
> rename" option is disabled on this processor then the SFTP put works ok.
> This appears to be an issue with the underlying SSHJ 0.32 that was upgraded
> in NIFI-9303. Release 0.32 includes support for SFTP rename flags which as a
> SFTP V5+ feature. Unfortunately SSHJ supports a max version of 3 so there is
> a bit of unpicking to be had here. The impact is that all rename packets will
> contain a rogue uint32 at the end, which may or may not cause issues
> depending on how the server handles badly formed or unexpected content in V3
> packets.
> There are two issues on SSHJ GitHub issues relating to this.
> [https://github.com/hierynomus/sshj/issues/751]
> [https://github.com/hierynomus/sshj/issues/750]
>
> Example failure log attached.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
