jabberd2 cannot cope with empty responses that contain Base64 padding only.
Bug #964951 reported by
Patrick R McDonald
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Jabberd |
Incomplete
|
High
|
Patrick R McDonald | ||
Bug Description
I worked with the Guardian Project developers in testing Gibberbot. We
believe we discovered an issue with how jabberd2 handles empty responses
that contain Base64 padding only. Please note, we have not checked the
RFC as we haven't had the available cycles. We figured someone here
could answer it better. Below is the URI to the relevant message to the
GP list.
https:/
This issue occured across multiple packages on both CentOS and Debia.
Revision history for this message
| Tomasz Sterna (smoku) wrote | #1 |
| Changed in jabberd2: | |
| status: | New → Invalid |
Revision history for this message
| Tomasz Sterna (smoku) wrote | #2 |
| Changed in jabberd2: | |
| assignee: | nobody → Tomasz Sterna (smoku) |
| importance: | Undecided → Medium |
| status: | Invalid → In Progress |
Revision history for this message
| Tomasz Sterna (smoku) wrote | #3 |
| Changed in jabberd2: | |
| assignee: | Tomasz Sterna (smoku) → Patrick R McDonald (marlowe-c) |
| importance: | Medium → High |
| status: | In Progress → Incomplete |
Revision history for this message
| Patrick R McDonald (marlowe-c) wrote | #4 |
To post a comment you must log in.
Closing of inactivity.