processone / processone/ejabberd
Stream incorrectly closed after IBR remove
Open
Nobody has claimed this yet.
Component:XMPP Compliance
- Dominant language
- Erlang
- Stars
- 6.7k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
Environment
- ejabberd version: 19.05
Bug description
If a user removes his account via IBR <remove>, ejabberd doesn't end the stream with the appropriate stream error <not-authorized>.
Further if i send stanzas to the server, after i sent <remove> the server ends the stream with <conflict> (text: User Removed)
which seems like ejabberd removes the user from the database before it ends the stream, which seems problematic.
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 IBR flow described for ejabberd 19.05 and trace how the stream is terminated after account removal. Check that the stream ends with rather than (User Removed), including when further stanzas are sent.
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
- Mostly clear
- Newbie friendliness
- 35/100