processone / processone/ejabberd
Ejabberd is not able to serve the appropriate cert
Open
Nobody has claimed this yet.
Note:Needs more info
- Dominant language
- Erlang
- Stars
- 6.7k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
Environment
- ejabberd version: 22.05
- Erlang version:
24 - OS: Linux (Debian)
- Installed from: official deb/rpm
Configuration:
certfiles:
- abc.com # given by godaddy
- xyz.com # given by lets encrypt for *.xyz.com
Bug description
Ejabberd is not able to serve the appropriate cert if multiple certs. If I am making a request to ejabberd with r0.xyz.com as the SNI, then it serves cert given toabc.com
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue on ejabberd 22.05 with the shown certfiles configuration on Debian, making an SNI request for r0.xyz.com. Trace the certificate-selection entry point and verify that the appropriate certificate is served for each SNI name; no source files or tests are identified in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- erlang
- Domain
- backend, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100