aboutsummaryrefslogtreecommitdiffstats
path: root/protocols/yahoo/libyahoo2.c
Commit message (Collapse)AuthorAgeLines
* Remove yahoo (the old protocol). Use funyahoo++ instead.dequis2016-11-19-5711/+0
| | | | | | RIP The previous commit already handled the part of telling users.
* typofix - https://github.com/vlajos/misspell_fixerVeres Lajos2015-08-07-2/+2
|
* Reindent everything to K&R style with tabsIndent2015-02-20-965/+1230
| | | | | | | 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.
* Fix compiler warnings on Cygwin and Mac OS X.Jason Copenhaver2015-01-16-7/+8
| | | | | | | | * Don't use PIE/PIC on Cygwin/Darwin unless specified as these platforms don't support it. * Cleanup warnings for 'make check' build. * Fix the type issue for getsockopt calls. * Fix enum warnings in Yahoo libs on Mac OS X.
* Fix incorrect Free Software Foundation addressMatej Cepl2015-01-16-1/+1
|
* Use glib functions for base64 decoding/encodingdequis2014-11-24-2/+17
| | | | | | | | | | | | 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.
* RIP native win32 support (use cygwin instead)dequis2014-09-27-2/+0
| | | | It has been broken for a very long time and nobody cared about it.
* Cleaning up some more Yahoo! symbols.Wilmer van der Gaast2012-10-20-6/+11
|
* Some more removals. Using ifdefs instead of read deletions in Yahoo! dir toWilmer van der Gaast2012-10-20-1/+17
| | | | | | not make merges too complicated (although upstream really seems dead at this point :-/).
* Removing some more cruft now that I've (re)discovered ld garbage collection.Wilmer van der Gaast2012-10-20-3/+0
| | | | | Mostly stuff related to obsolete Y!MSG login obfuscation schemes.
* yahoo: unused-but-set-variablesMiklos Vajna2011-12-06-42/+19
|
* Better handling of yahoo add responses: libyahoo2 seems to (IMHO) wronglyWilmer van der Gaast2010-08-22-0/+19
| | | | | | assume that a non-0 status means the contact is on the list already and on-line. This causes ugly "imcb_buddy_status() for unknown handle" msgs.
* OpenSolaris (non-gcc) fixes, patches from Dagobert Michelsen <dam@opencsw.org>Wilmer van der Gaast2010-08-07-1/+2
| | | | | with some changes.
* Some NULL pointer checks for libyahoo2 - this code's currently crashingWilmer van der Gaast2010-07-25-3/+6
| | | | | because BitlBee ignores file transfers.
* Merge complete. It still logs in...Wilmer van der Gaast2010-07-24-1485/+1512
|
* This should mostly be a no-op, merging *loads* of whitespace changes fromWilmer van der Gaast2010-07-23-700/+768
| | | | | libyahoo2 so that I can see better what really changed.
* Deal with stupid (on first sight, at least) Yahoo! server behaviour causingWilmer van der Gaast2010-03-15-1/+5
| | | | | | double free()s on testing ATM. Apparently it's perfectly legal to give buddy information with an "end buddy" marker but no "begin buddy".
* Fixed handling of contact lists where at least the first contact is not inWilmer van der Gaast2010-03-13-2/+3
| | | | | any group yet. Crashing is not the right solution.
* Yahoo! status updates (at least initial ones, I assume) can be too long toWilmer van der Gaast2010-03-12-25/+10
| | | | | | | | fit into one packet. Yahoo! servers will split them up, and not necessarily on buddy boundaries. Trying to handle this a little bit better now. (Sadly I can't test this myself, I can only see this causing troubles on testing sometimes.)
* Merging in some code from libyahoo2-trunk that deals better with (initial)Wilmer van der Gaast2010-03-12-194/+146
| | | | | status updates and cleans up some stale stuff.
* Yahoo! fixes. Turns out the protocol really is somewhat odd.Wilmer van der Gaast2010-03-06-4/+1
|
* Fixed up Yahoo! I'll have to do some more thorough testing of this codeWilmer van der Gaast2010-03-06-15/+5
| | | | | since I may have broken something.
* A few fixes for bugs that caused coredumps on testing.bitlbee.org (orWilmer van der Gaast2009-12-17-10/+29
| | | | | caught my attention in new compiler warnings).
* Valgrind pointed me at some memory leaks in the Yahoo! codek, including oneWilmer van der Gaast2009-10-17-3/+5
| | | | | that existed for a while already. Fixed.
* Turns out I *did* implement HTTPS auth for Yahoo! myself already, but IWilmer van der Gaast2009-10-13-184/+178
| | | | | | kept it as a patch somewhere in my homedir because I thought I didn't need it. I like this code more so I'll use it instead.
* Setting Yahoo! away states works again.Wilmer van der Gaast2009-10-10-23/+30
|
* More Yahoo! fixes: Adding and removing buddies works, and for the firstWilmer van der Gaast2009-10-10-36/+111
| | | | | | | | | time buddy add requests are actually handled; from what I can see this simply didn't exist in libyahoo2 yet so far. :-( I melded pieces of changes from http://geny.sf.net/ to make this stuff work.
* Cleaned up Yahoo! fix: Error handling, and also not crashing when theWilmer van der Gaast2009-10-03-77/+66
| | | | | connection disappears again before authentication finishes.
* Yahoo! can log in again. This code still needs major cleanups, use it onlyWilmer van der Gaast2009-10-03-7/+303
| | | | | if you're very desparate.
* Merge trunk.Jelmer Vernooij2008-06-28-7/+4
|\
| * This seems to fix the Yahoo! logoff code. I have no idea why this was brokenWilmer van der Gaast2008-06-14-7/+4
| | | | | | | | | | | | | | (on purpose) in libyahoo2, but this fix seems to work and at least Valgrind is still happy. And I actually see myself log off now, and the fd is actually cleaned up properly.
* | Merge trunk.Jelmer Vernooij2008-04-02-121/+547
|\|
| * Although I have no idea what the author meant with code likeWilmer van der Gaast2008-03-15-1/+1
| | | | | | | | | | | | | | `if(cp != "\005")', I'm sure he feels homesick to QuickBasic. Since BitlBee doesn't use this function anyway, it doesn't really matter if my fix works. As long as it keeps the compiler quiet.
| * Indicate that we support YMSG protocol version 12, this should hopefullyWilmer van der Gaast2008-03-15-1/+1
| | | | | | | | | | keep BitlBee working after 2008-04-02 <http://messenger.yahoo.com/eol>.
| * Replaced GPL-incompatible SHA1 hashing code (and renamed the files in caseWilmer van der Gaast2007-11-23-22/+22
| | | | | | | | | | I ever need SHA256 ;-)).
| * More API changes: buddy list management. imcb_add_buddy() is now a *real*Wilmer van der Gaast2007-04-18-6/+13
| | | | | | | | | | | | | | | | | | callback, it's only called from inside IM-modules. This makes sure a buddy only gets added to the BitlBee structures if the add was successful. This gets rid of the weirdness described in #55. Unfortunately for now this change breaks A) automatic renaming of ICQ contacts (if there are names stored in the contact list) B) add -tmp.
| * Updating the Yahoo! module. This seems to fix handling of incoming awayWilmer van der Gaast2007-04-15-65/+506
| | | | | | | | | | | | states/messages, should fix some issues with group chats, and unfortunately also adds some crap which I don't want to clean up for now.
| * Moved Base64-related functions to a separate file and added decode funtions.Wilmer van der Gaast2006-06-25-1/+3
| |
| * Added saner base64 encoding function (actually, moved the one from libyahoo2.cWilmer van der Gaast2006-06-23-26/+2
| | | | | | | | | | to core, with some changes), which I need for the XML format password garbling.
* | Remove unnecessary Windows-specific code.Jelmer Vernooij2006-05-26-2/+0
|/
* Got rid of the config.h includes in IM-code. Now that HAVE_CONFIG_H isWilmer van der Gaast2005-11-30-4/+0
| | | | | defined, they started to cause problems.
* Initial repository (0.99 release tree)0.99Wilmer van der Gaast2005-11-06-0/+4591
generated by cgit v1.2.3 (git 2.25.1) at 2025-04-27 08:02:02 +0000