Skip to content

Disable encryption via /.well-known/matrix/client #28397

@frenn

Description

@frenn

Steps to reproduce

Good afternoon.

  1. Launched the synapse server from the Docker-image matrixdotorg/synapse:latest on the domain matrix.example.com.
  2. Launched element-web from the Docker-image vector/element-web on the domain element.example.com.
  3. Everything is fine. The messaging is ok. The calls are working.

Encryption must be disabled. My teammates will lose the keys in a week. :D

  1. Read this:
    https://github.com/element-hq/element-web/blob/develop/docs/e2ee.md#disabling-encryption
  2. Set it up in nginx on the domain matrix.example.com :
location /.well-known/matrix/client {
  return 200 '{"io.element.e2ee": {"force_disable": "true"}}';
  add_header Content-Type application/json;
  add_header "Access-Control-Allow-Origin" *;
}
  1. Checking the setting:
    curl -s https://matrix.example.com/.well-known/matrix/client | jq

I get:

{
    "io.element.e2ee": {
        "force_disable": true
    }
}

Outcome

When creating private chats, encryption is still enabled by default. You can't turn it off.

What did I do wrong?

Operating system

No response

Browser information

No response

URL for webapp

No response

Application version

No response

Homeserver

No response

Will you send logs?

No

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-E2EEO-UncommonMost users are unlikely to come across this or unexpected workflowS-MinorImpairs non-critical functionality or suitable workarounds existT-DefectX-Needs-InfoThis issue is blocked awaiting information from the reporter

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions