| Commit message (Collapse) | Author | Age | Lines |
|---|
| | |
|
| | |
|
| |\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Wilmer van der Gaast 2007-12-02 Imported setuid() patch from Simo Leone <simo@archlinux...> with some
Wilmer van der Gaast 2007-12-02 Forgot to return something in jabber_chat_join_failed().
Wilmer van der Gaast 2007-12-02 Merging a change I should've pulled before committing three other changes.
Wilmer van der Gaast 2007-12-02 Added charset checks on incoming msgs (from the IRC side) to prevent possible
Wilmer van der Gaast 2007-12-02 Handling of presence-error packets (only useful for groupchats now), moved
Wilmer van der Gaast 2007-12-02 Defining DEBUG via CFLAGS so that it'll always be there, even when a file
Wilmer van der Gaast 2007-12-02 Removed retarded printf() (ARGH) and moved the event handling handling of
Wilmer van der Gaast 2007-11-29 printf() in daemons considered harmful.
Wilmer van der Gaast 2007-11-28 Fixed the epoll+ForkDaemon combination. The libevent event handling
|
| | |
| |
| |
| |
| |
| | |
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.
|
| | |
| |
| |
| |
| | |
only one buffer of 2k per transfer now.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* move from out_of_data to is_writable, eliminate buffers
* implement "transfers reject [id]"
* documentation in commands.xml
* implement throughput and cummulative throughput boundaries
* feature discovery before sending
* implement sending over a proxy
(proxy discovery, socks5 client handshake for sending, activate message)
* integrate toxik-mek-ft
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
only a few changes to bitlbees code, mainly the addition of the "transfers"
command.
This is known to work with Kopete, Psi, and Pidgin (formerly known as gaim).
At least with Pidgin also over a proxy. DCC has only been tested with irssi.
IPV6 is untested but should work.
Currently, only receiving via SOCKS5BYTESREAMS is implemented. I'm not sure if
the alternative(in-band bytestreams IBB) is worth implementing since I didn't
see a client yet that can do it. Additionally, it is probably very slow and
needs support by the server as well.
|
| |
|
|
|
|
| |
from other BitlBees won't be picked up accidentally. Might also want to
randomize the per-packet IDs because they're still predictable.
|
| | |
|
| |
|
|
|
| |
(only presence so far) errors.
|
| |
|
|
|
|
| |
channel name generation code in root_commands.c and fixed one memory leak
in jabber_buddy_remove_bare().
|
| |
|
|
|
|
|
| |
fixes a bug reported by James Teh in the monster ticket #20. There's no
proper garbage collection yet in the Jabber conference code, really have
to do that soon. :-(
|
| | |
|
| |
|
|
|
|
|
| |
(without any @server part) to your contact list and you'll see all XMPP
traffic going in and out, and messages sent to the buddy will be sent as
packets to the server.
|
| |
|
|
|
|
| |
doesn't deal with it very well, and I don't really know yet how I'll
solve this... :-(
|
| |
|
|
|
| |
with anonymous rooms (ie about 95% of all available Jabber chatrooms?).
|
| |
|
|
|
| |
Just don't use this, you're really not going to like it. :-)
|
| |
|
|
|
|
| |
will come tomorrow. It compiles, I'll leave the real testing up to someone
else. ;-)
|
| | |
|
| |
|
|
|
| |
insensitivity. Probably not complete yet...
|
| | |
|
| |
|
|
|
|
| |
makes it easier to find out if an event handler has to be called for a
reply packet.
|
| | |
|
| |
|
|
|
|
|
| |
list, proper checking (and handling) of events related to buddies that
aren't "hashed" yet, limit checks on priorityto setting, renamed JEP85
to XEP85, support for more XEP85 states.
|
| |
|
|
|
|
| |
login, and now sending proper error responses to IQ packets we can't
handle.
|
| |
|
|
|
|
|
| |
budd_by_jid(), added a full_jid property to easily address that resource
without having to rebuild the full JID every time and implemented typing
notification shite.
|
| |
|
|
|
|
|
|
|
| |
means the buddy won't show up offline when one resource goes down (while
there are still others available). It also remembers away state
information for every separate resource. Later this system will be used
to keep track of client capability information (Typing notices, yay...)
and who knows what else.
|
| |
|
|
|
| |
mess in iq.c!
|
| |
|
|
|
|
|
| |
event handlers that can be set when sending a packet to handle the reply
to this specific packet. This should allow me to make the iq handler a
lot cleaner.
|
| |
|
|
|
|
|
| |
by any client I know of. Also, they're already working on a (probably
completely incompatible) standard: JEP-191. Maybe BitlBee will implement
it too some day...
|
| | |
|
| |
|
|
|
| |
connecting to Google Talk.
|
| | |
|
| |
|
|
|
| |
seem to be completely like how it works on other IM networks.)
|
| |
|
|
|
| |
to work perfectly though.
|
| |
|
|
|
|
| |
setting has to be finished, plus an ssl_starttls() function for the other
SSL libraries (this code will only compile with GnuTLS for now).
|
| | |
|
| |
|
|
|
| |
got rid of the double <presence> tag sent because of presence_announce().
|
| |
|
|
|
| |
properly working SASL authentication (although only PLAIN so far).
|
| |
|
|
|
|
|
| |
against write()ing to sockets that are closed already, hopefully sane
detection for SASL support, and only sending type=unavailable presence
tag to logged in sessions.
|
| |
|
|
|
| |
yet.
|
| |
|
|
|
|
| |
table like in the MSN module), added sending of keepalive "packets" and
removed old main() code (for testing only) from jabber.c.
|
| |
|
|
|
| |
recommended by rfc3921/5.1.5.
|
| |
|
|
|
|
| |
at the end of sessions, support for sending messages, and restored the old
(and leaking) xt_print(), which I'll only use for debugging.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
developed outside this tree)
|
