Details
-
Improvement
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
1.5.0
-
None
-
None
Description
the current build/sbt-launch-lib.bash uses two URLs to try and fetch sbt from
URL1=http://typesafe.artifactoryonline.com/typesafe/ivy-releases/org.scala-sbt/sbt-launch/${SBT_VERSION}/sbt-launch.jar URL2=http://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/sbt-launch/${SBT_VERSION}/sbt-launch.jar
Using HTTP means that the artifacts are downloaded without any auth, and without any checksum validation. Yet the actual URL currently just redirects to URL https://repo.typesafe.com/typesafe/ivy-releases/
switching to that directly would reduce vulnerability to MITM publishing of subverted artifacts -or at least postpone it to the maven/ivy phase.
An alternative strategy would be to have the SHA1 checksum in the script, and explicitly validate the D/L
Attachments
Issue Links
- relates to
-
SPARK-9254 sbt-launch-lib.bash should use `curl --location` to support HTTP/HTTPS redirection
- Resolved