Status: Proposed — not adopted · Last reviewed: 2026-11-06

Sources: NIST SP 800-88 Rev. 2, Guidelines for Media Sanitization (Sept. 2025) · Linux Mint supported releases (accessed 2026-11-06)

Technical Hub

Draft – Proposed. Everything on these pages is a recommendation waiting for Mark's approval. None of it is adopted program policy yet. If these drafts are approved for publication, they are meant to show donors, volunteers and neighbors how we intend to work, and to invite their suggestions.

Computers for Kids aims to take donated computers, clean them safely, and give them a second life with people in Oklahoma who need one, both kids and adults. This hub explains the technical side in plain language: how we propose to handle donor data, how we propose to prepare machines, what kinds of parts might help, and which free software we plan to try.

What each status means

Standards status

What we're aiming for (proposed principles)

• Donor privacy first. Under the proposed process, donor names, serial numbers, addresses and recipient details are kept off public pages.
• Honest labels. Each page shows whether it's proposed, tested or adopted.
• Official sources. Software links go to the maker's own site.
• Low cost. We prefer free tools. Any cost would be approved before anything is spent.

Want to help?

See the main program page for ways to get involved. Technical reviewers who want to comment on these drafts are welcome too.

Data Wiping Standard

Status: Proposed — not adopted · Last reviewed: 2026-11-06

Sources: NIST SP 800-88 Rev. 2, Guidelines for Media Sanitization, Sept. 2025, supersedes Rev. 1 (2014) · NIST SP 800-88r2 full text PDF; definitions from Appendix A pp. 32-33, Sec. 3.1 pp. 8-11, Sec. 4.5 pp. 24-25 (printed page numbers) · NIST announcement of Rev. 2 changes · IEEE 2883, media-specific sanitization standard referenced by Rev. 2

Data Wiping Standard

Draft – Proposed. This is a recommendation for Mark to review. It is not adopted program policy, and this process hasn't yet been tested as written.

A donated computer may still hold photos, passwords, tax files or saved logins. We propose making protection of that data the first step, before any repair or reuse.

Proposed basis

We propose basing this program on NIST Special Publication 800-88, Revision 2 (Guidelines for Media Sanitization), published September 2025. It replaced Revision 1 (2014).

Revision 2 focuses on running a sanitization program: written policy, defined roles, training, records, verification and validation. It no longer lists step-by-step techniques for each kind of media. For media-specific techniques, it points to standards such as IEEE 2883, or to an approved organizational standard. Cryptographic erase is the one technique it still discusses in detail.

NIST defines three sanitization methods. The wording below is quoted from the Rev. 2 glossary (Appendix A, printed pages 32–33):

• Clear: "A method of sanitization that applies logical techniques to sanitize data in all user-addressable storage locations for protection against simple, non-invasive data recovery techniques using the same interface that is available to the user."
• Purge: "A method of sanitization that applies physical or logical techniques to render target data recovery infeasible using state-of-the-art laboratory techniques."
• Destroy: "A method of sanitization that renders target data recovery infeasible using state-of-the-art laboratory techniques and results in the subsequent inability to use the media to store data."

Section 3.1.2 (printed page 10) adds that, when possible, purge should be used instead of clear, and that IEEE 2883 should be consulted for acceptable purge techniques on each media type.

Which method fits depends on how sensitive the data is and where the media is going next. Donated media leaves the donor's control for good, which is why the method choice is a policy decision for Mark (see open questions).

Why the drive type matters

Hard disk drives (HDDs) store data magnetically on spinning platters. The right clear or purge technique depends on the drive and the approved standard.

Solid-state storage (SSD, NVMe, eMMC) spreads data across areas the computer can't directly address, such as spare and remapped blocks. Overwriting what the computer can see may leave data elsewhere. Purge on these devices normally depends on the device's own sanitize functions, carried out and confirmed according to the approved standard.

Labels are not proof: - A tool or menu option called "secure erase" doesn't by itself show that a purge happened. What it actually does varies by device and firmware. - Cryptographic erase is not approved under this draft. Its prerequisites must be reviewed against the full NIST guidance and confirmed for the particular device before it can be considered.

