github PartialVolume/shredos.x86_64 v2025.11_30_x86-64_0.41
on GitHub

6 hours ago

v2025.11_30_x86-64_0.41

Buildroot Version Kernel Version Shredos Minor version Architecture Nwipe Version
2025.11 6.18.0 30 x86-64 and i686 0.41

Other software versions used within ShredOS for disc related operations

hexedit hdparm Smartctl Sg3_Utils nvme-cli openSeaChest
1.6 9.65 7.5 1.48 2.15 25.05.3

ShredOS Lite vs. Full: System RAM Requirements

ShredOS now offers Lite versions for both x86-64 (64-bit) and i686 (32-bit) architectures, specifically designed for low-resource hardware.

Memory Requirements:

  • Lite Versions: Boot successfully with just 512MB of RAM.
  • Standard Versions: Requires a minimum of 2GB of RAM to run properly.

Notable changes in this release - ShredOS

  • Pre/post wipe scripts
    ShredOS now includes support for user written pre and post wipe scripts. Instructions ⚠️ Security Warning
    Fetching and executing scripts as root poses significant security risks. To prevent Man-in-the-Middle (MitM) attacks, this feature should only be used over a secure, private network—never over the public internet. If you do not fully understand these security implications, we strongly advise against using this feature. Note: Depending on user feedback, we may update this feature in the future to allow user scripts to be loaded directly from the USB boot device. If this is something you are interested in, please let us know at #493 Thanks to @JeremyComelli1 #492

What's Changed (auto generated list)

New Contributors

Full Changelog: v2025.11_29_x86-64_0.40...v2025.11_30_x86-64_0.41

Notable changes in this release - Nwipe

  • System PDF Report nwipe has expanded its reporting capabilities to better support hardware refurbishers, resellers, and fleet-scale server wiping operations. In addition to individual drive certificates, nwipe can now generate a single system-focused erasure certificate. This document consolidates the erasure status and SMART data of all installed drives on a system and captures essential SMBIOS/DMI identifiers to ensure full auditability of the host, whether server, desktop or laptop." Note: The population of SMBIOS/DMI fields varies by manufacturer. While tier-one brands generally ensure high data integrity, some hardware vendors may provide incomplete or unpopulated data fields." Thanks to @PartialVolume #717 #723 #724 #752 #753 #754 Example: nwipe_system_report (anonymized)
  • Protection of Mounted Drives
    Having personally experienced the joy of wiping my system drive by mistake, we introduced a new feature to nwipe that now marks a mounted drive as [ In Use ] and will not allow you to wipe it.. unless you use the ./nwipe --force command line option to override this protection. In my opinion this is a really useful addition and will hopefully save somebody from accidentally wiping their system drive by mistake. Note for ShredOS users. As ShredOS is a disk less operating system running completely in RAM, it doesn't have a permanently mounted system disc unlike your typical Linux distribution so if you boot your work laptop/PC with ShredOS it won't recognise that one of your drives may have your favourite Linux distribution installed, as it won't be mounted. Therefore, if using ShredOS, make sure you are careful about selecting the correct drive that you want to wipe as this protection is not relevant for ShredOS. Thanks to @desertwitch #742 #751
Screenshot_20260515_214834
  • Reverse Wiping
    Nwipe can now reverse wipe a disk. The default wipe is a forward wipe starting at block zero to max block. You can now have nwipe wipe the disc in reverse from the max block to block zero. This feature may be useful if you are wiping a faulty disc that fails with an I/O error at a specific location on the disc. Prior to this new feature every block after the I/O error would have not been erased. Therefore, if a I/O error should occur due to a faulty disc, you can now use the d key on the drive selection screen to have nwipe start the wipe from the other end of the disc. In this way you are far more likely to wipe the bulk of the disk subject to the type of fault the disc may have. If reversing the wipe, a (R) is placed after the method to indicate which mode you have selected. Thanks to @desertwitch #735
Screenshot_20260515_220422
  • Scatter Wiping
    Nwipe can now optionally wipe a disk in a scattered segment mode instead of sequentially. Giving long seeks and short sequential writes while still completely erasing the entire disc. This is useful for stress testing a drive that you suspect of having seek errors. Scatter wiping can be selected with the d key from the drive selection screen. If scatter wipe mode is selected a (S) will be placed after the method to indicate which mode you are using. Thanks to @desertwitch #743
Screenshot_20260515_222619
  • Two New PRNGs - SplitMix64 (General-purpose PRNG) and ChaCha20 (Cryptographically-secure PRNG)
    ChaCha20, which is a very popular CSPRNG that's used in OS kernels, TLS, SSH.
    SplitMix64, a fast 64-bit centric PRNG, optimised and providing a great increase in speed which will be a nice feature for mass wipes/NVMe etc. In addition CSPRNG and PRNGs have been split between two menus in the GUI as shown below. Thanks to @desertwitch #727
