Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Quick checksum file update to support current release as of 2024-11-13 @ 2131 US/Pacific Time #58

Open
wants to merge 8 commits into
base: main
Choose a base branch
from

Commits on Nov 14, 2024

  1. Update tak-md5checksum.txt

    Added docker-5.2-RELEASE-43.zip
    WaffleThief123 authored Nov 14, 2024
    Configuration menu
    Copy the full SHA
    ed24478 View commit details
    Browse the repository at this point in the history
  2. Update tak-sha1checksum.txt

    added docker-5.2-RELEASE-43.zip
    WaffleThief123 authored Nov 14, 2024
    Configuration menu
    Copy the full SHA
    23a96ad View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    0b86ddd View commit details
    Browse the repository at this point in the history
  4. Configuration menu
    Copy the full SHA
    ca83e36 View commit details
    Browse the repository at this point in the history
  5. fixed printf to be safer.

     the `"%s"` format string with `printf` is used to avoid potential issues related to unintended format specifiers in the variables. Here’s why it’s necessary and best practice:
    
    1. **Avoiding Unintended Format Specifiers**: If we directly pass variables like `printf "$info"`, it may contain unintended format specifiers (like `%d`, `%s`, etc.) that can cause unexpected behavior or errors if `printf` tries to interpret them. By specifying `"%s"`, we tell `printf` to treat the variable as a plain string.
    
    2. **Security and Stability**: Relying on the explicit `"%s"` format makes the script more robust and secure. If a variable accidentally includes a user-provided or dynamic string containing `%` characters, `printf` could interpret those as format specifiers, leading to errors or even security vulnerabilities in certain contexts.
    
    3. **Shellcheck Compliance**: Shellcheck, a popular linting tool for shell scripts, flags this usage (`SC2059`) because treating variables as format strings can lead to unpredictable behavior. Shellcheck recommends using explicit format strings to ensure consistency and avoid errors.
    
    4. **Readability and Maintainability**: Specifying `"%s\n"` for strings in `printf` is a clear signal to anyone reading the script that the output is intended as a simple string without embedded formatting instructions, making the code easier to understand and less error-prone.
    WaffleThief123 committed Nov 14, 2024
    Configuration menu
    Copy the full SHA
    8992d84 View commit details
    Browse the repository at this point in the history
  6. Undoing changes to main branch

    Revert "fixed printf to be safer."
    
    This reverts commit 8992d84.
    WaffleThief123 committed Nov 14, 2024
    Configuration menu
    Copy the full SHA
    deab54e View commit details
    Browse the repository at this point in the history
  7. undo changes to main

    Revert "sanity correction, not everyone has a /bin/bash, and some of us are on nix"
    
    This reverts commit ca83e36.
    WaffleThief123 committed Nov 14, 2024
    Configuration menu
    Copy the full SHA
    ad15331 View commit details
    Browse the repository at this point in the history
  8. Removed change to main

    Revert "fix to prevent unwanted expansion"
    
    This reverts commit 0b86ddd.
    WaffleThief123 committed Nov 14, 2024
    Configuration menu
    Copy the full SHA
    3a6e56d View commit details
    Browse the repository at this point in the history