|  | Commit message (Collapse) | Author | Age | Lines | 
|---|
| | 
| 
| 
| 
| | As far as I can see this isn't remotely exploitable (and if it were it
would be just DoS of the child process), but i'm still looking into it | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| | It's basically prepending the organization id, appending the default MUC
host from the success packet, and generating a slug based on the name
for the middle part, which is replacing a few characters with
underscores and doing a unicode aware lowercasing.
Includes tests, which are useless other than validating the initial
implementation with the test vectors that i already tested manually.
Guaranteed to detect zero breakages in the future. Good test code. | 
| | 
| 
| 
| 
| 
| 
| | I can't believe the tests did something!
Returning the bare jabber_buddy when asking for GET_BUDDY_EXACT is now
acceptable, since the google talk typing commit. | 
| | 
| 
| 
| 
| 
| 
| | Used uncrustify, with the configuration file in ./doc/uncrustify.cfg
Commit author set to "Indent <please@skip.me>" so that it's easier to
skip while doing git blame. | 
| | |  | 
| | 
| 
| 
| 
| | of storing full JIDs belongong to a contact. | 
| | |  | 
| | 
| 
| 
| 
| | broken. :-( | 
| | 
| 
| 
| 
| 
| 
| | since apparently that's how the RFC wants it. (While the rest of the JID
should be case IN-sensitive. Consistency is hard to find these days...) Also
extended the unittests a little bit. Closes #422. | 
|  |  |