Synapse: Synapse Server Hardening Best Practices [Security]

Created on 5 May 2019 · 3Comments · Source: matrix-org/synapse

Hi,

I was wondering what the best practices are for hardening a Synapse server?

For example, I noticed Synapse listens on http://127.0.0.1:8008

Does it make sense to get a local certificate to change it to https://127.0.0.1:8008 ?

I hope we can share ideas.

Thank you.

Source

brainscar

👍2

Most helpful comment

I can write a wiki article if everyone helps with ideas.

brainscar on 5 May 2019

👍3

All 3 comments

I can write a wiki article if everyone helps with ideas.

brainscar on 5 May 2019

👍3

想知道怎么查看已经安装的synapse的版本
还有就是怎么版本控制

yang202 on 24 May 2019

I second this request; it will make version management a bit easier, since
we won't have to guess how out-of-date our rooms are.

On Thu, May 23, 2019 at 9:15 PM yang202 notifications@github.com wrote:

想知道怎么查看已经安装的synapse的版本
还有就是怎么版本控制

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/matrix-org/synapse/issues/5141?email_source=notifications&email_token=ACBYGLK7336VZOWHPA7LT2LPW46S3A5CNFSM4HK4GBO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWD4QYA#issuecomment-495437920,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACBYGLK7HYQX7YOQKUPD3STPW46S3ANCNFSM4HK4GBOQ
.