Repository navigation
Security fixes
- Validate Gotify client tokens against an approved Gotify instance before saving a device registration or restarting WebSocket connections.
- Use parameterized SQLite queries for device and registration data.
- Remove the startup log entry that exposed the full Gotify client token. Rotate any tokens included in previously shared logs.
- Update OpenAPI, SQLite, Dapper, Scalar, and Websocket.Client dependencies.
Docker upgrade
Keep the existing api-data volume mounted at /app/data. The Assistant reloads saved registrations after the container restarts, so existing devices can continue receiving push notifications.
If you use External Instance, set GOTIFY_REGISTRATION_URLS before updating. Use the Gotify base URL entered in the app so the same app can register additional devices or register again after signing out or reinstalling.
GOTIFY_REGISTRATION_URLS='https://gotify.example.org'For a separate validation route to the same Gotify instance, use https://gotify.example.org|http://gotify. Separate multiple entries with semicolons. An empty setting disables new automatic registrations.
Manual Local Instance setup continues to use GOTIFY_URLS, GOTIFY_CLIENT_TOKENS, and SECNTFY_TOKENS.
See the installation and upgrade guide.
Acknowledgments
Thanks to @CnHack3r for reporting the security issues addressed in this release.