[GH-ISSUE #7215] Model change hash detection feature #4581

Open
opened 2026-04-12 15:30:35 -05:00 by GiteaMirror · 0 comments
Owner

Originally created by @jasonculligan on GitHub (Oct 15, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/7215

When I download a model and then manually flip a bit or two in the blob, there is no apparent check or complaint that the hash has changed. I've tried both quitting a running ollama prompt that uses the model and restarting it, and stopping and restarting the service. I can of course confirm that the SHA256 does indeed change. This leads me to believe that there is no checksum tests to ensure that the model has not been changed on disk, either accidentally or maliciously, so protection or detection of malicious or compromised models.

Originally created by @jasonculligan on GitHub (Oct 15, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/7215 When I download a model and then manually flip a bit or two in the blob, there is no apparent check or complaint that the hash has changed. I've tried both quitting a running ollama prompt that uses the model and restarting it, and stopping and restarting the service. I can of course confirm that the SHA256 does indeed change. This leads me to believe that there is no checksum tests to ensure that the model has not been changed on disk, either accidentally or maliciously, so protection or detection of malicious or compromised models.
GiteaMirror added the feature request label 2026-04-12 15:30:35 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#4581