-
Daniel Gerhardt authored6019ecda
Changelog
2.3.4
This release fixes a minor security vulnerability which allowed an attacker to remove a MotD from a session without being the creator.
Additional changes:
- Libraries have been upgraded to fix potential bugs
2.3.3
This release fixes a security vulnerability caused by the CORS implementation.
Origins allowed for CORS can now be set in the configuration via
security.cors.origins
. (Reported by Rainer Rillke at Wikimedia)
Additional changes:
- Libraries have been upgraded to fix potential bugs
2.2.2
This release fixes a security vulnerability caused by the CORS implementation.
Origins allowed for CORS can now be set in the configuration via
security.cors.origins
. (Reported by Rainer Rillke at Wikimedia)
Additional changes:
- Libraries have been upgraded to fix potential bugs
2.1.2
This release fixes a security vulnerability caused by the CORS implementation. Support for cross-origin requests has been removed. Use ARSnova version 2.2 or newer for proper CORS. (Reported by Rainer Rillke at Wikimedia)
Additional changes:
- Libraries have been upgraded to fix potential bugs
2.0.4
This release fixes a security vulnerability caused by the CORS implementation. Support for cross-origin requests has been removed. Use ARSnova version 2.2 or newer for proper CORS. (Reported by Rainer Rillke at Wikimedia)
Additional changes:
- Libraries have been upgraded to fix potential bugs
2.3.2
This release fixes a security vulnerability in the account management API. It is highly recommended to upgrade if you are using database authentication.
Additional changes:
- Libraries have been upgraded to fix potential bugs
2.2.1
This release fixes a security vulnerability in the account management API. It is highly recommended to upgrade if you are using database authentication.
Additional bug fixes:
- The
security.authentication.login-try-limit
setting now works as intended.
2.1.1
This release fixes a security vulnerability in the account management API. It is highly recommended to upgrade if you are using database authentication.
Additional changes:
- Libraries have been upgraded to fix potential bugs
2.0.3
This release fixes a security vulnerability in the account management API. It is highly recommended to upgrade if you are using database authentication.
Additional changes:
- Libraries have been upgraded to fix potential bugs
- Some unnecessary log warnings for Websocket communication are filtered
2.3.1
Bug fixes:
- Case-insensitive user IDs are now correctly handled for LDAP authentication.
- LDAP authentication does no longer request unnecessary user attributes.