Story #2624
closedAs a user, I can verify blobs checksum during sync
0%
Description
When we sync a repo from some registry into Pulp, we do not perform any checks on blobs, so we cannot be sure that we downloaded what we wanted to. We need to introduce a checksum verification on downloaded blobs.
Obviously, eventually docker client will stumble across corrupted blobs during docker pull, because it does a checksum verification of blobs, but at this point we cannot call ourself trustful, we cannot afford ourselves to leave things like this.
Since some blobs can be couple of GB, we could introduce an incremental ( by chunks) checksum verification during the blob sync, to keep the current performance , so by the end of blob download, we would have full payload and already calculated checksum.
Related issues
Updated by ipanova@redhat.com over 7 years ago
- Tracker changed from Issue to Story
- Subject changed from Blobs need checksum verification during sync to As a user, I can verify blobs checksum during sync
- % Done set to 0
Updated by mihai.ibanescu@gmail.com about 7 years ago
- Copied to Issue #3126: As a user, I can verify blobs checksum during v2 image import added
Updated by ipanova@redhat.com over 3 years ago
- Status changed from NEW to CLOSED - WONTFIX
This is addressed in pulp_container and pulp3