# 🔐 SHA256 Verification
## 🎯 Objective
Verify that the downloaded Ledger Live AppImage has not been corrupted or altered before replacing the existing binary.
This adds a simple integrity check to the update workflow.
---
## 🧠 Why This Matters
An AppImage is a standalone executable.
Before moving it into the permanent location, it is good practice to verify:
- the download completed properly
- the file is not corrupted
- the checksum matches the official release value
This is especially useful when manually managing binaries.
---
## ✅ Step 1 — Generate the local SHA256 hash
Run:
---
## ✅ Step 2 — Compare with the official hash
Check the SHA256 value published by Ledger for that exact version and verify that:
- the version matches
- the filename matches
- the hash matches exactly
If the hashes differ, do **not** use the file.
---
## ⚠️ Important
A valid file size alone is not enough.
Example:
- correct size → suggests a complete download
- matching SHA256 → confirms integrity
Both checks are useful, but SHA256 is the stronger verification.
---
## ✅ Recommended Verification Flow
### 1. Check file size
---
## ❌ If the Hash Does Not Match
Do not move the file into `~/AppImages`.
Instead:
rm ~/Downloads/ledger-live-desktop-2*.AppImage
Then download it again and repeat the check.
---
## 🧩 Practical Note
For routine use, checking file size may be enough to catch obvious failures such as the earlier **75-byte corrupted AppImage**.
For stronger assurance, especially with wallet-related software, SHA256 verification is the better habit.
---
## 💡 Guiding Principle
> Verify first. Replace second.