| Commit message (Collapse) | Author | Age | Lines |
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|\ |
|
| |
| |
| |
| |
| | |
misc@mandriva.org, bug #381.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
ft_listen = <IP-A>:<Port-A>;<IP-B>:<Port-B> to specify listening addresses for
the bitlbee<->client connection and the bitlbee<->IM peer connection,
respectively.
ft_max_size should be obvious. ft_max_kbps should limit the kilobits per second
per transfer (not implemented yet).
|
|\| |
|
| |
| |
| |
| |
| | |
specific interface before connecting to a remote host.
|
|\|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |
| |
| |
| |
| | |
modifications. Also adding some missing g_free()s to conf.c.
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
*INSECURE* because users can just do /mode +o to become operator.
|
| |
|
|
|
|
|
|
| |
Fix two bugs in the text storage backend that were introduced by my previous
changes.
|
| |
|
|
|