-
v1.5.2-beta
Pre-releasereleased this
2026-09-11 22:19:16 +00:00 | 243 commits to master since this releaseSecurity in 1.5.2-beta
- New API tokens' secrets were kept in the queue history — creating a token stored deSEC's response, including the token's one-time secret, as is: it was shown in the Queue page's detail panel and written in plain text to
queue_history.json(readable only by your user). The queue now keeps a copy of each response withtokenvalues replaced by(redacted); only the token dialog gets the secret, once. History files written by earlier versions are scrubbed when the app starts, even with queue history persistence switched off. If a token created with an earlier version is still in use and your~/.config/desecqthas been backed up or synced anywhere, consider replacing it
Changed in 1.5.2-beta
- README rewritten — install routes (AppImage, RPM, from source), use, rate limiting, DNSSEC and subdomains, privacy with what is kept on disk, documentation and support sections
- Security reports go to support@jdneer.com — named in SECURITY.md and the README
- Project links point at git.jdneer.com — the About page's project link and the changelog link opened GitHub
Fixed in 1.5.2-beta
- README license link — pointed to
LICENSE; the file isLICENSE.txt
Technical Improvements in 1.5.2-beta
scripts/test_api_queue.py(9 tests) runs in CI with the other headless unit tests
Downloads
-
Source code (ZIP)
1 download
-
Source code (TAR.GZ)
1 download
- New API tokens' secrets were kept in the queue history — creating a token stored deSEC's response, including the token's one-time secret, as is: it was shown in the Queue page's detail panel and written in plain text to