Verify MarkView for Linux
The normal download remains one click. If you prefer to verify it
before running it, new Linux releases include SHA-256 checksums
and a detached signature for both the .deb package and
AppImage.
Loading the current release…
Option 1: Check the SHA-256 checksum
Download your chosen package and SHA256SUMS into the
same directory, then run the commands below. A successful check
prints the downloaded filename followed by OK. The
example defaults to AppImage; the comment shows the one-line change
for the Debian package.
Loading current filenames…SHA-256 files are published beginning with the next MarkView release. The Minisign verification below is available for the current release.
Option 2: Verify the Minisign signature
This provides the stronger check: it proves the downloaded bytes were signed by the same MarkView key embedded in the app's updater. Install Minisign, then run the commands for the file you downloaded.
MarkView's public key ID is
57CD593855331F8F.
The Tauri-generated .sig asset is a base64 wrapper, so the
command explicitly decodes it into the standard Minisign format first.
AppImage
Loading current filenames…Debian / Ubuntu package
Loading current filenames…
Success prints Signature and comment signature verified
and the signed release filename. If verification fails, do not run or
install the download.
What each file proves
SHA256SUMSdetects an incomplete or changed download.- The detached
.sigplus the published public key proves the file was signed by MarkView and has not changed since. - The public key is also attached to each new release and is published at markview.io/markview-updater.pub.