USB sticks, memory cards and other media may not support dependable sanitize functions and need separate evaluation.

We don't publish step-by-step wiping commands. Running the wrong command can erase the wrong disk or leave data behind.

Proposed process

1. Intake and quarantine. Storage media is kept apart in a secured "not yet sanitized" area. The proposed process prohibits browsing, copying or booting into donor data.
2. Private record. An internal intake number, media type and capacity are logged privately; the proposed process keeps them off the public site.
3. Choose the technique that the approved standard specifies for that media type (still pending).
4. Sanitize with an approved tool.
5. Verify. NIST describes verification as determining "the outcome of the sanitization technique" and inspecting results "to verify that the sanitization technique was completed successfully" (Sec. 4.5.1, printed page 24). For clear and logical purge done with tools, NIST says this is done "by checking the completion status of the tools and identifying errors, anomalies, and the health of the ISM." For destruction, it means inspecting what remains and identifying the equipment used.
6. Validate. NIST describes validation as ensuring "that the target data was effectively sanitized," which ends in a decision to "approve the sanitization as being effective or reject it" (Sec. 4.5.2, printed pages 24–25). We propose that a designated reviewer considers the verification results, checks that the method and technique fit the media and the data, and accepts or rejects the result. NIST gives this example of a mismatch: degaussing an SSD "can complete successfully, but no sensitive data is sanitized." Opening the drive and finding no readable files therefore doesn't by itself show that an SSD was purged.
7. Record the date, technique, operator, reviewer and outcome privately.
8. Release for preparation only after the reviewer accepts.

If sanitization fails or can't be verified

The media stays quarantined and isn't released. NIST says a rejected sanitization requires "repeating the sanitization method using a different sanitization technique or escalating to a more secure sanitization method" (Sec. 4.5.2). Under this proposal, the media gets evaluated: another approved sanitization attempt, or destruction through an authorized process if that's approved. Errors don't trigger destruction automatically. The outcome is decided and recorded under the approved policy.

Limits

Following recognized guidance greatly lowers risk, but no process can guarantee results in every case. Donors with highly sensitive data may want to talk with us before donating. Whether we accept a computer with its drive removed is a decision still pending.

Before you donate (suggestions)

• Back up anything you want to keep.
• Sign out of your accounts and, if you can, deauthorize any purchased apps.
• You're welcome to wipe the computer yourself. How the program treats media that was already wiped is a pending policy question.

Preparation & Linux Mint Image

Status: Proposed — not adopted · Last reviewed: 2026-11-06

Sources: Linux Mint supported releases, accessed 2026-11-06 · Linux Mint 22.3 Cinnamon download page · Linux Mint 22.3 release notes · Linux Mint Installation Guide · Linux Mint ISO verification · Linux Mint OEM installation

Preparation & Linux Mint Image

Draft – Proposed. These are technical recommendations waiting for Mark's approval. They are not adopted program policy.

Our starting focus is Linux Mint Cinnamon for older donated computers; this written preparation standard remains Proposed and untested as written. Linux Mint is free to download. As of November 6, 2026, Linux Mint lists 22.3 "Zena" as a long-term-support release supported until April 2029 (supported releases). Details such as which release to use, minimum hardware and the setup method are still open.

Step 1: Start with one test machine

We recommend preparing one machine under this plan, writing down every step and problem, and only then writing a repeatable process.

Step 2: Hardware inventory (private record)

Record internally: make and model, processor, memory, storage type and size, screen, Wi-Fi, webcam, battery condition (laptops), ports and any damage. Serial numbers go only in the private record.

Step 3: Check compatibility

• 64-bit. Linux Mint 22.3 is offered as 64-bit downloads, so computers that can only run 32-bit software can't use it.
• Older graphics. The release notes say 22.2 and 22.3 ship a newer kernel (HWE 6.14) that has problems with old NVIDIA cards using the 470 driver. For those cards, Linux Mint suggests installing 22.1 and then upgrading without switching to the HWE kernel. A "Compatibility Mode" boot option may help with some graphics problems.
• Minimum specs: to be set from our own test results.

