GAIM Problem - Rate limiting error

[deadly7]

Duh, that's why I linked to my thing. It sounds plausible, at least, since EVERYONE is away 24/7.

[RoMi]

I'm getting this quite a bit now also.

[Newby]

I got it when I logged on overnight! Stupid disconnect.

[Furious]

Since you're on XP, screw GAIM, use Trillian, I personally think it's better :/

[RoMi]

Trillian's a hog, no thanks.

[Quik]

Since you're on XP, screw GAIM, use Trillian, I personally think it's better :/

Not only is Trillian Pro (Basic isn't even worth mentioning, much less using) eats up resources, and this clan is mainly made up of gamers, that should be your clue right there. But, I'll continue.

Now, this is a biased opinion, but you'll get over it. I've used Trillian Pro for a few years, and Gaim for a few months, at least on WindowsXP. So don't go thinking I'm ignorant on each of these subjects.

Price

- Trillian Pro costs a tidy sum to use, forcing the majority of users to pirate it. This is quite unethical to most, and a large downside when there are free alternatives THAT DO ALL OF THE SAME FEATURES, SOMETIMES BETTER.

- Not only is Gaim free, but it's open source. This is a huge advantage, especially in the next few sections.

Bugs and Patches

- Cerulean Studios is horrible at patches. They only patch when something big breaks, like one of their plugins for the different services, and they get bitched at enough to be motivated to fix it. Often times, large gaping holes are left open, as exemplified in the next section.

- Gaim is always up-to-date, especially because it's open source. There is a consistant amount of patches being submitted to the beta versions by different programmers, and since the code is available it's easier to find and correct bugs before they are even a problem.

Security

- I remember iago mentioning something about Skywing and Yoni's debate over Trillian Pro's security. I believe it ended in Skywing using a year-old exploit in Trillian Pro to run arbitrary code on Yoni's machine. That exploit is still unpatched.

- Again, open source allows security issues to be fixed before they are discovered and exploited.

I think you get the point. I'm kinda lazy, but I could continue.

[iago]

I believe you mean:

   Trillians Identd is susceptible to a buffer overflow
Release Date: 2002-09-17
Secunia Advisory ID: SA7115
Solution Status: Unpatched
Impact: System access
Where: From remote
Short Description:
When using Trillian to connect to IRC it is necessary to have indent running, Trillians ident suffers a buffer overflow. [Read More]

That's for Trillian1.  Although it doesn't affect most people, it's evidence on how they don't patch.  3+years later..


This one is for Trillian3:

   Trillian Exposure of User Credentials
Release Date: 2005-08-01
Secunia Advisory ID: SA16289
Solution Status: Unpatched
Impact: Exposure of sensitive information
Where: Local system
Short Description:
Suramya Tomar has discovered a security issue in Trillian, which can be exploited by malicious, local users to gain knowledge of sensitive information, including passwords. [Read More]

The reason for that one is that Trillian stores account information in public folders, in plaintext.  Gaim stores account information in plaintext; however, it stores it in private folders. 

Here's some more:

CVE reference:   CAN-2005-0874
CAN-2005-0875

Description:
LogicLibrary has reported some vulnerabilities in Trillian, allowing malicious people to compromise a users system.

The vulnerabilities are caused due to boundary errors in the handling of HTTP/1.1 response headers. This can be exploited to cause a heap-based buffer overflow and execute arbitrary code by sending a maliciously crafted HTTP/1.1 response.

Successful exploitation requires that the attacker controls a server, which Trillian connects to, or is able to conduct a Man-in-the-Middle attack.

The vulnerabilities have been reported in the AIM, Yahoo, MSN, RSS and possibly other plug-ins in Trillian 2.0. It has also been reported in the Yahoo IM and possibly other plug-ins in Trillian version 3.0 and 3.1.

Note: of all Trillian vulnerabilities in all versions, only one has ever been patched