| Commit message (Collapse) | Author | Age | Lines |
|
|
|
|
|
|
|
|
|
| |
CID 18634: 'Logically dead code' in jabber_get_info
CID 18638: 'Dereference after null check' in oauth2_access_token_done
CID 18691: 'Copy into fixed size buffer' in bee_irc_user_new
CID 20274: Leak in bee_irc_chat_invite
CID 20297, CID 20283: Leaks in crypt_main
Some the base64 leaks there weren't detected, needs modeling.
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
Also abort() if there's no /dev/urandom
See http://www.2uo.de/myths-about-urandom/ for details.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
- SIGSEGV: broadcast a message manually, avoiding the usual irc_write()
functions which are unsafe due to malloc().
- SIGTERM, SIGINT: Write to a pipe which gets handled in the main loop by
bitlbee_shutdown(), saving configs and stuff.
- SIGCHLD: set to ignore explicitly, which handles zombies correctly.
This also drops some log messages with 'info' level, which in practice
means they never got logged.
- SIGPIPE: set to ignore (nobody cares)
- SIGILL, SIGBUS, SIGFPE, SIGQUIT, SIGXCPU: Not handling anymore.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This might look like a simple diff, but those 'lies' made this not very
straightforward.
The NSS bug itself is simple: NSS detects a fork happened after the
initialization, and refuses to work because shared CSPRNG state is bad.
The bug has been around for long time. I've been aware of it for 5
months, which says something about this mess. Trac link:
http://bugs.bitlbee.org/bitlbee/ticket/785
This wasn't a big deal because the main users of NSS (redhat) already
applied a different patch in their packages that workarounded the issue
somewhat accidentally. And this is the ticket for the 'lies' in unix.c:
http://bugs.bitlbee.org/bitlbee/ticket/1159
Basically a conflict with libotr that doesn't happen anymore. Read that
ticket for details on why ignoring those comments is acceptable.
Anyway: yay!
|
|
|
|
|
|
|
| |
my copyright mentions since some were getting pretty stale. Left files not
touched since before 2012 alone so that this change doesn't touch almost
EVERY source file.
|
|
|
|
|
| |
ways it's not BitlBee and I'm tired of getting libpurple-related bug reports.
|
| |
|
|
|
|
|
|
| |
using libpurple). This was leaking memory and indirectly caused the bug
fixed by the previous revision.
|
|
|
|
|
|
|
| |
libotr installed". Also, it appears that this code needs libotr 3.2.0 or
higher, but I'm not adding a build-dep since that'll cause troubles on the
build bot, people can just build with BITLBEE_OTR=0.
|
|\
| |
| |
| |
| |
| | |
Not 100% sure about the OpenSSL merge, should double check that but I'm
currently offline.
|
| |
| |
| |
| |
| | |
with a horrible practice of reading the MOTD file one by one.
|
| |
| |
| |
| |
| | |
away with doing this without libtool (eep).
|
|\ \
| |/
|/|
| |
| | |
and parts I want to/have to redo (because of ui-fix).
|
| |\ |
|
| |\ \ |
|
| | | | |
|
| |\ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | | |
the global state of libgcrypt
|
| |\ \ \ \ |
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
with some changes.
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
still only for offline users).
|
|\ \ \ \ \ \
| | |_|_|_|/
| |/| | | | |
|
| | |_|_|/
| |/| | |
| | | | |
| | | | |
| | | | | |
and annoying.
|
|\| | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
argument checking to avoid ugly (even though harmless) segfaults. Also skip
any md5: prefix that may be present when checking hashes.
|
| | |_|/
| |/| |
| | | |
| | | |
| | | |
| | | | |
with a few command-line options to the BitlBee binary. Type "bitlbee -x"
for more info.
|
|/ / /
| | |
| | |
| | |
| | |
| | | |
nogaim_init() should be done after fork() to make ForkDaemon mode work
again. Also, doing help_init() earlie makes "help purple" work.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
version of BitlBee from Linux. No working SSL support yet though!
|
| | | | |
|
| |\ \ \ |
|
| | | |/
| | |/| |
|
| |\| | |
|
| |\ \ \ |
|
| |\ \ \ \ |
|
| |\ \ \ \ \ |
|
| |\ \ \ \ \ \ |
|
| | | | | | | | |
|
| |_|_|_|_|/ /
|/| | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
restarting the ForkDaemon. Preparing for a proper fallback when execv()
fails. (Bug #425)
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
file couldn't be found while the user specified an alternative location with
the -c option, and double complaints about /var/lib/bitlbee/ permissions.
|
| |_|_|_|_|/
|/| | | | |
| | | | | |
| | | | | |
| | | | | | |
wasn't even aware of. This closes bug #352.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
for pid_t variables).
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
modifications. Also adding some missing g_free()s to conf.c.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
global.conf->plugindir is actually filled in before we call nogaim_init().
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
encryption for the IM account passwords, plus some calls to srand() to keep
the salts secure and unique.
|
| |_|_|_|/
|/| | | | |
|