[ 
https://issues.apache.org/jira/browse/NIFI-14720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18004453#comment-18004453
 ] 

Michael W Moser commented on NIFI-14720:
----------------------------------------

Looking forward to this, SSHJ has demonstrated throughput deficiencies.

> Switch to Apache MINA SSHD for SFTP Processors
> ----------------------------------------------
>
>                 Key: NIFI-14720
>                 URL: https://issues.apache.org/jira/browse/NIFI-14720
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: David Handermann
>            Assignee: David Handermann
>            Priority: Major
>
> NiFi SFTP Processors have used the [SSHJ|https://github.com/hierynomus/sshj] 
> library for the last several years, following a migration from JSch. Although 
> SSHJ continues to receive regular maintenance, [Apache MINA 
> SSHD|https://mina.apache.org/sshd-project/] also provides robust and 
> extensible support for SSH and SFTP. NiFi has used MINA SSHD server 
> components for unit testing over several years. Moving from SSHJ to MINA SSHD 
> reduces the dependency maintenance surface for SFTP Processors while 
> maintaining existing capabilities.
> The initial migration should retain existing Processor properties and 
> implementation structure built in the internal {{SFTPTransfer}} class. Tests 
> that mock particular SSHJ behavior should be removed or redesigned to make 
> use of SFTP interaction with MINA SSHD server components where necessary.
> Some low-level features such as particular algorithm negotiation, or private 
> key formats like PuTTY, may require manual migration. Support for legacy 
> cipher or key negotiation algorithms may require deprecation. Further 
> refinement of algorithm selection should be considered separately.
> Moving to MINA SSHD should provide a better foundation for considering future 
> changes, such as key management and connection reuse through a separate 
> Controller Service.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to