magdev/bau-pm-pdf-tools
1
Fork 1
Code Issues Pull Requests Actions Releases 3 Activity

Release v0.1.2: the signing tool keeps no signature on the device
Release / release (push) Successful in 21m0s
Details
CI / gate (push) Successful in 23m56s
Details

Browse Source 
PDF.js's signature dialog saved every signature in the PDF origin's
localStorage, "save" ticked on every open, so the next person on a
shared device was offered the previous one's, a bau-pm logout
included. The glue now wipes that store, refuses its writes, holds the
save box off and hides it, and hides the dialog's Bild tab (#1, bau-pm
BAU-260, PLAN.md §2.77 there).

Gate, the same one CI runs, on this tree: shellcheck clean over
scripts/; the image built with --pull, BentoPDF v2.8.8 verified at its
pinned commit, 2776 pages tagged with a CSP carrying no host, nginx
1.31.8; the zero-hosts gate drove all 117 tool pages and nothing left
the origin; the new signatures gate: 0 findings (9 on v0.1.0).

bau-pm pins this as v0.28.1.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
magdevandClaude Opus 5.5 committed 2026-11-01 09:51:53 +01:00
1 parent 4248bc791a
commit 4326ea68d9
1 file changed
+4
Download Patch File Download Diff File Expand all files Collapse all files
CHANGELOG.md
+4
View File
@@ -4,6 +4,10 @@ All notable changes to this project are documented in this file. The format is b
## [Unreleased] ## [Unreleased]
## [0.1.2] - 2026-11-01
The signing tool keeps no signature on the device. PDF.js's signature dialog saved every signature in the browser, ticked by default, for the PDF tools address rather than for a bau-pm user, so the next person on a shared tablet or site office PC was offered the previous one's. Signing now means typing or drawing the signature each time, and the image tab is gone (issue #1, bau-pm BAU-260).
### Security ### Security
- The signing tool keeps no signature on the device (issue #1, bau-pm BAU-260). PDF.js's signature dialog saved every signature in the browser's `localStorage`, with *Unterschrift speichern* ticked by default, for this address rather than for a bau-pm user, so the next person on a shared tablet or site office PC was offered the previous one's signature, typed, drawn or traced from an uploaded image, and logging out of bau-pm did not clear it. Every page now deletes that store and refuses its writes, and the dialog's save box is held unticked and hidden. Signatures a device saved before are deleted on its first visit after the update. - The signing tool keeps no signature on the device (issue #1, bau-pm BAU-260). PDF.js's signature dialog saved every signature in the browser's `localStorage`, with *Unterschrift speichern* ticked by default, for this address rather than for a bau-pm user, so the next person on a shared tablet or site office PC was offered the previous one's signature, typed, drawn or traced from an uploaded image, and logging out of bau-pm did not clear it. Every page now deletes that store and refuses its writes, and the dialog's save box is held unticked and hidden. Signatures a device saved before are deleted on its first visit after the update.