mix
5e5d157496
A bounce could be recorded as a successful delivery. The log-tailer's Fixed: - A bounce could be recorded as a successful delivery. The log-tailer's - Log-tailer resumes where it stopped instead of jumping to end-of-file on - Level-2 rate limit no longer overshoots under concurrency: messages that Changed: - The project has a single public home: `github.com/mixeme/selfpost`. Codeberg - Code comments no longer cite the archived specification. References like - `docs/code-review.md` is gone. Its plan is finished — phases 0 (bar the - `docs/architecture.md` gained a *Code layers* section: a diagram of - Phase 1 doc/code hygiene (`docs/code-review.md`): removed ~30 stale … (1 more in CHANGELOG) Security: - Pre-release security review (plan § D, model Fable, 2026-08-06): full pass - `saslpasswd2` argv: the application login is now passed after a `--` Added: - Optional password encryption for the two secret-bearing downloads (plan - Domain import accepts an encrypted export: the envelope is detected by its - `selfpost-backup` writes encrypted archives and reads them back: - `TestParseDelivery` covers the exotic mail.log shapes the review asked for - docs: README *Encrypting a backup or export*; `docs/security.md` § … (14 more in CHANGELOG) Removed: - docs: `security.md` — accepted risk «restore old backup revives session rows» Changed: - docs: `implementation-plan.md` trimmed to the sole open v1.x gate — pre-release - docs: `architecture.md` — sessions (SQLite, idle renew, password change), - docs: `development.md` — expanded e2e stack and `release.yml` matrix workflow. - docs: `security.md` — accepted risk for send-log rows stuck at `queued` after - docs: `roadmap.md` — optional send-log / `mail.log` follow-ups under v1.x tail. … (10 more in CHANGELOG) Full detail: CHANGELOG.md (0.5.0).
24 lines
1.2 KiB
HTML
24 lines
1.2 KiB
HTML
{{/* Password fields shared by the full-backup and domain-export forms. The
|
|
checkbox is the switch: unticked, the download keeps its historic plain
|
|
form (.tar.gz / .json); ticked, the file is sealed in a password-encrypted
|
|
envelope (.spbk / .spde). The fields start hidden and are revealed by
|
|
panel.js — with JavaScript blocked they are simply always visible, and the
|
|
server still decides from the checkbox alone. */}}
|
|
{{define "encryptfields"}}
|
|
<div class="encrypt">
|
|
<label class="check">
|
|
<input type="checkbox" name="encrypt" value="1" data-encrypt-toggle>
|
|
<span>Encrypt with a password</span>
|
|
</label>
|
|
<div class="encrypt-fields" data-encrypt-fields>
|
|
<label for="encpw">Password</label>
|
|
<input id="encpw" name="password" type="password" autocomplete="new-password"
|
|
minlength="{{.MinPwLen}}" placeholder="at least {{.MinPwLen}} characters">
|
|
<label for="encpw2">Repeat password</label>
|
|
<input id="encpw2" name="password_confirm" type="password" autocomplete="new-password">
|
|
<p class="muted">Keep this password: without it the file cannot be opened,
|
|
and SelfPost does not store it anywhere.</p>
|
|
</div>
|
|
</div>
|
|
{{end}}
|