Verification

Checksums

Verify the checksum and signature of every image before you write it. A few seconds of checking now beats booting something you never meant to trust.

Saphira-D

Archive: saphira-d.tar.xz
Checksum file: TBC
Algorithm: SHA-256
Published hash: TBC

# with the checksum file alongside the archive
sha256sum -c TBC

# or compare by eye
sha256sum saphira-d.tar.xz
cat TBC

Saphira Linux Earlybird Beta

Archive: saphira.tar.xz
Checksum file: saphira.tar.xz.sha256
Algorithm: SHA-256
Published hash: 919728f474708c5100e81eb37e48650797d6e68e6161788812798898bc658f21

# with the checksum file alongside the archive
sha256sum -c saphira.tar.xz.sha256

# or compare by eye
sha256sum saphira.tar.xz
cat saphira.tar.xz.sha256

Saphira Linux v0 Bootstrap

Archive: saphira-linux-v0.bootstrap.tar.xz
Checksum file: saphira-linux-v0.bootstrap.tar.xz.sha256
Algorithm: SHA-256
Published hash: 765b2833cbaa3ddebd71bbf01d4d24da290cc15c7ee20047444f25b3c5c37f42

# with the checksum file alongside the archive
sha256sum -c saphira-linux-v0.bootstrap.tar.xz.sha256

# or compare by eye
sha256sum saphira-linux-v0.bootstrap.tar.xz
cat saphira-linux-v0.bootstrap.tar.xz.sha256

Saphira Linux Earlybird Beta 2

Archive: TBC
Checksum file: TBC
Algorithm: SHA-256
Published hash: TBC

# with the checksum file alongside the archive
sha256sum -c TBC

# or compare by eye
sha256sum TBC
cat TBC

Why this matters

A checksum proves the file you have is the file that was published. It catches truncated downloads, corrupted storage, a mirror that went wrong, and deliberate tampering. If the checksum does not match, delete the file and download it again. If it still does not match, tell us.