censor/Censor
1
37
Fork
You've already forked Censor
3

feat: warning for insufficient redactions #144

Open
opened 2026年03月16日 12:51:06 +01:00 by mahlzahn · 0 comments

Description

Given that there are (and possibly always will be) some insufficient redactions (currently: form fields (widgets), some graphics #134, signatures #98, ...), maybe add warnings for users who want to use Censor for secure redaction.

Context: currently, only (削除) 86-92% (v0.5.0) (削除ここまで) 90-96% (with !151) of test PDF files are redacted properly, see #110!

Implementation

  • Generally warn about the limits of Censor
    • from time to time or at first opening or at first opening after an update?
    • in the application description on Flathub (in appstream data
    • in the about dialog or potentially in a help page?
  • If a document cannot be opened or saved
  • Detect insufficient redaction
    • after opening a document
      • try full page redaction !124 and verify that it works, else warn user that redactions in this document may not be secure
      • or/and check if document contains non-redactable elements
    • after saving a document with redactions
      • check if all rectangles from remaining graphics do not overlap with redactions, else warn user that some graphics redactions may not have been applied properly
      • check for hidden text?
## Description Given that there are (and possibly always will be) some insufficient redactions (currently: form fields (widgets), some graphics #134, signatures #98, ...), maybe add warnings for users who want to use Censor for secure redaction. Context: currently, only ~86-92% (v0.5.0)~ 90-96% (with !151) of test PDF files are redacted properly, see #110! ## Implementation - [ ] Generally warn about the limits of Censor - [ ] from time to time or at first opening or at first opening after an update? - [ ] in the application description on Flathub (in appstream data - [ ] in the about dialog or potentially in a help page? - [x] If a document cannot be opened or saved - [ ] Detect insufficient redaction - after opening a document - [ ] try full page redaction !124 and verify that it works, else warn user that redactions in this document may not be secure - [ ] or/and check if document contains non-redactable elements - after saving a document with redactions - [x] check if all rectangles from remaining graphics do not overlap with redactions, else warn user that some graphics redactions may not have been applied properly - [ ] check for hidden text?
mahlzahn added this to the v0.6.0 milestone 2026年03月16日 16:21:26 +01:00
mahlzahn modified the milestone from v0.6.0 to v0.7.0 2026年03月23日 13:32:25 +01:00
mahlzahn modified the milestone from v0.7.0 to v0.7.1 2026年04月03日 22:01:27 +02:00
mahlzahn removed this from the v0.7.1 milestone 2026年04月28日 17:11:06 +02:00
Sign in to join this conversation.
No Branch/Tag specified
main
v0.7.3
v0.7.2
v0.7.1
v0.7.0
v0.6.0
v0.5.0
v0.4.0
v0.3.0
v0.2.0
v0.1.0
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
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
censor/Censor#144
Reference in a new issue
censor/Censor
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?