Recent changes to Home

Home modified by Yonas Abeselom

Yonas Abeselom — Sun, 05 Jul 2026 07:00:44 -0000

--- v2
+++ v3
@@ -1,102 +1,87 @@
-
-
-AAD-50 — Abeselom ASIC-Direct 50
-Firmware-Enforced, 50-Cycle NVMe Sanitization with Per-Cycle Hardware Verification
-
-What Is AAD-50?
-AAD-50 is an open-source NVMe sanitization framework that solves a problem most operators do not know exists.
-When you run nvme sanitize on Linux, the command returns immediately. The drive acknowledges receipt. You move on. But NVMe Sanitize is asynchronous — the actual erasure happens in the background, and the standard tooling never checked whether it completed. If drive firmware silently fails — which UC San Diego researchers documented happening in 3 of 12 drives they tested — the operator has no way to know.
-AAD-50 fixes this. After every single sanitize cycle, AAD-50 polls NVMe Log Page 0x81 and refuses to advance until SSTAT = 0x1 confirms hardware completion. No assumptions. No trust. Hardware confirmation only.
-
-Key Facts
-
-Property | Detail
--- | --
-Version | 1.1
-Platforms | Linux, Windows, Windows GUI
-Cycles | 50 (B→C→A phase matrix)
-Verification | Log Page 0x81 per-cycle polling
-Audit output | SHA-256 tamper-evident chain + PDF Certificate of Destruction
-Standards alignment | NIST SP 800-88 Rev.2 Purge, NVMe Base Spec 2.0, ISO/IEC 27040
-License | Open source, free
-Author | Yonas Abeselom, Addis Ababa, Ethiopia
+# AAD-50 — Abeselom ASIC-Direct 50

