Synapse 0.33.1 (2018-08-02)
===========================

SECURITY FIXES
--------------

- Fix a potential issue where servers could request events for rooms they have not joined. (`#3641 <https://github.com/matrix-org/synapse/issues/3641>`_)
- Fix a potential issue where users could see events in private rooms before they joined. (`#3642 <https://github.com/matrix-org/synapse/issues/3642>`_)

Check room visibility for /event/ requests

Make sure that the user has permission to view the requeseted event for
/event/{eventId} and /room/{roomId}/event/{eventId} requests.

Also check that the event is in the given room for
/room/{roomId}/event/{eventId}, for sanity.

Validation for events/rooms in fed requests

Since we're about to look up the events themselves anyway, we can skip the
extra db queries here.

When we get a federation request which refers to an event id, make sure that
said event is in the room the caller claims it is in.

(patch supplied by @turt2live)

Split out DB writes in federation handler

Initial impl of capping MAU

return 404 if room not found

Improvements for Docker usage

rename replication_layer to federation_client

Rewrite cache list decorator

Per the Client-Server API[0] we should return
`M_NOT_FOUND` if the room isn't found instead
of generic SynapseError.

This ensures that /directory/list API returns
404 for room not found instead of 400.

[0]: https://matrix.org/docs/spec/client_server/unstable.html#get-matrix-client-r0-directory-list-room-roomid



Signed-off-by: Serban Constantin <serban.constantin@gmail.com>

Remove pdu_failures from transactions

I have HAD ENOUGH of trying to remember wtf a replication layer is in terms of
classes.

Make EventStore inherit from EventFederationStore