OSX Keychains and adium problem

[noahwallach]

Hi there,

I am wondering if there is something corrupted in my keychains? I am running adium and after entering my passwords and clicking the "save to keychains" option. I still keep getting asked for my password.

What could be wrong here?

Cheers,

Noah

[Robby]

From http://trac.adiumx.com/wiki/TroubleshootingTips:

7) Run keychain repair

If Adium prompts you for your password every time you connect, and checking the “remember my password” box does not work, open the Keychain Access application and run Keychain First Aid or Repair from the Keychain Access menu. If that does not solve the problem, you can also try deleting each Adium entry that you see in the Keychain Access application.

If you run an application “slimmer” that removes code from your applications that does not match your computer's CPU architecture, it can cause the same symptoms as described here. Re-downloading and installing a fresh, un-slimmed Adium should solve that problem.

See if that helps!

[The_Tick]

I had this problem, it ended up being that my adium app support folder was read only

[rickross]

I had no keychain problems with any of the Adium 1.3 betas, but after installing the release version today I am having no end of aggravation. I have run keychain repair, wiped out previous preferences, installed a fresh copy of Adium 1.3 and even set all my pref but no joy.

I get prompted several times to allow keychain changes, then I get prompted for my account passwords. I do ultimately get connected to each service, but if I quit Adium and restart, then the whole routine begins again as if nothing is remembered. Additionally, I see no new Adium entries in my keychain.

Anyone have any ideas?

Thanks,
Rick

[Qoroite]

