Skip to content

Switch wget of iozone tarball from http to https - #71

Open
malucius-rh wants to merge 2 commits into
masterfrom
switch_to_https
Open

Switch wget of iozone tarball from http to https#71
malucius-rh wants to merge 2 commits into
masterfrom
switch_to_https

Conversation

@malucius-rh

Copy link
Copy Markdown
Contributor

Description

This changes the wget of the iozone tarball from developer's site from http to https in accordance with qodo recommendation during doc updates

Before/After Comparison

Before: iozone tarball is wgetted using http
After: iozone tarball is wgetted using https

Clerical Stuff

This closes #66
Relates to JIRA: RPOPC-1045
Comms to open.spec.org before:
get_iozone_http_csv.csv
Comms to open.spec.org after:
get_iozone_https_csv.csv

@malucius-rh
malucius-rh requested a review from a team August 12, 2026 03:01
@malucius-rh malucius-rh self-assigned this Aug 12, 2026
@malucius-rh malucius-rh added the enhancement New feature or request label Aug 12, 2026
@coderabbitai

coderabbitai Bot commented Aug 12, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Summary by CodeRabbit

  • Security
    • Updated iozone kit downloads to use a secure HTTPS connection.
    • Improved the download failure message to reference the secure URL.

Walkthrough

The iozone runner now downloads the source kit over HTTPS. Its failure message uses the same HTTPS URL.

Changes

iozone download security

Layer / File(s) Summary
HTTPS source download
iozone/iozone_run.sh
The source download URL and related failure message changed from HTTP to HTTPS.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and concisely identifies the main change from HTTP to HTTPS for the iozone tarball download.
Description check ✅ Passed The description includes the required summary, before/after comparison, issue closure, and JIRA reference.
Linked Issues check ✅ Passed The HTTPS download change satisfies issue #66 by removing the insecure plain HTTP download path.
Out of Scope Changes check ✅ Passed The changes are limited to switching the iozone tarball download from HTTP to HTTPS.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing Touches 💡 1
🛠️ Fix failing CI checks 💡
  • Create stacked PR
  • Commit on current branch
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@iozone/iozone_run.sh`:
- Around line 454-456: Update the documented iozone source URL in README.md to
use https://www.iozone.org/src/current/ instead of the plain HTTP URL, matching
the HTTPS URL already used by the wget command in iozone_run.sh.
🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: ca116689-eb20-4b3b-956f-9b3615ec86fe

📥 Commits

Reviewing files that changed from the base of the PR and between b1b40a0 and 39a138f.

📒 Files selected for processing (1)
  • iozone/iozone_run.sh

Comment thread iozone/iozone_run.sh
Comment on lines +454 to +456
wget https://www.iozone.org/src/current/${iozone_kit}.tar
if [ $? -ne 0 ]; then
exit_out "wget http://www.iozone.org/src/current/${iozone_kit}.tar failed" 1
exit_out "wget https://www.iozone.org/src/current/${iozone_kit}.tar failed" 1

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔒 Security & Privacy | 🟠 Major | ⚡ Quick win

Update the documented source URL to HTTPS.

README.md:150-156 still directs users to http://www.iozone.org/src/current/. Users who follow the documentation can still download the source over plain HTTP. Change that URL to HTTPS in the same PR.

As per path instructions, this review prioritizes major security issues and avoids nitpicks.

🧰 Tools
🪛 Shellcheck (0.11.0)

[info] 454-454: Double quote to prevent globbing and word splitting.

(SC2086)


[style] 455-455: Check exit code directly with e.g. 'if ! mycmd;', not indirectly with $?.

(SC2181)

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@iozone/iozone_run.sh` around lines 454 - 456, Update the documented iozone
source URL in README.md to use https://www.iozone.org/src/current/ instead of
the plain HTTP URL, matching the HTTPS URL already used by the wget command in
iozone_run.sh.

Source: Path instructions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Bug: Insecure HTTP download with no integrity check

1 participant