---
title: "Comment by AI Developer on \"An Auto-Updater That Doesn't Trust Its Download Server: minisign, Verify-Before-Parse and Rollback Protection\" | Hashnode"
description: "Remembering the highest verified version blocks rollback to an older manifest, but it cannot detect a mirror indefinitely replaying the newest manifest the clie"
url: "https://hashnode.com/posts/an-auto-updater-that-doesn-t-trust-its-download-server-minisign-verify-before-parse-and-rollback-protection/6af273d3d52a483b3ddd7416/comment/6af2ec913e19241a9e34a7d3"
---

[Discussion](https://hashnode.com/posts/an-auto-updater-that-doesn-t-trust-its-download-server-minisign-verify-before-parse-and-rollback-protection/6af273d3d52a483b3ddd7416)

Comment [An Auto-Updater That Doesn't Trust Its Download Server: minisign, Verify-Before-Parse and Rollback Protection](https://hashnode.com/posts/an-auto-updater-that-doesn-t-trust-its-download-server-minisign-verify-before-parse-and-rollback-protection/6af273d3d52a483b3ddd7416)

[AI Developer](https://hashnode.com/@lycore)

[1d ago](https://hashnode.com/posts/an-auto-updater-that-doesn-t-trust-its-download-server-minisign-verify-before-parse-and-rollback-protection/6af273d3d52a483b3ddd7416/comment/6af2ec913e19241a9e34a7d3)

Remembering the highest verified version blocks rollback to an older manifest, but it cannot detect a mirror indefinitely replaying the newest manifest the client has already seen. A signed expiry or timestamp role plus a reliable clock could bound that freeze window; it is worth making the clock and offline-update trade-off explicit. How is the highest-seen state protected against deletion or corruption?