[
https://issues.apache.org/jira/browse/NIFI-1415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy LoPresto reopened NIFI-1415:
---------------------------------
I am re-opening this ticket and suggest adding a property to this processor to
explicitly allow an empty passphrase on a private key, but by default requiring
a passphrase. I think we should raise the status quo to enforce good security
practices, which require a passphrase to protect this extremely sensitive data.
We should instruct the user on the proper process to add a passphrase to their
key if necessary. If there are legacy requirements/blockers to doing this, the
administrator/dataflow manager will be required to explicitly acknowledge that
this is unsafe and set the override property. As an example, this has been
implemented for weak legacy cryptographic combinations in {{EncryptContent}}
processor in [NIFI-1463]. This should also be done for all other uses of
"private keys" throughout the application.
> FetchSFTP should not require password or private key passphrase
> ---------------------------------------------------------------
>
> Key: NIFI-1415
> URL: https://issues.apache.org/jira/browse/NIFI-1415
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Reporter: Mark Payne
> Assignee: Mark Payne
> Fix For: 0.5.0
>
> Attachments:
> 0001-NIFI-1415-Do-not-enfoce-that-a-password-or-Private-K.patch
>
>
> SFTP does support allowing a user to connect with a Private Key but not
> passphrase. The Processor should support this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
