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

Mano Kovacs commented on SOLR-10076:
------------------------------------

Thank you [[email protected]] for your comment.

bq. We probably want to push users towards configuring this in a way it's not 
on the command line though, right?
I agree that this is more like a workaround in the current state. It could also 
work as a second layer of protection if passwords being passed in command line. 
I would assume that getting the list of running processes on a server would 
require higher privileges than accessing the admin-ui, which suggests that the 
passwords should not be exposed there.

bq. I know our start scripts recently still set some of this ssl stuff via the 
command line, but if that is still the case, we should fix that too.
Is there a jira for that? I would be happy looking into it.

> Hiding keystore and truststore passwords from /admin/info/* outputs
> -------------------------------------------------------------------
>
>                 Key: SOLR-10076
>                 URL: https://issues.apache.org/jira/browse/SOLR-10076
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Mano Kovacs
>            Assignee: Mark Miller
>         Attachments: SOLR-10076.patch
>
>
> Passing keystore and truststore password is done by system properties, via 
> cmd line parameter.
> As result, {{/admin/info/properties}} and {{/admin/info/system}} will print 
> out the received password.
> Proposing solution to automatically redact value of any system property 
> before output, containing the word {{password}}, and replacing its value with 
> {{******}}.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to