| Commit message (Collapse) | Author | Age | Lines |
... | |
| |_|_|_|_|_|_|_|_|/ / / / / /
|/| | | | | | | | | | | | | |
| | | | | | | | | | | | | | |
| | | | | | | | | | | | | | |
| | | | | | | | | | | | | | |
| | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | |
Jabber server returns an empty <iq type="result"/> response to the session
establishment request (which is valid and actually done by the example, but
my test Jabberd shows different behaviour). Fixed.
|
| | | | | | | | | | | | | | |
| | | | | | | | | | | | | | |
| | | | | | | | | | | | | | |
| | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | |
because some very picky jabberd's don't like it. (Fixes Bug #569)
|
| |/ / / / / / / / / / / / /
|/| | | | | | | | | | | | |
| | | | | | | | | | | | | |
| | | | | | | | | | | | | |
| | | | | | | | | | | | | |
| | | | | | | | | | | | | | |
jabberd's including Zimbra's. Thanks to jMCg and balzar in #bitlbee for
helping with figuring this out.
|
| | | | | | | | | | | | | | |
|
|/ / / / / / / / / / / / /
| | | | | | | | | | | | |
| | | | | | | | | | | | |
| | | | | | | | | | | | |
| | | | | | | | | | | | | |
more consistent. Except for free-for-chat, which is nuts anyway.
|
| |_|_|_|_|_|_|_|_|_|_|/
|/| | | | | | | | | | | |
|
| |_|_|_|_|_|/ / / / /
|/| | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | | |
incorrect, so stop spamming. Ideally it should return a feature-not-
implemented but I'll do that later.
|
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | | |
servers, sending a "you left this chat" without first acknowledging you
entering it.
|
| |_|_|_|_|_|_|_|_|/
|/| | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
chatrooms. Doesn't seem to be Google Talk specific, other than that this
is the first time I see empty <x xmlns="http://jabber.org/protocol/muc#user"/>
elements that cause this crash.
A more proper/efficient fix may be to just move the break outside the inner if.
|
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
when the user logs in from mulitple locations) and the irc->debug setting
shouldn't be read from inside the IM modules.
|
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
password-protected rooms *really* works.
|
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
a password in the IRC JOIN command).
|
| |_|_|_|_|/ / / /
|/| | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
when the given value is not accepted. This to allow certain variables
actually be set to NULL (server, for example). This should fully close
#444.
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
MD5 hashes instead of a known MD5 hash with a number. Just to make it
harder to confuse BitlBee by sending it faked responses to packets.
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
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.
|
| | | | | | | | | |
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
numbers, adding 80 and 443. Partially closes #265.
|
| |_|_|_|/ / / /
|/| | | | | | | |
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Got rid of the bogus window handler pointer as the first argument to the
callback.
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| |_|_|_|_|_|/
|/| | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Jabber module.
|
| |_|_|_|_|/
|/| | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
internal buddy list a little bit earlier. This should deal better with
Jabber servers that send presence information of a new buddy before the
roster push.
|
|\ \ \ \ \ \ |
|
| | | | | | | |
|
| |_|_|_|/ /
|/| | | | |
| | | | | |
| | | | | |
| | | | | | |
described in RFC 2831 secion 7.1 (the #rule description). Closes bug #362.
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
chatroom. Until now they were ignored, which might make backlogs a little
bit confusing.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
clients interested in capabilities can cache discovery info, so they don't
have to ask about it every time you/they log in.
|
| |_|_|_|/
|/| | | |
| | | | |
| | | | |
| | | | |
| | | | | |
cached packets are removed after about ten minues instead of something
between one and two minutes. Closes one issue in #354.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
ignored if the connection's dead already. Necessary if using GLib for event
handling for now. :-/
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
possible.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
already. I don't want to know how long it took me to find out...
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
jabber_pkt_presence (presence.c:174). Valgrind-Wilmer: 1-0.
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | | |
do complicated things with multiple resources. (There were two bugs and
some duplicated code, so I moved things around a bit.)
|
| | | |
| | | |
| | | |
| | | |
| | | | |
in upper case while "Error:" wasn't .... that doesn't really make sense.
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
usage bug.
|
| |_|/
|/| |
| | |
| | |
| | | |
to chat_invite).
|
| |/
|/|
| |
| |
| | |
connect failure.
|
| | |
|
| |
| |
| |
| |
| |
| | |
jabber_chat_by_jid() (with the right name) to conference.c, I don't know
what it was doing in jabber_util.c.
|
|/
|
|
|
| |
IQ packets to jabber_util so I can reuse it for certain presence packets.
|
|
|
|
|
|
| |
from other BitlBees won't be picked up accidentally. Might also want to
randomize the per-packet IDs because they're still predictable.
|
|
|
|
|
|
| |
<presence type=unavailable> tag properly and keeps showing the buddy as
on-line. (When the tag comes from a bare JID.)
|
|
|
|
|
| |
I ever need SHA256 ;-)).
|
| |
|