-
-Every cycle is hardware-confirmed via Log Page 0x81 before the next begins.
-
-Real-World Validation
-On June 2, 2026, RFC [#3415] was opened on linux-nvme/nvme-cli proposing that the fire-and-forget verification gap be addressed natively in the tool.
-14 days later, PR [#3438] — implementing --wait and --repeat N — was merged into linux-nvme/nvme-cli master by Daniel Wagner, the primary maintainer. The verification architecture now ships with virtually every Linux distribution on earth.
-nvme-cli v3.0-b.1 explicitly lists PR [#3438] in its official release changelog.
-
-Peer Engagement
-→ Peter Gutmann (Univ. of Auckland, author of the Gutmann 35-pass method) — reviewed the specification twice, both rounds improved it. Final verdict: "It looks pretty good, I can't really find anything to complain about."
-→ Steven Swanson (UC San Diego, senior author of Wei et al. FAST 2011) — responded with substantive feedback on the generalisability of his 2011 findings to modern NVMe drives.
-→ Keith Busch (primary nvme-cli maintainer) — gave qualified personal approval for PR [#3438].
-→ Daniel Wagner (nvme-cli maintainer) — merged PR [#3438] into master, commit 84078fa.
-→ Guido van Rossum (creator of Python) — reviewed the implementation and called it "very cool."
-→ NVM Express — initiated internal review of the specification.
-
-Wiki Pages
-
-Quick Start — get running on Linux or Windows in minutes
-How It Works — the verification architecture explained
-Hardware Test Reports — confirmed drives and community results
-FAQ — common questions answered
-Standards Alignment — NIST, IEEE, NVMe Base Spec
-Roadmap — what comes next
-
-
-Links
-
-Repository: https://github.com/yonasabeselom/aad50
-Whitepaper DOI: https://doi.org/10.5281/zenodo.20839417
-RFC [#3415]: https://github.com/linux-nvme/nvme-cli/issues/3415
-PR [#3438]: https://github.com/linux-nvme/nvme-cli/pull/3438
-Contact: yonas_abeselom@protonmail.com
-
-AAD-50 — Abeselom ASIC-Direct 50
-Firmware-Enforced, 50-Cycle NVMe Sanitization with Per-Cycle Hardware Verification
+*Firmware-Enforced, 50-Cycle NVMe Sanitization with Per-Cycle Hardware Verification*

-What Is AAD-50?
+---
+
+## What Is AAD-50?
+
 AAD-50 is an open-source NVMe sanitization framework that solves a problem most operators do not know exists.
-When you run nvme sanitize on Linux, the command returns immediately. The drive acknowledges receipt. You move on. But NVMe Sanitize is asynchronous — the actual erasure happens in the background, and the standard tooling never checked whether it completed. If drive firmware silently fails — which UC San Diego researchers documented happening in 3 of 12 drives they tested — the operator has no way to know.
+
+When you run `nvme sanitize` on Linux, the command returns immediately. The drive acknowledges receipt. You move on. But NVMe Sanitize is asynchronous — the actual erasure happens in the background, and the standard tooling never checked whether it completed. If drive firmware silently fails — which UC San Diego researchers documented happening in 3 of 12 drives they tested — the operator has no way to know.
+
 AAD-50 fixes this. After every single sanitize cycle, AAD-50 polls NVMe Log Page 0x81 and refuses to advance until SSTAT = 0x1 confirms hardware completion. No assumptions. No trust. Hardware confirmation only.

-Key Facts
-PropertyDetailVersion1.1PlatformsLinux, Windows, Windows GUICycles50 (B→C→A phase matrix)VerificationLog Page 0x81 per-cycle pollingAudit outputSHA-256 tamper-evident chain + PDF Certificate of DestructionStandards alignmentNIST SP 800-88 Rev.2 Purge, NVMe Base Spec 2.0, ISO/IEC 27040LicenseOpen source, freeAuthorYonas Abeselom, Addis Ababa, Ethiopia
+---

-The Three Phases
-PhaseCyclesActionNVMe CommandB — Physical Overwrite1–40NAND cell overwriteSANITIZE_ACTION_OVERWRITE (0x02)C — FTL Teardown41–45FTL index destructionSANITIZE_ACTION_BLOCK_ERASE (0x01)A — Crypto Seal46–50Media key destructionSANITIZE_ACTION_CRYPTO_ERASE (0x04)
+## Key Facts
+
+| Property | Detail |
+|---|---|
+| Version | 1.1 |
+| Platforms | Linux, Windows, Windows GUI |
+| Cycles | 50 (B->C->A phase matrix) |
+| Verification | Log Page 0x81 per-cycle polling |
+| Audit output | SHA-256 tamper-evident chain + PDF Certificate of Destruction |
+| Standards alignment | NIST SP 800-88 Rev.2 Purge, NVMe Base Spec 2.0, ISO/IEC 27040 |
+| License | Open source, free |
+| Author | Yonas Abeselom, Addis Ababa, Ethiopia |
+
+---
+
+## The Three Phases
+
+| Phase | Cycles | Action | NVMe Command |
+|---|---|---|---|
+| B - Physical Overwrite | 1-40 | NAND cell overwrite | SANITIZE_ACTION_OVERWRITE (0x02) |
+| C - FTL Teardown | 41-45 | FTL index destruction | SANITIZE_ACTION_BLOCK_ERASE (0x01) |
+| A - Crypto Seal | 46-50 | Media key destruction | SANITIZE_ACTION_CRYPTO_ERASE (0x04) |
+
 Every cycle is hardware-confirmed via Log Page 0x81 before the next begins.

-Real-World Validation
+---
+
+## Real-World Validation
+
 On June 2, 2026, RFC [#3415] was opened on linux-nvme/nvme-cli proposing that the fire-and-forget verification gap be addressed natively in the tool.
-14 days later, PR [#3438] — implementing --wait and --repeat N — was merged into linux-nvme/nvme-cli master by Daniel Wagner, the primary maintainer. The verification architecture now ships with virtually every Linux distribution on earth.
+
+14 days later, PR [#3438] — implementing `--wait` and `--repeat N` — was merged into linux-nvme/nvme-cli master by Daniel Wagner, the primary maintainer. The verification architecture now ships with virtually every Linux distribution on earth.
+
 nvme-cli v3.0-b.1 explicitly lists PR [#3438] in its official release changelog.

-Peer Engagement
-→ Peter Gutmann (Univ. of Auckland, author of the Gutmann 35-pass method) — reviewed the specification twice, both rounds improved it. Final verdict: "It looks pretty good, I can't really find anything to complain about."
-→ Steven Swanson (UC San Diego, senior author of Wei et al. FAST 2011) — responded with substantive feedback on the generalisability of his 2011 findings to modern NVMe drives.
-→ Keith Busch (primary nvme-cli maintainer) — gave qualified personal approval for PR [#3438].
-→ Daniel Wagner (nvme-cli maintainer) — merged PR [#3438] into master, commit 84078fa.
-→ Guido van Rossum (creator of Python) — reviewed the implementation and called it "very cool."
-→ NVM Express — initiated internal review of the specification.
+---

-Wiki Pages
+## Peer Engagement

-[Quick Start](https://github.com/yonasabeselom/aad50/wiki/Quick-Start) — get running on Linux or Windows in minutes
-[How It Works](https://github.com/yonasabeselom/aad50/wiki/How-It-Works) — the verification architecture explained
-[Hardware Test Reports](https://github.com/yonasabeselom/aad50/wiki/Hardware-Test-Reports) — confirmed drives and community results
-[FAQ](https://github.com/yonasabeselom/aad50/wiki/FAQ) — common questions answered
-[Standards Alignment](https://github.com/yonasabeselom/aad50/wiki/Standards-Alignment) — NIST, IEEE, NVMe Base Spec
-[Roadmap](https://github.com/yonasabeselom/aad50/wiki/Roadmap) — what comes next
+-> **Peter Gutmann** (Univ. of Auckland, author of the Gutmann 35-pass method) — reviewed the specification twice, both rounds improved it. Final verdict: "It looks pretty good, I can't really find anything to complain about."

+-> **Steven Swanson** (UC San Diego, senior author of Wei et al. FAST 2011) — responded with substantive feedback on the generalisability of his 2011 findings to modern NVMe drives.

-Links
+-> **Keith Busch** (primary nvme-cli maintainer) — gave qualified personal approval for PR [#3438].

-Repository: https://github.com/yonasabeselom/aad50
-Whitepaper DOI: https://doi.org/10.5281/zenodo.20839417
-RFC [#3415]: https://github.com/linux-nvme/nvme-cli/issues/3415
-PR [#3438]: https://github.com/linux-nvme/nvme-cli/pull/3438
-Contact: [yonas_abeselom@protonmail.com](mailto:yonas_abeselom@protonmail.com)
+-> **Daniel Wagner** (nvme-cli maintainer) — merged PR [#3438] into master, commit 84078fa.
+
+-> **Guido van Rossum** (creator of Python) — reviewed the implementation and called it "very cool."
+
+-> **NVM Express** — initiated internal review of the specification.
+
+---
+
+## Wiki Pages
+
+- [Quick Start](Quick-Start) — get running on Linux or Windows in minutes
+- [How It Works](How-It-Works) — the verification architecture explained
+- [Hardware Test Reports](Hardware-Test-Reports) — confirmed drives and community results
+- [FAQ](FAQ) — common questions answered
+- [Standards Alignment](Standards-Alignment) — NIST, IEEE, NVMe Base Spec
+- [Roadmap](Roadmap) — what comes next
+
+---
+
+## Links
+
+- Repository: https://github.com/yonasabeselom/aad50
+- Whitepaper DOI: https://doi.org/10.5281/zenodo.20839417
+- RFC [#3415]: https://github.com/linux-nvme/nvme-cli/issues/3415
+- PR [#3438]: https://github.com/linux-nvme/nvme-cli/pull/3438
+- Contact: yonas_abeselom@protonmail.com

Home modified by Yonas Abeselom

Yonas Abeselom — Sun, 05 Jul 2026 07:00:43 -0000

--- v1
+++ v2
@@ -1,8 +1,102 @@
-Welcome to your wiki!
+
+
+AAD-50 — Abeselom ASIC-Direct 50
+Firmware-Enforced, 50-Cycle NVMe Sanitization with Per-Cycle Hardware Verification
+
+What Is AAD-50?
+AAD-50 is an open-source NVMe sanitization framework that solves a problem most operators do not know exists.
+When you run nvme sanitize on Linux, the command returns immediately. The drive acknowledges receipt. You move on. But NVMe Sanitize is asynchronous — the actual erasure happens in the background, and the standard tooling never checked whether it completed. If drive firmware silently fails — which UC San Diego researchers documented happening in 3 of 12 drives they tested — the operator has no way to know.
+AAD-50 fixes this. After every single sanitize cycle, AAD-50 polls NVMe Log Page 0x81 and refuses to advance until SSTAT = 0x1 confirms hardware completion. No assumptions. No trust. Hardware confirmation only.
+
+Key Facts
+
+Property | Detail
+-- | --
+Version | 1.1
+Platforms | Linux, Windows, Windows GUI
+Cycles | 50 (B→C→A phase matrix)
+Verification | Log Page 0x81 per-cycle polling
+Audit output | SHA-256 tamper-evident chain + PDF Certificate of Destruction
+Standards alignment | NIST SP 800-88 Rev.2 Purge, NVMe Base Spec 2.0, ISO/IEC 27040
+License | Open source, free
+Author | Yonas Abeselom, Addis Ababa, Ethiopia

-This is the default page, edit it as you see fit. To add a new page simply reference it within brackets, e.g.: [SamplePage].
+
+Every cycle is hardware-confirmed via Log Page 0x81 before the next begins.
+
+Real-World Validation
+On June 2, 2026, RFC [#3415] was opened on linux-nvme/nvme-cli proposing that the fire-and-forget verification gap be addressed natively in the tool.
+14 days later, PR [#3438] — implementing --wait and --repeat N — was merged into linux-nvme/nvme-cli master by Daniel Wagner, the primary maintainer. The verification architecture now ships with virtually every Linux distribution on earth.
+nvme-cli v3.0-b.1 explicitly lists PR [#3438] in its official release changelog.
+
+Peer Engagement
+→ Peter Gutmann (Univ. of Auckland, author of the Gutmann 35-pass method) — reviewed the specification twice, both rounds improved it. Final verdict: "It looks pretty good, I can't really find anything to complain about."
+→ Steven Swanson (UC San Diego, senior author of Wei et al. FAST 2011) — responded with substantive feedback on the generalisability of his 2011 findings to modern NVMe drives.
+→ Keith Busch (primary nvme-cli maintainer) — gave qualified personal approval for PR [#3438].
+→ Daniel Wagner (nvme-cli maintainer) — merged PR [#3438] into master, commit 84078fa.
+→ Guido van Rossum (creator of Python) — reviewed the implementation and called it "very cool."
+→ NVM Express — initiated internal review of the specification.
+
+Wiki Pages
+
+Quick Start — get running on Linux or Windows in minutes
+How It Works — the verification architecture explained
+Hardware Test Reports — confirmed drives and community results
+FAQ — common questions answered
+Standards Alignment — NIST, IEEE, NVMe Base Spec
+Roadmap — what comes next
+
+
+Links
+
+Repository: https://github.com/yonasabeselom/aad50
+Whitepaper DOI: https://doi.org/10.5281/zenodo.20839417
+RFC [#3415]: https://github.com/linux-nvme/nvme-cli/issues/3415
+PR [#3438]: https://github.com/linux-nvme/nvme-cli/pull/3438
+Contact: yonas_abeselom@protonmail.com
+
+AAD-50 — Abeselom ASIC-Direct 50
+Firmware-Enforced, 50-Cycle NVMe Sanitization with Per-Cycle Hardware Verification

-The wiki uses [Markdown](/nf/markdown_syntax) syntax.
+What Is AAD-50?
+AAD-50 is an open-source NVMe sanitization framework that solves a problem most operators do not know exists.
+When you run nvme sanitize on Linux, the command returns immediately. The drive acknowledges receipt. You move on. But NVMe Sanitize is asynchronous — the actual erasure happens in the background, and the standard tooling never checked whether it completed. If drive firmware silently fails — which UC San Diego researchers documented happening in 3 of 12 drives they tested — the operator has no way to know.
+AAD-50 fixes this. After every single sanitize cycle, AAD-50 polls NVMe Log Page 0x81 and refuses to advance until SSTAT = 0x1 confirms hardware completion. No assumptions. No trust. Hardware confirmation only.

-[[members limit=20]]
-[[download_button]]
+Key Facts
+PropertyDetailVersion1.1PlatformsLinux, Windows, Windows GUICycles50 (B→C→A phase matrix)VerificationLog Page 0x81 per-cycle pollingAudit outputSHA-256 tamper-evident chain + PDF Certificate of DestructionStandards alignmentNIST SP 800-88 Rev.2 Purge, NVMe Base Spec 2.0, ISO/IEC 27040LicenseOpen source, freeAuthorYonas Abeselom, Addis Ababa, Ethiopia
+
+The Three Phases
+PhaseCyclesActionNVMe CommandB — Physical Overwrite1–40NAND cell overwriteSANITIZE_ACTION_OVERWRITE (0x02)C — FTL Teardown41–45FTL index destructionSANITIZE_ACTION_BLOCK_ERASE (0x01)A — Crypto Seal46–50Media key destructionSANITIZE_ACTION_CRYPTO_ERASE (0x04)
+Every cycle is hardware-confirmed via Log Page 0x81 before the next begins.
+
+Real-World Validation
+On June 2, 2026, RFC [#3415] was opened on linux-nvme/nvme-cli proposing that the fire-and-forget verification gap be addressed natively in the tool.
+14 days later, PR [#3438] — implementing --wait and --repeat N — was merged into linux-nvme/nvme-cli master by Daniel Wagner, the primary maintainer. The verification architecture now ships with virtually every Linux distribution on earth.
+nvme-cli v3.0-b.1 explicitly lists PR [#3438] in its official release changelog.
+
+Peer Engagement
+→ Peter Gutmann (Univ. of Auckland, author of the Gutmann 35-pass method) — reviewed the specification twice, both rounds improved it. Final verdict: "It looks pretty good, I can't really find anything to complain about."
+→ Steven Swanson (UC San Diego, senior author of Wei et al. FAST 2011) — responded with substantive feedback on the generalisability of his 2011 findings to modern NVMe drives.
+→ Keith Busch (primary nvme-cli maintainer) — gave qualified personal approval for PR [#3438].
+→ Daniel Wagner (nvme-cli maintainer) — merged PR [#3438] into master, commit 84078fa.
+→ Guido van Rossum (creator of Python) — reviewed the implementation and called it "very cool."
+→ NVM Express — initiated internal review of the specification.
+
+Wiki Pages
+
+[Quick Start](https://github.com/yonasabeselom/aad50/wiki/Quick-Start) — get running on Linux or Windows in minutes
+[How It Works](https://github.com/yonasabeselom/aad50/wiki/How-It-Works) — the verification architecture explained
+[Hardware Test Reports](https://github.com/yonasabeselom/aad50/wiki/Hardware-Test-Reports) — confirmed drives and community results
+[FAQ](https://github.com/yonasabeselom/aad50/wiki/FAQ) — common questions answered
+[Standards Alignment](https://github.com/yonasabeselom/aad50/wiki/Standards-Alignment) — NIST, IEEE, NVMe Base Spec
+[Roadmap](https://github.com/yonasabeselom/aad50/wiki/Roadmap) — what comes next
+
+
+Links
+
+Repository: https://github.com/yonasabeselom/aad50
+Whitepaper DOI: https://doi.org/10.5281/zenodo.20839417
+RFC [#3415]: https://github.com/linux-nvme/nvme-cli/issues/3415
+PR [#3438]: https://github.com/linux-nvme/nvme-cli/pull/3438
+Contact: [yonas_abeselom@protonmail.com](mailto:yonas_abeselom@protonmail.com)

Home modified by Yonas Abeselom

Yonas Abeselom — Sun, 05 Jul 2026 07:00:41 -0000

Welcome to your wiki!

This is the default page, edit it as you see fit. To add a new page simply reference it within brackets, e.g.: [SamplePage].

The wiki uses Markdown syntax.

Project Members:

Yonas Abeselom (admin)