You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[SPARK-47172][CORE][3.5] Add support for AES-GCM for RPC encryption
### What changes were proposed in this pull request?
This change adds AES-GCM as an optional AES cipher mode for RPC encryption. The current default is using AES-CTR without any authentication. That would allow someone on the network to easily modify RPC contents on the wire and impact Spark behavior. See [SPARK-47172](https://issues.apache.org/jira/browse/SPARK-47172) for more details.
### Why are the changes needed?
The current default is using AES-CTR without any authentication. That would allow someone on the network to easily modify RPC contents on the wire and impact Spark behavior.
### Does this PR introduce _any_ user-facing change?
Yes, it adds an additional configuration flag is reflected in the documentation.
### How was this patch tested?
Existing unit tests are all ensured to pass. New unit tests are written to explicitly test GCM support and to verify that modifying ciphertext content will cause an exception and fail.
`build/sbt "network-common/test:testOnly"`
`build/sbt "network-common/test:testOnly org.apache.spark.network.crypto.AuthIntegrationSuite"` `build/sbt "network-common/test:testOnly org.apache.spark.network.crypto.AuthEngineSuite"`
### Was this patch authored or co-authored using generative AI tooling?
Nope.
Closes#47060 from sweisdb/SPARK-47172-3.5.
Authored-by: Steve Weis <steve.weis@databricks.com>
Signed-off-by: Yi Wu <yi.wu@databricks.com>
0 commit comments