# personal_scripts
These are various scripts I have created to make some tasks easier. There
aren't many here now, but I will be adding to them as I need them. If
you find any of them useful, feel free to grab them and use them.

Each script will have a "fancy info box" giving some background
information about why I created the script. If relevant, I will give some
information on how to use the script other than using `./${script_name}`.

# Cyber-Resilience Declaration
**Project** posix-scripts-collection

## Scope & Intended Use
A set of POSIX-compliant shell scripts for various tasks, such as media
conversion, floppy disk reformatting, etc.

The scripts are designed to act upon a file or device node and assume
the operating system enforces file permissions.

The scripts rely on various utilities. The scripts assume the utilities
are either included with the user's operating system or installed by
the user and are trusted by the user.

## CRA Compliance Summary
 * Scripts avoid `eval` and use quoted variables
 * No script escalates privileges; they rely on the operating system's
 permission model
 * External dependencies are not bundled with the scripts; they must be
 provided by the user's operating system or installed by the user
 * New versions are published on GitHub. No official releases are made --
 users must download via the repositories Code tab or use `git clone`
 to clone the repository and `git pull` to update.
 * Security patches will be provided where relevant for **12 months*
 after the most recent commit.
 * Vulnerability reporting -- see the SECURITY file

== Why a README instead of a README.md ==
Because I don't see a need to use MarkDown for a simple README. MarkDown
can be great for some stuff, but not so much for a plain-text README.