srowen commented on issue #5617: [SPARK-7037] [CORE] Inconsistent behavior for 
non-spark config properties in spark-shell and spark-submit
URL: https://github.com/apache/spark/pull/5617#issuecomment-565718466
 
 
   Yes, I think that's a good idea. We can redact them too, but no big reason
   to log the value anyway. I'll raise a PR.
   
   On Fri, Dec 13, 2019 at 11:32 PM Aaron Steers <[email protected]>
   wrote:
   
   > Is it expected that this error would print aws security keys to log files?
   > Seems like a serious security concern.
   >
   > Warning: Ignoring non-spark config property: 
fs.s3a.access.key={full-access-key}
   > Warning: Ignoring non-spark config property: 
fs.s3a.secret.key={full-secret-key}
   >
   > Could we not accomplish the same thing by printing the name of the key
   > *without* the key's value?
   >
   > —
   > You are receiving this because you were mentioned.
   > Reply to this email directly, view it on GitHub
   > 
<https://github.com/apache/spark/pull/5617?email_source=notifications&email_token=AAGIZ6TSSMBI3I2IVQIRIPDQYRVYTA5CNFSM4BAVX3R2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEG325OI#issuecomment-565685945>,
   > or unsubscribe
   > 
<https://github.com/notifications/unsubscribe-auth/AAGIZ6XOSHGGHWQMRYTOEJLQYRVYTANCNFSM4BAVX3RQ>
   > .
   >
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

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

Reply via email to