Well, I've come up with a way to help solve this problem. I wanted to use trillian again (wingaim seemed unstable on my system. WinME, bleh). I was looking over the plans of my password generator and realized that if I built something that would simply change my password in that file automatically, I could use the autologin and be able to log in with a new password each time. Of course, you'd have to have a way to let the login servers know you were changing your password somehow too. I guess this would really only help programmers though seeing as there's no available software like that.

You can also run it in lock-down mode where you have a lead-in program that decrypts all the files, then loads trillian and after trillian closes, encrypts them all again. You don't need particularly strong encryption, just enough to keep someone from sending some automated bot.

It seems that trillian uses the functions held in crypto.dll perhaps some analysis of this would allow you to create a more secure version with the same function names. If I had the skill to attempt this, I surely would. But, the idea's out there for those who like trillian but want to be a bit safer with logon info.