[
https://issues.apache.org/jira/browse/SPARK-47172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17838474#comment-17838474
]
Mridul Muralidharan edited comment on SPARK-47172 at 4/18/24 5:47 AM:
----------------------------------------------------------------------
We do not backport features to released versions - so TLS will be in 4.x, not
3.x
Given the security implications for SPARK-47318, it was backported to 3.4 and
3.5 - as it was fixing a security issue in existing functionality.
This proposal reads like a new feature development, which would typically be
out of scope for 3.x
Given TLS, it would not very useful for 4.x either ?
was (Author: mridulm80):
We do not backport features to released versions - so TLS will be in 4.x, not
3.x
Given the security implications for SPARK-47318, it was backported to 3.4 and
3.5 - as it was fixing a security issue in existing functionality.
This proposal reads like a new feature development, while would be out of scope
for 3.x
Given TLS, not very useful for 4.x either ?
> Upgrade Transport block cipher mode to GCM
> ------------------------------------------
>
> Key: SPARK-47172
> URL: https://issues.apache.org/jira/browse/SPARK-47172
> Project: Spark
> Issue Type: Improvement
> Components: Security
> Affects Versions: 3.4.2, 3.5.0
> Reporter: Steve Weis
> Priority: Minor
>
> The cipher transformation currently used for encrypting RPC calls is an
> unauthenticated mode (AES/CTR/NoPadding). This needs to be upgraded to an
> authenticated mode (AES/GCM/NoPadding) to prevent ciphertext from being
> modified in transit.
> The relevant line is here:
> [https://github.com/apache/spark/blob/a939a7d0fd9c6b23c879cbee05275c6fbc939e38/common/network-common/src/main/java/org/apache/spark/network/util/TransportConf.java#L220]
> GCM is relatively more computationally expensive than CTR and adds a 16-byte
> block of authentication tag data to each payload.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
