security: enforce HTTPS for Javadoc external links#11
Open
kcvabeysinghe wants to merge 1 commit intogoogle:masterfrom
Open
security: enforce HTTPS for Javadoc external links#11kcvabeysinghe wants to merge 1 commit intogoogle:masterfrom
kcvabeysinghe wants to merge 1 commit intogoogle:masterfrom
Conversation
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix: Upgrade
junit.orgJavadoc URLs to HTTPS inbuild.gradle.kts.Security Rationale:
Currently, the build script fetches Javadoc resources over plain HTTP (
http://junit.org).Although the server redirects to HTTPS, the initial cleartext request is vulnerable to Man-in-the-Middle (MitM) stripping attacks. An attacker on the network could intercept this request and inject malicious artifacts (like a spoofed
package-list) before the secure redirect occurs.Hardcoding HTTPS guarantees a secure connection from the start and ensures the integrity of the generated documentation.