GitHub user Devian-ua opened a pull request:

    https://github.com/apache/spark/pull/14409

    [SPARK-16796] [Web UI] Visible passwords on Spark environment page

    ## What changes were proposed in this pull request?
    
    Mask spark.ssl.keyPassword, spark.ssl.keyStorePassword, 
spark.ssl.trustStorePassword in Web UI environment page.
    (Changes their values to ***** in env. page)
    
    
    ## How was this patch tested?
    
    I've built spark, run spark shell and checked that this values have been 
masked with *****.
    
    Also run tests:
    ./dev/run-tests
    
    [info] ScalaTest
    [info] Run completed in 1 hour, 9 minutes, 5 seconds.
    [info] Total number of tests run: 2166
    [info] Suites: completed 65, aborted 0
    [info] Tests: succeeded 2166, failed 0, canceled 0, ignored 590, pending 0
    [info] All tests passed.
    
    
![mask](https://cloud.githubusercontent.com/assets/15244468/17262154/7641e132-55e2-11e6-8a6c-30ead77c7372.png)
    
    


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/Devian-ua/spark maskpass

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/spark/pull/14409.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #14409
    
----
commit a9376cbe3409cd18f1c859f82908de9ebe844572
Author: Artur Sukhenko <[email protected]>
Date:   2016-07-29T20:07:20Z

    [SPARK-16796] [Web UI] Visible passwords on Spark environment page

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

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

Reply via email to