Signed-off-by: Jason Robinson <jasonr@matrix.org>

Signed-off-by: Jason Robinson <jasonr@matrix.org>

Signed-off-by: Jason Robinson <jasonr@matrix.org>

Signed-off-by: Jason Robinson <jasonr@matrix.org>

Instead document it commented out.

Signed-off-by: Jason Robinson <jasonr@matrix.org>

Signed-off-by: Jason Robinson <jasonr@matrix.org>

Signed-off-by: Jason Robinson <jasonr@matrix.org>

This allows the OpenID userinfo endpoint to be active even if the
federation resource is not active. The OpenID userinfo endpoint
is called by integration managers to verify user actions using the
client API OpenID access token. Without this verification, the
integration manager cannot know that the access token is valid.

The OpenID userinfo endpoint will be loaded in the case that either
"federation" or "openid" resource is defined. The new "openid"
resource is defaulted to active in default configuration.

Signed-off-by: Jason Robinson <jasonr@matrix.org>

Check all possible variants of openid and federation listener on/off
possibilities.

Signed-off-by: Jason Robinson <jasonr@matrix.org>

For all the homeserver classes, only the FrontendProxyServer passes
its reactor when doing the http listen. Looking at previous PR's looks
like this was introduced to make it possible to write a test, otherwise
when you try to run a test with the test homeserver it tries to
do a real bind to a port. Passing the reactor that the homeserver
is instantiated with should probably be the right thing to do anyway?

Signed-off-by: Jason Robinson <jasonr@matrix.org>

Check all possible variants of openid and federation listener on/off
possibilities.

Signed-off-by: Jason Robinson <jasonr@matrix.org>

For all the homeserver classes, only the FrontendProxyServer passes
its reactor when doing the http listen. Looking at previous PR's looks
like this was introduced to make it possible to write a test, otherwise
when you try to run a test with the test homeserver it tries to
do a real bind to a port. Passing the reactor that the homeserver
is instantiated with should probably be the right thing to do anyway?

Signed-off-by: Jason Robinson <jasonr@matrix.org>

Allows running parameterized tests. BSD license.

Signed-off-by: Jason Robinson <jasonr@matrix.org>

Signed-off-by: Jason Robinson <jasonr@matrix.org>

Fix bug when removing duplicate rows from user_ips

Config option to disable requesting MSISDN on registration

This was caused by accidentally overwritting a `last_seen` variable
in a for loop, causing the wrong value to be written to the progress
table. The result of which was that we didn't scan sections of the table
when searching for duplicates, and so some duplicates did not get
deleted.

All this magic is redundant.

* remove dh_params and set better cipher string

Implement server side of MSC1794 - Federation v2 Invite API

Add groundwork for new versions of federation APIs

* Migrate encryption state on room upgrade

Signed-off-by: Andrew Morgan <andrew@amorgan.xyz>

* Add changelog file

* Fix race when persisting create event

When persisting a chunk of DAG it is sometimes requried to do a state
resolution, which requires knowledge of the room version. If this
happens while we're persisting the create event then we need to use that
event rather than attempting to look it up in the database.

* Tweak code coverage settings

* Fix manifest

* Newsfile

* Fix commit status?

* Remove redundant WrappedConnection

The matrix federation client uses an HTTP connection pool, which times out its
idle HTTP connections, so there is no need for any of this business.

Just got very confused about the fact that the headers are only an output, not
an input.

Update Dependencies

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

Since 0.13.0, pymacaroons works correctly with pynacl, so there
isn’t any more reason to depend on an outdated pynacl fork.

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>