[jira] [Commented] (NIFI-3045) Usage of -k undermines encrypted configuration

["Andy LoPresto (JIRA)" <ji...@apache.org>]

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

Andy LoPresto commented on NIFI-3045:
-------------------------------------

I have previously filed [NIFI-2656] to address this by allowing the actual application process ({{NiFi.java}}) to securely prompt for the key if not received from the bootstrap process ({{RunNiFi.java}}). This means the key material would not be exposed to the running process list, but would require manual intervention on startup/restart. 

> Usage of -k undermines encrypted configuration
> ----------------------------------------------
>
>                 Key: NIFI-3045
>                 URL: https://issues.apache.org/jira/browse/NIFI-3045
>             Project: Apache NiFi
>          Issue Type: Bug
>            Reporter: Anders Breindahl
>         Attachments: 2016-11-16_dash-ks-extraction.png, extract-dash-ks-from-process-list.xml
>
>
> Hey,
> When setting up a hardened NiFi installation I ran into this. I hope I'm mistaken.
> When running the `encrypt-config.sh` script, one has a `nifi.bootstrap.sensitive.key` string configured in `bootstrap.conf`. The service startup script makes this be passed from `RunNifi` to`NiFi` by a `-k` parameter.
> This however can be retrieved by any user of the interface -- which, combined with NiFi being able to read from (the encrypted-under-`nifi.bootstrap.sensitive.key`) `nifi.properties` file means that e.g. the `nifi.security.keystorePasswd` property can be decrypted offline.
> Does this have anything to it?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)