ktx/pocket_archive
Watch
1
0
Fork
You've already forked pocket_archive
 0
Code Issues 25 Pull requests Releases 5 Packages 1 Wiki Activity Actions

Fixity check from user provided checksum #1

New issue
Closed
opened 2025-12-27 18:01:36 +00:00 by scossu · 1 comment
scossu commented 2025-12-27 18:01:36 +00:00
Owner
Copy link

Implement fixity check via user-provided checksum.

A depositor should be able to provide a pre-computed BLAKE2 checksum at deposit time, as part of the SIP metadata. Pocket Archive should compute the received file's checksum and validate it against the user-provided one.

Special cases for updated files should be considered.

Implement fixity check via user-provided checksum. A depositor should be able to provide a pre-computed BLAKE2 checksum at deposit time, as part of the SIP metadata. Pocket Archive should compute the received file's checksum and validate it against the user-provided one. Special cases for updated files should be considered.
scossu added this to the v1.1.0 milestone 2026-01-07 13:38:53 +00:00
scossu commented 2026-10-01 01:00:29 +00:00
Author
Owner
Copy link

Fixed in 7bf89ef16b.

Fixed in 7bf89ef16b.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
1.1.x
1.0.x
test
v1.0.0
v1.0b14
v1.0rc7
v1.0rc6
v1.0rc5
v1.0rc4
v1.0rc3
v1.0rc2
v1.0rc1
v1.0b13
v1.0b12
v1.0b11
v1.0b10
v1.0b9
v1.0b8
v1.0b7
v1.0b6
v1.0b5
v1.0b4
v1.0b3
v1.0b2
v1.0b1
v1.0a9
v1.0a8
v1.0a7
v1.0a6
v1.0a5
v1.0a4
v1.0a3
v1.0a2
v1.0a1
v1.0a0
Labels
Clear labels   
area/api_cli
Lua API and command-line interface issues.

  
area/apps
Issues related to ancillary executables distributed with PKAR.

  
area/content_model

   
area/framework
General application framework issues.

  
area/infrastructure

   
area/integrity
Data integrity issues. Usually high priority.

  
area/io

   
area/presentation

   
area/preservation

   
area/rdf

   
area/security

   
area/submission

   
area/ui
  
s
blocked

  
s
done

  
s
progress

  
s
testing

  
s
wontfix

  
p
critical
 A major malfunction, data corruption, or missing critical feature. It SHOULD be in the current milestone and SHOULD be resolved ASAP, and a new release cut immediately after fixing.

  
p
high
 A bug that causes significant disruption or missing or incomplete feature that impairs basic workflows. It MUST be in a milestone.

  
p
low
 A bugfix or enhamcement request that does not affect normal usage significantly. It MAY be in a milestone.

  
p
normal
 A bug or missing feature that causes some disruption or forces annoying workarounds. It SHOULD be in a milestone.

  
t
bug

  
t
documentation

  
t
enhancement

  
t
feature

  
t
test

No labels
area/api_cli
area/apps
area/content_model
area/framework
area/infrastructure
area/integrity
area/io
area/presentation
area/preservation
area/rdf
area/security
area/submission
area/ui
s
blocked
s
done
s
progress
s
testing
s
wontfix
p
critical
p
high
p
low
p
normal
t
bug
t
documentation
t
enhancement
t
feature
t
test
Milestone
Clear milestone
No items
No milestone
v1.1.0
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
ktx/pocket_archive#1
No description provided.