Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/8218#issuecomment-137252475
I see, so it seems then that there are two kinds of authentication, one
during the handshake where we use some secure secret (i.e. the one used passed
from `ExecutorRunnable` to `YarnShuffleService`), and another for reading each
shuffle block where we use the app ID.
For the latter, could we use the same shuffle secret instead of the app ID?
That would require us to pass the secret to the executor JVM securely, which
could be difficult. This patch is already a strict improvement as is, so I'm
just wondering whether it's worth it to strengthen the security guarantees
further.
---
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]
