ハッシュでデータ整合性を検証する方法
ハッシュ比較を使って、偶発的な破損か意図的な改ざんかを問わず、データの変化を検出します。
问题
以前記録したハッシュを使って、データが既知の正常な状態から変化していないことを確認する必要があります。
前提条件
- ハッシュ関数の理解
- ハッシュ値を保存・取得できること
ステップ
-
1. Record the baseline hash
Compute a hash (SHA-256 recommended) of the data in its known-good state. Store this hash in a secure, separate location. The hash serves as a compact fingerprint of the original data.
入力original file输出SHA-256: a1b2c3... -
2. Re-hash the current data
At a later time, compute the hash of the data again using the same algorithm and encoding. Any change — even a single bit — will produce a completely different hash due to the avalanche effect.
入力current file输出SHA-256: d4e5f6... -
3. Compare and interpret
If the hashes match, the data is unchanged. If they differ, the data has been modified. For accidental corruption (e.g., disk errors), this detects the problem. For intentional tampering, the hash must be stored somewhere the attacker cannot modify.
入力a1b2c3... == d4e5f6...?输出DIFFERENT — data changed
期待される結果
ベースラインハッシュが記録されてからデータが変わったかどうかについての、明確な Yes/No の答え。
よくあるエラー
- Using a weak hash like CRC32 for security
- CRC32 detects accidental corruption but is trivial to collide. Use SHA-256 for tamper detection.
- Storing the hash next to the data
- If an attacker can modify the data, they can also recompute and replace the hash. Store the hash in a separate, trusted location.
トラブルシューティング指引
- If hashes differ unexpectedly, check for encoding or line-ending changes before assuming corruption.
- Use a hash comparison tool that shows both values for easy inspection.
セキュリティ上の制限
- Hash comparison detects changes but cannot identify what changed. For that, use a diff tool.
- All hashing is local.