| 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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This changes behavior slightly:
- md5_init()/sha1_init() allocate a GChecksum
- md5_finish()/sha1_finish() close and free() it
- md5_digest_keep() was added (no sha1 equivalent needed)
And yes, glib has this concept of "closing" the GChecksum, which means
it can't be used anymore after g_checksum_get_digest().
jabber_cache_add() actually seems to need to do that to generate some
random-ish values, so i kept that working by adding a md5_digest_keep()
function that copies the GChecksum before it gets closed
GChecksum was introduced in glib 2.16, so the configure script version
was bumped. We were already depending on glib 2.16 accidentally
(some post-3.2.2 code uses GHashTableIter)
|
| | |
|
| |
|
|
|
|
| |
really support desktop app OAuth in a way that would work with BitlBee.
Plus, it's only OAuth-compliant by, err, name?
|
| |
|
|
|
| |
have a function for it..
|
| |
|
|
|
|
|
|
| |
on big-endian machines. (If someone thinks BitlBee should work on PDPs,
send me the fix. I don't care. :-P) This fixes bug #351 (MSN challenge-
response failure) but might break backward compatibility if the broken MD5
code was used to save settings. (Somewhere between rev 266 and now.)
|
| |
|
|
|
| |
for pid_t variables).
|
| | |
|
|
|
protocols/, and adding RC4 code.
|