Step 4: Install and check

1. Download only from linuxmint.com and verify the download (SHA256 checksum and signature) following the official guide. This confirms the file matches what Linux Mint published, which lowers the risk of a corrupted or tampered download. It doesn't make the system secure by itself.
2. Install only on storage that has passed the approved sanitization review (see Data Wiping).
3. After installing, check: reliable startup, Wi-Fi, wired network, sound and microphone, webcam, brightness, keyboard and touchpad, USB ports, battery charging and holding a charge, sleep and wake, and all available updates installed through Update Manager.
4. Record pass or fail for each item.

Step 5: Repeatable setup (cloning)

Linux Mint's documented OEM install lets each recipient create their own account the first time the computer starts. It's one option to evaluate, alongside disk imaging.

Whatever method is chosen, each machine should have: - No personal data or saved credentials from donors or volunteers. - No shared accounts or passwords. - A unique machine identity (hostname, machine ID, and any SSH keys created fresh for each computer).

Licensing: Windows vs. Linux

• Linux Mint is free to download and use.
• Windows license transfer rules depend on the license type. Whether the program will reinstall or reuse Windows is an open decision for Mark, ideally made with qualified advice. Recommendation: hold off on reinstalling Windows until that policy exists.

Needed Parts & Compatibility

Status: Proposed — not adopted · Last reviewed: 2026-11-06

Sources: Linux Mint 22.3 release notes · Linux Mint supported releases

Needed Parts & Compatibility

Draft – Proposed. This is NOT a live wishlist. We don't have verified needs or inventory counts. This page explains the kinds of parts that often help with older computers and the details needed to check whether a part fits.

Please contact us before bringing any parts. We can't promise to accept a donation until we know what we need.

Part categories that often help

Describing a part

When you contact us, include the details printed on the part's label (type, size, model number). A photo of the label helps. Any used storage you offer would be handled under the proposed Data Wiping process, which prohibits browsing donor data.

Compatibility basics

• Current Linux Mint downloads are 64-bit.
• Some older NVIDIA graphics have known issues with the newest Mint kernel; see Preparation.

Software Testing Notes

Status: Proposed — not adopted · Last reviewed: 2026-11-06

Sources: Official links below returned HTTP 200 when checked on 2026-11-06. · Scratch app download and FAQ · Linux Mint ISO verification

Software Testing Notes

Draft – Proposed. None of these have been tested under this plan. Every row reads Not tested. Being on this list is not a recommendation.

Proposed method

For each candidate, record: install method, whether it launches, whether it works offline, performance on older hardware, suitability for kids and adults, accessibility, and license and terms. Note the date and the Linux Mint version.

Preferred install source: Linux Mint's Software Manager when the app is there; otherwise the maker's official site only.

Candidate matrix

Changelog

Status: Proposed — not adopted · Last reviewed: 2026-11-06

Sources: Internal record of draft edits.

Changelog

2026-11-10

• Published the public guide Fake-Capacity USB Drives: How to Spot and Test Them, prepared by Grace, with a link from this hub. Publication does not change other standards’ status.

2026-11-08

• Published the proposed Macintosh Reuse Guide with grouped model boundaries, dated source references and evaluation criteria. Publication does not adopt program policy.

2026-11-06

• Created first Proposed drafts: Technical Hub, Data Wiping Standard, Preparation & Linux Mint Image, Needed Parts & Compatibility, Software Testing Notes, and this Changelog.
• Same day: revised the drafts to make clear that they are recommendations pending approval, not adopted policy.
• Same day: checked the Data Wiping page against the NIST SP 800-88r2 PDF and replaced the summarized definitions with quoted wording and page references.
• Same day: softened privacy wording to proposed handling rules, simplified parts guidance, removed form-status statements, and clarified that Linux Mint Cinnamon is the starting focus while the written standard stays Proposed.
• These technical drafts have not been tested as written, adopted or published.