This commit updates the nwipe package to build from a specific Git commit
instead of using the previously referenced tarball release. The changes
include:
- Setting NWIPE_SITE to the GitHub repository and NWIPE_SITE_METHOD to git.
- Specifying the commit hash (051e1aa) in NWIPE_VERSION.
- Removing or emptying the nwipe.hash file, as we no longer verify a tarball
and instead rely on the Git checkout.
This approach allows ShredOS/Buildroot to clone the nwipe repository at
commit 051e1aa, apply the banner patch, and build the nwipe binary directly
from Git.
Enable additional cryptographic kernel options required for using
AES-CTR via the AF_ALG userspace interface in future features:
- CONFIG_CRYPTO_PCRYPT: parallel crypto wrapper for symmetric ciphers
- CONFIG_CRYPTO_USER_API_SKCIPHER: AF_ALG user API for skcipher
- CONFIG_CRYPTO_AES_NI_INTEL: AES-NI accelerated AES implementation on x86_64
These options prepare the kernel for an AF_ALG-based AES-CTR PRNG and
other potential AF_ALG-backed cryptographic functionality in nwipe.
Allow to append a FAT16 partition image when building an ISO in hybrid mode.
This allows to add an extra writeable partition for when the ISO is burned to USB.
This feature is experimental and disabled by default.
Signed-off-by: desertwitch <24509509+desertwitch@users.noreply.github.com>
The EFI partition for hybrid ISOs does not reliably show on all Windows systems, so we cannot use our "hack" of writing the configurations/PDFs to it. Reverted instead to a sane-sized EFI partition which is used just for booting. Added a note to the README that some tools such as Rufus support an ISO-mode to add a writeable partition at burning-time.
Signed-off-by: desertwitch <24509509+desertwitch@users.noreply.github.com>
It is more convenient to not have to search for configuration files in different directories, and also helpful to see the standard configuration files, so move all ShredOS configurations into board/shredos.
Signed-off-by: desertwitch <24509509+desertwitch@users.noreply.github.com>
Reconfigure starts one stage before rebuild, just to be safe. It is the earliest step after the source download and patching.
Signed-off-by: desertwitch <24509509+desertwitch@users.noreply.github.com>
Helps GRUB find the ShredOS volume when it otherwise cannot (such as when the IMG is used with Ventoy in BIOS)
Signed-off-by: desertwitch <24509509+desertwitch@users.noreply.github.com>
The all-in-one ISO works well and is the jack-of-all-trades, covering all imaginable systems and scenarios, so include that in the default build configurations.
Signed-off-by: desertwitch <24509509+desertwitch@users.noreply.github.com>
This adds a configuration for a jack-of-all-trades ISO, which allows BIOS and UEFI booting, being written to CD/DVD-ROM and USB drives, as well as having a writeable partition when being used from an USB drive. It basically combines the functionality of all prior release versions into one single ISO (per architecture).
Signed-off-by: desertwitch <24509509+desertwitch@users.noreply.github.com>
To keep things consistent, copy the EFI configuration also to the EFI structure on the ISO9660 filesystem.
Signed-off-by: desertwitch <24509509+desertwitch@users.noreply.github.com>
Improved the iso9660 argument order to better reflect modern best practices, inspired by the Debian distribution ISOs.
Signed-off-by: desertwitch <24509509+desertwitch@users.noreply.github.com>
Additional configurations for the i586 builds were added, so that new users can easily build those targets without needing to change things around via "make menuconfig" (potentially triggering unwanted other changes, e.g. reset of GRUB modules).
Signed-off-by: desertwitch <24509509+desertwitch@users.noreply.github.com>
The default configuration "shredos_defconfig" was amended to produce both the existing USB image (which allows writing PDFs to the USB) and the new hybrid ISO (which now allows BIOS+UEFI booting, as well as flashing to USB and burning to CD/DVD-ROM) in one build.
Additional configurations "shredos_img_defconfig" and "shredos_iso_defconfig" were added which only target either the existing USB image or the new hybrid ISO, for full flexibility.
Signed-off-by: desertwitch <24509509+desertwitch@users.noreply.github.com>
Post-processing used a static (outdated?) GRUB image for USB image generation, but it is better to use the GRUB image produced as part of the building process, which ensures that the actual compiled GRUB version is used as bootloader in our images and not an outdated one.
Post-processing previously embedded the 64-bit EFI bootloader to 32-bit builds, as no architecture checks were in place. This was changed to check for architecture and embed the correct EFI bootloader for the respective target architecture instead.
The GRUB configuration was changed to use a menu, to allow the user to choose between standard and nomodeset parameters, while also allowing the user to edit the command line to append other kernel parameters they may need for their systems.
The vanity kernel image name was returned to bzImage to clearly mark the image for what it is, and to remain consistent with the ISO file generation where we have no direct control over the image now.
Signed-off-by: desertwitch <24509509+desertwitch@users.noreply.github.com>
As the board is now using a GRUB menu, replacing these messages no longer makes sense (most users will never see them), so the additional patch is better removed.
Signed-off-by: desertwitch <24509509+desertwitch@users.noreply.github.com>
The entire iso9660 filesystem folder was restructured to replace partially unreadable legacy code with modern, readable and modular structures. Hardcoded paths were replaced with variables, as much as possible, to make the code work with different setups. A mode "both" was added, producing Debian-style hybrid ISOs for both BIOS and EFI usage, while still allowing for flashing to USB and/or burning to CD/DVD-ROM. The configuration GUI (via "make menuconfig") was also refactored and adapted to the new changes.
Signed-off-by: desertwitch <24509509+desertwitch@users.noreply.github.com>
* Completed Troubleshooting Information
* Update README.md with information about toggling font size
Previously the toggling of bigger font sizes required access to the virtual terminal. PartialVolume integrated a shortcut.
* Smaller Readibility Updates
* Clarification regarding Mac Support
Expanded definition of Mac to all intel powered macs
* Clarified supported systems
* Fixed typo on new Display Font Size Toggle paragraph
