The reports key
Write the reports key once, from its image, to keep the proofs of the sessions started from a CD or a virtual DVD.
Wipe writes the proof of each session to a reports key: a small USB key carrying one FAT32
partition named WipeReports. You write that key once, from the image file the portal offers in
Settings → Agent & tools, on the Reports key card, then plug it in beside the machine at
each session. The key is a relay: you collect the proofs from it and upload them to the portal.
When you need it
You start the machine from your organization's ISO as a CD or DVD, real or the virtual DVD of a management card (iLO, iDRAC or XClarity). A CD has no place to keep the proof, so the agent keeps it on the reports key. See Start from a CD or a virtual DVD and Start a server through its management card.
You start the machine from a USB key written from the ISO: that key has its own space for the proofs. A reports key plugged in beside it is ignored and never erased.
One reports key at a time. With two, the session is refused.
Plug the key in before the session starts, and leave it in until the session has ended: its last
screen says Proof stored on the key, then what the portal answered. That last step can take up
to 20 minutes when the portal is slow or out of reach: up to 10 to deliver the proof, then up to
10 for its status. See What happens at the end.
What you need
A USB key of at least 269,484,032 bytes (257 MiB). Everything on it is lost.
About 23 MB free on the key per session: room for the proof and the session's logs. When the key lacks the space, the agent says so from its first screen:
Not enough free space on the reports key: free some or plug in another keyIf the key still lacks it when the work is about to start, the agent refuses the session before erasing anything, with the figures:
Reports key too full, nothing erased: free space on it or plug in another key
Free: 11 MB, needed: 23 MB, to free: 12 MB
Delete only files you put there: a proof in proofs/ may be undeliveredTo free space, see When the stick is full: the agent lists the sessions you may delete.
A key the agent cannot write to gives Reports key not writable: plug in another key.
The image file, exawipe-reports-key.img, and its SHA-256, both on the Reports key card of
Settings → Agent & tools: Download saves the file, and the card shows its SHA-256 and
its Size.
1. Check the file
Compute the file's SHA-256 and compare it with the one the Reports key card shows. The two values must be identical; if they differ, download the file again.
# Windows (PowerShell)
Get-FileHash .\exawipe-reports-key.img -Algorithm SHA256# macOS
shasum -a 256 exawipe-reports-key.img
# Linux
sha256sum exawipe-reports-key.img2. Write it to the key
Writing erases the device you choose, without a question. Choose the USB key, never a disk of your computer. Unplug every other USB drive first if you are unsure.
Windows, balenaEtcher (free, also on macOS and Linux): click Flash from file and choose
exawipe-reports-key.img, click Select target and tick the USB key alone, then Flash!. Etcher
writes the image and reads it back. If Windows asks meanwhile to format the key, click Cancel:
formatting would compete with the write.
Windows, Rufus (free): under Device, choose the USB key. Click SELECT and choose
exawipe-reports-key.img; Rufus writes an .img as it is (DD mode). Click START, then OK
when it warns that the key will be erased.
macOS, balenaEtcher: as on Windows. macOS then shows the key as WipeReports. If Etcher
answers Error opening source for every file, a fault of some of its versions, use another tool
of this list.
macOS, Terminal: find the key, /dev/diskN, by its size and external, physical:
diskutil list
diskutil unmountDisk /dev/diskN
sudo dd if=exawipe-reports-key.img of=/dev/rdiskN bs=4m
diskutil eject /dev/diskNLinux: find the key, /dev/sdX, by its size and model; balenaEtcher works too.
lsblk -o NAME,SIZE,MODEL,TRAN
sudo dd if=exawipe-reports-key.img of=/dev/sdX bs=4M conv=fsync status=progressRaspberry Pi Imager (free, on Windows, macOS and Linux): as the device, choose No filtering;
as the operating system, Use custom and exawipe-reports-key.img; as the storage, the USB key.
Write, and confirm the erase. It applies no customization to this image, and ejects the key when
done. If Windows then gives the key no drive letter, add one in Disk Management: right-click its
partition, Change Drive Letter and Paths, Add.
3. Check the key
Unplug the key and plug it in again. It shows one volume of about 256 MiB (268 MB) whatever the key's size, as expected: the rest of the key stays unused.
Windows: in PowerShell or a Command Prompt, cmd /c vol E: (the key's letter) gives
Volume in drive E is WipeReports and Volume Serial Number is 4558-4157. In PowerShell,
Get-Volume -DriveLetter E shows WipeReports, FAT32 and about 252 MB, the volume's usable
size.
Linux: lsblk -o NAME,SIZE,LABEL shows the partition WipeReports of 256M, and
blkid /dev/sdX1 shows LABEL="WipeReports", UUID="4558-4157" and TYPE="vfat".
macOS: diskutil list shows the key's partition, WipeReports, of 268.4 MB, and
diskutil info /dev/diskNs1 shows File System Personality: MS-DOS FAT32 and
Volume Name: WipeReports.
The agent itself checks the partition's type, name and serial before using the key.
Never do this
Never rename the key, never format it, and never let a tool "repair" it by formatting it. The agent
recognizes the key by its exact name, WipeReports with this case, and its serial: a renamed or
formatted key is ignored, and the session is refused with
No reports partition: start from a USB key of the ISO, or plug in a reports key. To recover such
a key, copy its files to your computer, then write the image again.
What the key holds after a session
exawipe.conf the session file, at the root
proofs/<session>.der the proof of one session, encrypted for the portal
proofs/<session>.logs.gz the logs of that session
proofs/<session>.ids.json the session's disks, written before erasing them
proofs/index.txt one line per proof, in plain text
proofs/reserved.bin room kept for the proof of the session in progress
support/<date>.tar.gz logs for support, when asked forexawipe.conf is the session file: who carries out the erasure and the other values you want in
the proofs. See Prepare a session in advance.
index.txt ends each proof's line with its delivery status:
stored: the proof is on the key and the portal has not acknowledged it. Upload the
.der from the portal's Proofs page.
accepted or final: the portal has the proof.
Delete a proof only when the agent lists its session as safe to delete (see
When the stick is full), and then every file in proofs/ whose
name starts with that session's identifier. Delete nothing else in proofs/: even a proof the
portal refused may have its only intact copy there, and after a power cut a .der.tmp file may be
the only trace of a proof.
Files that your computer adds (System Volume Information, .Spotlight-V100, .fseventsd,
.TemporaryItems, ._*) are ignored by the agent. Eject the key before unplugging it from your
computer.
What the key exposes
The proofs are encrypted for the portal: whoever holds the key cannot read them. exawipe.conf
holds the name and email of the person carrying out the erasure in clear, and the logs and the
index are in clear too. Keep the key as you would keep a list of your technicians.