| Commit message (Collapse) | Author | Age | Lines |
|---|
| |
|
|
|
|
|
| |
Third time's the charm.
Previous attempt fixed something and broke something else. Whatever.
Definitely valgrind clean this time.
|
| |
|
|
|
|
|
| |
Yeah ok that was dumb.
This is essentially just using a 'data' variable instead of 'l->data',
but i went ahead and cleaned up the function.
|
| |
|
|
|
|
|
| |
These were passing a pointer to a variable right after it was g_free()'d
They are most likely harmless as g_slist_remove() probably just needs
the pointer location, but fixing it anyway.
|
| |
|
|
|
|
|
| |
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)
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This fixes several coverity warnings about 'tainted data index sink' and
a fixme about thread safety in the old base64_decode implementation.
Had to adapt the code that used base64_encode_real:
- oauth.c: different character set order, but it's for the nonce so it
doesn't matter
- libyahoo2.c: used as part of the auth, changes "+/=" into "._-".
Fixed by encoding first the usual way through glib, then replacing.
|
| |
|
|
|
|
| |
Replaced them with GPL headers where possible. OSCAR and Twitter modules
can't be relicenced though, so add an LGPL blurb to debian/copyright.
|
| |
|
|
|
|
| |
let me close #641, and more importantly, prepares the Twitter module for
an upcoming API change. https://dev.twitter.com/blog/deprecating-http-1.0-streaming-api
|
| |
|
|
|
| |
setup for identi.ca. Turning on oauth for identi.ca accounts by default now.
|
| | |
|
| |
|
|
|
| |
support any of them.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
which http_client really can't deal with.
|
| |
|
|
|
|
|
| |
completely for whatever the reason may be (invalid signature). I give up for
now. Stuff does actually work if you generate access tokens using different
software so BitlBee's definitely able to generate good signatures.
|
| |
|
|
|
|
| |
don't match. This is not a real problem but can be confusing if you don't
expect it.
|
| |
|
|
|
| |
with some changes.
|
| |\
| |
| |
| |
| | |
Somewhat intrusive, should've done this right immediately. :-/
|
| | | |
|
| |/
|
|
|
|
| |
Keep it in the Twitter module, and use the oauth_info struct through the
whole session to keep all this together.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
the vars don't need escaping. But this shouldn't be so fragile anymore.
|
| |
|
|
|
| |
:-(
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Twitter's tricky. It returns vars (user_id, screen_name) in the access token
that, the way I read the spec, should be included in all subsequent queries.
However, stuff only started to work when I dropped those vars.
This code's definitely not pretty ATM. Need to clean up now that it actually
works.
|
| | |
|
| |
|
|
|
| |
http://twitter.com/oauth_clients/details/127170 . \o/
|
| | |
|
|
|
around all of this the rest is going to be easier..
|