Possibly a similar or related problem here too(again only started once I moved from the 1.3 beta's to the final version & then up to 1.3b1):

I hold my adium folder on a shared drive & link to it by adding the following lines(slightly censored, naturally) to the bottom of the Info.plist file

<key>Preference Folder Location</key>
<string>/Volumes/**************/Users/**************/Library/Application Support/Adium 2.0/</string>

Worked fine right up til I moved from 1.3b9 to 1.3; stored the passwords on the local keychain. With 1.3 and the above lines in the info.plist, it doesnt appear to be looking at my local keychain at all doesn't add or edit any items.

If I remove those lines it works fine adds entries to the local keychain and looks to it for passwords; readd the lines & it asks for passwords each time.

Again, I've attempted to repair the keychain, added entries manually, wiped prefs and most other fun options; with no joy. Is there anywhere we can download 1.2.7 or one of the beta's of 1.3? - no matter found it; went back down to 1.2.7 and it works again

[zac]

I don't recall any keychain code changing between the 1.3 betas and final. Are you modifying the Adium.app Info.plist? This will cause the codesigning to fail; did you say NO to the dialogs asking you to confirm the application changes? 1.2.7 is signed as well, so it should show the same problem, however.

[dndparks]

I am seeing the same thing. I never see anything put into keychain. New preferences did not work. All started when I did the last update. Running 1.2.7 on another machine and no issues there. I am going to move it back to this machine and test again.

[dndparks]

When I drop back to 1.2.7 i see the keychain entries happen now. However it still prompts for the password. Clicking save has no effect, and neither does entering the passowrd information in the account preferences.

[pencrush]

Is there any word on this? I have the same problem, and have to log in each time I use adium...

[ShelbyDodgeImp]

I have this problem with 1.3.1b1, but only with yahoo messenger accounts.

Every couple hours all my yahoo accounts will disconnect (no idea why) and when adium tries to automatically reconnect them, I get the dialog asking for my password, to which I check the "add to keychain" option- and it DOES appear to remember the password because everytime I get this password nag screen it WILL already have my password in it!

These disconnections do not occur on my ICQ, AIM, or MSN accounts- nor do I have trouble with password dialog boxes popping up when they try to connect.

I cannot say if 1.3.1 fixes this for me because I cannot get 1.3.1 to work w/out instantly crashing (see other thread, separate issue from this one).

[Robby]

ShelbyDodgeImp, I do not think your issue is related.
It rather looks like the Yahoo servers are having problems.

[ThrashNeon]

I have this problem with 1.3.1b1, but only with yahoo messenger accounts.

Every couple hours all my yahoo accounts will disconnect (no idea why) and when adium tries to automatically reconnect them, I get the dialog asking for my password, to which I check the "add to keychain" option- and it DOES appear to remember the password because everytime I get this password nag screen it WILL already have my password in it!

These disconnections do not occur on my ICQ, AIM, or MSN accounts- nor do I have trouble with password dialog boxes popping up when they try to connect.

I cannot say if 1.3.1 fixes this for me because I cannot get 1.3.1 to work w/out instantly crashing (see other thread, separate issue from this one).

Same issue for me in 1.3.1. I noticed it AFTER upgrading from the beta to 1.3.1.
YIM accounts only-- random disconnects and re-prompts for passwords.

ShelbyDodgeImp, I do not think your issue is related.
It rather looks like the Yahoo servers are having problems.

If YIM servers are to blame, then EVERYONE should be having this issue, right?

I *do* see the passwords in the Keychain.. but every time the prompt shows up, the checkbox to save password is unchecked.

Note: I'm running Leopard (10.5.4) and had a beta installed.
On a Tiger machine that never had a beta installed, 1.3.1 is working fine- no random disconnect issues.

[zac]

It would be an issue for everybody if the Yahoo servers are sending whatever we think is an invalid password line, to everybody. This might not be the case. We need a debug log to determine what Yahoo is telling us.

http://trac.adiumx.com/wiki/ReportingBugs

[kevincop]

ThrashNeon's description of the problem matches mine 100%. I do have something to add: Adium 1.3.1 seems to disconnect from all services rather than just Yahoo (I use GTalk, AIM, MSN, Y!) but the password is only being asked for the Y! account. Also, the disconnection seems to occur more frequently when the computer sits idle and starts the screen saver, turns off the screens and so on.

I don't know if this is connected in any way, but the settings are to set my status to Away once the scrren saver kicks in.

[Jake513]

Same problem with me since upgrading to the latest build. Sometimes it does happen with Yahoo, AOL and Gchat but usually just Yahoo.

[EricaJoy]

It would be an issue for everybody if the Yahoo servers are sending whatever we think is an invalid password line, to everybody. This might not be the case. We need a debug log to determine what Yahoo is telling us.

http://trac.adiumx.com/wiki/ReportingBugs

Code: Select all

16:17:48: (Libpurple: yahoo) 19 bytes to read, rxlen is 128
16:17:48: (Libpurple: yahoo) Yahoo Service: 0x54 Status: -1
16:17:48: (Libpurple: yahoo) Key: 1  	Value: ericajoy
16:17:48: Connection Disconnected: gc=182e5df0 (Unknown error number 0. Logging into the Yahoo! website may fix this.)
16:17:48: -[AIAccount(Abstract) serverReportedInvalidPassword]: <ESPurpleYahooAccount:15d27530 1>:ericajoy
16:17:48: <ESPurpleYahooAccount:15d27530 1>:ericajoy accountConnectionReportDisconnect: Unknown error number 0. Logging into the Yahoo! website may fix this.
16:17:48: (Libpurple: yahoo) 69 bytes to read, rxlen is 89
16:17:48: (Libpurple: yahoo) Yahoo Service: 0x7d1 Status: -1
16:17:48: (Libpurple: yahoo) Key: 66  	Value: 1014
16:17:48: (Libpurple: yahoo) Key: 16  	Value: 42352,ericajoy,ericajoy,*.*.*.*,84,-1
16:17:48: (Libpurple: yahoo) Unhandled service 0x7d1
16:17:48: <ESPurpleYahooAccount:15d27530 1>:ericajoy: Telling the core we disconnected

Let me know if there is a bug in trac I can put this in.

[surr]

I was having the exact same problem, but only with my MSN account. I tried deleting all keychain entries starting with "Adium.", but it kept asking me for my MSN password. Then I found that the passwords were no longer saved in the entries starting with "Adium.", but in keychain entries in the following form: "<service>.<account_name>...".
So when I deleted the keychain entry named "MSN.<my_msn_account>...", Adium asked me one last time for my password, and now it finally remembers it.

Hope this helps.

[Caledai]

I have been experiencing this issue as well when attempting to get the Adium running on a Portable Disk.
The Portable Disk I am currently using is an Encrypted Sparse Disk Image.
Before anything is mentioned - my keychain has no problems.
My OS is 10.5.5 - Fully updated apart from the latest Java.
I previously had Adium working Portably using older versions.

As Suggested on Trac. - http://trac.adiumx.com/wiki/PortableAdium, yet it mentions nothing about code signing (which I picked up above)

• I can copy the App from Applications to /Volumes/xAdium (The Portable Drive) (Keychain works Ok)
• I can run the App without changes and it remembers all the Keychain Info
  (Still using ~/Library/Application Data.... rather then /Volumes/xAdium/Profile (Keychain works Ok)
• I explicitly add /Volumes/xAdium/Adium to the keychain (Keychain works Ok)
• I edit the info.plist - breaking Code Signing and it loads with the Copied Profile (Keychain Fails)
• I open the edited Adium App - After editing the entry in KeyChain to allow all applications (Keychain Works)

Thus - its an issue to do with Signing Only - but with the Code Signing Failed (As a result of the info.plist change) I can't add the changed Adium to the Keychain.
Yet allowing global access to the Keychain allows the version which has failed the code sign to access the keychain.
Perhaps the ability to self sign an app might help here, enough to let the keychain trust the app.
I might have a look at the developer tools and see if I can sign that app as a self signed one - but not sure if I would be able to do this.

Now using a launcher here - http://www.freesmug.org/portableapps/adium/
Portable Adium 1.3rc4.0.

• I removed the version of adium within this, replacing it with the current signed version from /Applications
• I Explicitly allowed access to Portable Adium to have access to the keychain entry.
• I allowed Portable Adium to copy the prefs from the Local Location
• I activated the account I was using for a test - straight away it prompted for the password - so the keychain has failed.
• I allowed all applications to access the keychain entry for that account - it logged in successfully.

Thus - even using a launcher - something is being modified that prevents it from using the keychain - but it doesn't appear to be editing the info.plist within Adium.app itself.

Third Option - Shell Script
Personally this is a fairly ugly hack to get a portable app just to access the keychain, as it requires terminal to be open.
I use this all the time, and opening/closing the terminal accidently would crash adium.

Looking in the console I get this message - pretty much confirming that its the code signing.

Code: Select all

7/11/08 7:20:09 PM Adium[13121] could not retrieve password for account ******@hotmail.com: SecKeychainFindInternetPassword returned -67061 (code or signature modified) 

So what can be done - it pretty much rules out using Adium in any form of portable version - as I am not prepared to type in 7 account different passwords each time I want to use the portable version, or 4 if I want to use an Open Fire gateway - and not have functions such as file transfers.

Its a known fact that this issue was not present in older versions of the application, so why now?
And in future - perhaps the option for a value to be stored in the Adium.app to redirect the profile folder that is outside of any signing requirements.

Neither is allowing every application access to the keychain entries for all my IM accounts.

At the moment I am going to look at the developer tools so see if there is any way to sign an edited app.

[Caledai]

Update.

I have managed to get this working on my machine to my satisfaction.

However, given this means I am overriding the signature of the developer
I don't plan to release any details on this unless on of the dev's here supports it, in which case I will put together a rough guide that works with the instructions for changing the info.plist.