f27ec770fc
Observed on the operator's machine 2026-10-30 while reinstalling to put the app to use. Four months after the package was purged, a fresh install found ~/.config/Signal/sql/db.sqlite (54,214,656 bytes, mtime 2026-06-21), tried to open it, and aborted before the linking screen: MainSQL: sqlite(SQLITE_NOTADB): file is not a database in PRAGMA journal_mode = WAL MainSQL: migrateDatabase: Migration without cipher change failed sql.initialize was unsuccessful; returning early The SQLCipher key in config.json no longer resolved. The UI named nothing and offered only 'Delete data and restart', which discards the history. Moving the config directory aside fixes it; nothing in the product says so. Recorded as a medium finding, status open. The score does not move: 76.4 / B. local_data_exposure was already 5 for exactly this behaviour, and a finding is evidence, not a point. What changes is that the number now has a receipt instead of a rationale. Artifact: Servetus/00-Artifacts/2026/10-Oct/30/clu-signal-startup-failure/ main.log.excerpt - the failing run, verbatim 00-provenance.txt - package version, file sizes, sha256 of the retained db Retained state moved to ~/Signal-backup-2026-10-30-0026, not deleted.
10 lines
No EOL
268 B
JSON
10 lines
No EOL
268 B
JSON
{
|
|
"digest": "e557e117f60a43f5023ebb2ebe51978c9a20aa1bcffca920623f79c92f0343d3",
|
|
"algorithm": "sha256",
|
|
"file": "catalog.json",
|
|
"byte_length": 92427,
|
|
"rebuilt_at": "2026-10-30T05:31:05.573Z",
|
|
"method_version": "btr-0.1",
|
|
"products": 137,
|
|
"assessed": 1
|
|
} |