element-hq / element-hq/element-x-android
io.element.e2ee in .wellknown/client doesn't work
- Dominant language
- Kotlin
- Stars
- 2.4k
- Forks
- 624
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 149
Description
### Steps to reproduce
1. Add io.element.e2ee : {default: false} to .wellknown/client
2. Start a Start
### Outcome
#### What did you expect?
New Rooms are not E2EE
#### What happened instead?
Rooms are E2EE and ignores the Value from .wellknown/client to have be not E2EE
### Your phone model
Nothing Phone (1)
### Operating system version
Android 13
### Application version and app store
Develop
### Homeserver
messenger.3dns.eu
### Will you send logs?
No
### Are you willing to provide a PR?
No
Contributor guide
Research direction
Start with the .wellknown/client configuration entry and trace how the io.element.e2ee default is read when creating a room. Reproduce with default set to false on Android, then verify that newly created rooms are not encrypted while other room-creation behavior remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100