Synapse 0.33.3.1 (2018-09-06)
=============================

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

- Fix an issue where event signatures were not always correctly validated ([\#3796](https://github.com/matrix-org/synapse/issues/3796))
- Fix an issue where server_acls could be circumvented for incoming events ([\#3796](https://github.com/matrix-org/synapse/issues/3796))

Internal Changes
----------------

- Unignore synctl in .dockerignore to fix docker builds ([\#3802](https://github.com/matrix-org/synapse/issues/3802))

remove synctl from .dockerignore

Use the actual origin for push transactions, rather than whatever the remote
server claimed.

We should check that both the sender's server, and the server which created the
event_id (which may be different from whatever the remote server has told us
the origin is), have signed the event.

Remove unnecessary resolve_events_with_state_map

matrix-synapse-auto-deploy is no longer maintained. 

fix bug where preserved threepid user comes to sign up and server is …

Make sure that we close db connections opened during init

fix #3445 - do not use itervalues() on SortedDict()

itervalues(d) calls d.itervalues() [PY2] and d.values() [PY3]
but SortedDict only implements d.values()

don't return non-LL-member state in incremental sync state blocks

This gives clearer messages when someone gets it wrong

We should explicitly close any db connections we open, because failing to do so
can block other transactions as per
https://github.com/matrix-org/synapse/issues/3682.

Let's also try to factor out some of the boilerplate by having server classes
define their datastore class rather than duplicating the whole of `setup`.

Change admin_uri to admin_contact in config and errors

Fix checking if service notice room is already tagged