Update ghcr.io/bulwarkmail/webmail Docker tag to v1.18.0 #69
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "renovate/ghcr.io-bulwarkmail-webmail-1.x"
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?
This PR contains the following updates:
1.17.2→1.18.0Release Notes
bulwarkmail/webmail (ghcr.io/bulwarkmail/webmail)
v1.18.0Compare Source
1.18.0 works with Stalwart 1.0, released today, as well as with 0.16. Sign-in, calendars, contacts, files and sending were adapted to what changed in 1.0, and a Stalwart that was moved from 0.16 to 1.0 with Stalwart's migration tool keeps working with the same open tabs. It also fixes the findings of a security review of the whole webmail, more places where an action in a view that mixes accounts could hit another account's message with the same id, and a series of calendar bugs around repeating events. Plugins can show their own search results and a count on their buttons, quick reply can be turned off, and a new device offers to restore your saved account list.
Thank you for your donations:
One-time
Monthly
Upgrading to Stalwart 1.0
stalwart-migrate) copies the data into a new store. Ids and sync state are kept, so Bulwark carries on without reloading anything, but OAuth tokens are not migrated: everyone who signed in with single sign-on, or with a password and a two-factor code, signs in again. Keep the server's public URL the sameSecurity
/api/plugin-approval-statusrefuses plugin packages while user plugins, plugin uploads or their review are turned off. Any signed-in user could fill the admin's review queue and the data directory with packages (GHSA-qc44-275p-gqw9, thanks @oguzyilmaznet)COOKIE_SECURE=true, the unprefixed sidebar-app cookie is no longer trusted behind a TLS proxy that sends noX-Forwarded-Proto, so a sibling subdomain can't add origins to the page'sframe-src(GHSA-cjm9-m826-mh78, thanks @oguzyilmaznet)cid:image no longer hides the rest of the messageconfig.json, the admin password hash and the setup token are written readable only by the app's user, a synced settings file can no longer pass as an admin session, and the setup wizard refuses a session secret under 32 charactersFeatures
email.get,email.getRawandemail.getAttachmenttake an optional account id, and summaries carry itNODE_USE_ENV_PROXY=1is set. Bulwark still checks the address itself and asks the proxy for exactly that address (#1367, thanks @Jan0oo)Fixes
setup.shasks again for a pasted session secret under 32 charactersv1.18.0Compare Source
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.