Screenshot_20260515_224525 Screenshot_20260515_224552
  • CI Unit Testing
    Nwipe has now adopted CI Testing: The purpose of Continuous Integration (CI) unit testing for nwipe is to ensure the absolute reliability, safety, and stability of the software before code changes are merged into production.

Because nwipe is a data sanitization tool, the stakes for software failure are incredibly high. CI unit testing addresses this through several core functions:

  • Guaranteeing Erasure Integrity: A bug in a wiping utility can lead to catastrophic data leaks (e.g., reporting a successful wipe when data remains intact). Unit tests mathematically validate that the data generation algorithms (like AES-CTR or ChaCha20) and verification passes behave exactly as intended.

  • Preventing Regressions: As developers introduce new features—such as consolidated system certificates or optimized I/O buffering—automated testing ensures that existing core capabilities (like multi-drive threading or disk geometry parsing) are not inadvertently broken.

  • Ensuring Platform and Dependency Stability: nwipe relies closely on the Linux kernel, system calls, and external libraries (like libparted). CI pipelines compile and test the code against various environments to catch platform-specific compilation errors or dependency conflicts early.

  • Accelerating Open-Source Contributions: Automated workflows allow maintainers to safely and efficiently vet community pull requests. It provides an immediate sanity check on code quality, reducing the need for tedious manual validation on physical testing hardware.

Thanks @Knogle #725 and @desertwitch #737 #740

  • New command line switch (--no-abort-on-block-errors)
    This commit introduces a new command line option --no-abort-on-block-errors that allows forward write passes to continue when a block write fails. When enabled, nwipe will: treat the entire block as failed, count its size toward pass_errors, skip the block via lseek(), advance z and round_done accordingly, and continue with the next block instead of aborting the pass. The default behaviour (aborting the pass on a write error) remains unchanged. This implementation modifies only nwipe_random_pass() and nwipe_static_pass(); no changes to verification or reverse passes. Thanks to @Knogle #685
  • Reformatted the command line help to improve legibility
    User-input text is now highlighted in green, as shown in the image below. Please note that the following image represents only a portion of the available commands. nwipe --help Thanks to @PartialVolume #730
Screenshot_20260515_231536
  • Added Contribution Guidelines
    especially regarding the use of AI agents. Thanks @Knogle #739

What's Changed (auto generated list of all changes)

Download Counters

Architecture file format / Boot Capability / min. RAM / Writable? Download link
x86-64 .img / BIOS+UEFI USB / minimum 2GB RAM / writable GitHub release (by file)
x86-64 .iso / hybrid ISO (BIOS+UEFI, USB+CD/DVD) / minimum 2GB RAM / read only GitHub release (by file)
x86-64 .iso / hybrid ISO (BIOS+UEFI, USB+CD/DVD) / minimum 2GB RAM / plus extra writable partition GitHub release (by file)
x86-64 iso lite / hybrid ISO (BIOS+UEFI, USB+CD/DVD) / minimum 512MB RAM / read only GitHub release (by file)
x86-64 .img lite / USB image (BIOS+UEFI, USB) / minimum 512MB RAM / writable GitHub release (by file)
i686 .img lite / USB image (BIOS+UEFI, USB) / minimum 512MB RAM / writable GitHub release (by file)
i686 .iso lite / hybrid ISO (BIOS+UEFI, USB+CD/DVD) / minimum 512MB RAM / read only GitHub release (by file)
i686 .iso lite / hybrid ISO (BIOS+UEFI, USB+CD/DVD) / minimum 512MB RAM / plus extra writable partition GitHub release (by file)

SHA1 checksums

44d8fdd2562f067cc940b88daf0e15ee1c8b2185 shredos-2025.11_30_x86-64_v0.41_20260520.img
8c8ba3eda2917e61150e7a3cb180d31b4545580c shredos-2025.11_30_x86-64_v0.41_20260520.iso
a6e2a441e1850e69de8d7ccdc60b7bdc566ba6bb shredos-2025.11_30_i686_v0.41_20260521_lite.img
893a398b5c8aa2103949546b9b59cafc2872a353 shredos-2025.11_30_i686_v0.41_20260521_lite.iso
fa5d7c0705c674b859c04d8323e4c81e774c73cc shredos-2025.11_30_x86-64_v0.41_20260521_plus-partition.iso
46344c99a09349a2bcadef05d4dd0c3cb8026053 shredos-2025.11_30_i686_v0.41_20260521_lite_plus-partition.iso
817529aef16f2f481631ed158148d72c73d45473 shredos-2025.11_30_x86-64_v0.41_20260520_lite.img
204c288dee29d042f2bc830aef8181f7191ed9fa shredos-2025.11_30_x86-64_v0.41_20260520_lite.iso

Check out latest releases or
releases around PartialVolume/shredos.x86_64 v2025.11_30_x86-64_0.41

Don't miss a new shredos.x86_64 release

NewReleases is sending notifications on new releases.

Get notifications