Login & Keychain Update 1.0 Released

[MacRumors]

http://www.macrumors.com/images/macrumorsthreadlogo.gif (http://www.macrumors.com)

Apple has released Login & Keychain Update 1.0 (http://www.apple.com/downloads/macosx/apple/macosx_updates/loginkeychainupdate10.html). The update, which is recommended for all users of Mac OS 10.5 Leopard, addresses a few issues according to Apple, including:

- Logging in with an account originally created in Mac OS X 10.1 or earlier that has a password of 8 or more characters.
- Connecting to some 802.11b/g wireless networks.
- Changing the password of a FileVault-protected account.

Article Link (http://www.macrumors.com/2007/10/28/login-and-keychain-update-1-0-released/)

[koobcamuk]

Update went without a hitch.

Seems to be ok and all keychains working so far...

[cloudnine]

This fixed a really annoying issue I was having where every time I reboot, I had to re-input my network name and password... thank jebus! :P

[Clix Pix]

This fixed a really annoying issue I was having where every time I reboot, I had to re-input my network name and password... thank jebus! :P

AHA!!!! I've been having this same problem in one machine ever since installing Leopard....

MANY thanks -- off to do the software update right now!

[Doctor Q]

- Logging in with an account originally created in Mac OS X 10.1 or earlier that has a password of 8 or more characters.Can a bug get more obscure than that? You can hardly blame Apple (as people did in this thread, for example) for not catching a bug like this while testing Leopard.

[daylight28]

i updated my powerbook 12" and now it will not see the airport card.
Help!!

[dizastor]

Logging in with an account originally created in Mac OS X 10.1 or earlier

Wow. Thats crazy... how is that possible?

Upgrade installations for the last six years on the 867mhz (bottom of Leopard's barrel) Powermac?

Amazing.

[longofest]

Can a bug get more obscure than that? You can hardly blame Apple (as people did in this thread, for example) for not catching a bug like this while testing Leopard.

The thread you quoted was a bug with Aperture getting messed up because of Time Machine. Seems a bit bigger, as Aperture is one of Apple's major media products.

[MacPhilosopher]

I had the same general problem with passwords as everyone else, but had an even more disheartening problem with my CPU being maxed out by user tasks. Just a solid green field in the activity monitor window with no applications running. I had a kernel crash during the restart after installing 10.5 and it seemed to have created some lasting bug in my root system. I tried a reinstall after other basic troubleshooting, but did not fix the problem. Once Apple released the keychain update, I ran it and after the install there was a dialogue box that messaged that the system root folders were being checked/fixed. Once I restarted, the CPU/User problem was gone.

[benlee]

Just a head up.
I installed the update even though I wasn't having any issues. Upon restart my computer started installing the update and then froze, I had to do a hard restart but everything seems fine now. I think a couple other people had this problem too.

I would suggest to maybe hit restart later and wait a little bit before restarting.

[Stuipdboy1000]

Just a head up.
I installed the update even though I wasn't having any issues. Upon restart my computer started installing the update and then froze, I had to do a hard restart but everything seems fine now. I think a couple other people had this problem too.

I would suggest to maybe hit restart later and wait a little bit before restarting.

That happened to me too. First time it froze so I switched it off. Tried again and it froze. Third time lucky though.

[youngestchild]

i'm not sure if this is related to the keychain update (i have installed it) but i'm having problems with my keychain... things like mail passwords don't save to the kc even though i've asked for them too. and I had an error signing on to .mac... i get this error

Keychain Error
There was a problem saving to your keychain. please try again or use keychain access to verify your keychain. Error: -25299.


this message pops at twice, one after the other.... anyone know what's going on.. when i look at the key chain i have two 'system' keychains that appear to be identical? is that the problem? :(

thanks.

[iHerzeleid]

after installing the update i got the click of death :[


now i have to buy a external hd to back up the part of my macbook that isnt damaged and send it to apple for replacement :[

[juniormaj]

i updated my powerbook 12" and now it will not see the airport card.
Help!!

Same here, but with a 15" PowerBook (1.67 Hi Res).
:(

edit: Found this in Apple Support Discussions..... ( http://discussions.apple.com/thread.jspa?threadID=1201382&tstart=0 )
"Some users have determined that an upgrade artifact left over from Mac OS X 10.4.x interferes with wireless connections after Mac OS X 10.5 is installed. It manifests itself as an inability for OS X 10.5 to recognize the AirPort card. The resolve is to find and remove the AppleAirPort2.kext file from your Extensions folder, that's located here: Macintosh HD:System:Library:Extensions"

This worked for me.
:)

[aardwolf]

:mad: When I first installed Leopard, Finder stopped responding for hours and hours after my first reboot (even after Spotlight finished indexing.) Eventually I got it working. Installing this patch brought the same problem back... :mad:

[Clix Pix]

Same here, but with a 15" PowerBook (1.67 Hi Res).
:(

edit: Found this in Apple Support Discussions..... ( http://discussions.apple.com/thread.jspa?threadID=1201382&tstart=0 )
"Some users have determined that an upgrade artifact left over from Mac OS X 10.4.x interferes with wireless connections after Mac OS X 10.5 is installed. It manifests itself as an inability for OS X 10.5 to recognize the AirPort card. The resolve is to find and remove the AppleAirPort2.kext file from your Extensions folder, that's located here: Macintosh HD:System:Library:Extensions"

This worked for me.
:)


Because I was still having problems with having to type in my network password each time I rebooted, even though my system was able to find the Airport card, I tried this on one of my machines. Rebooted....same problem stlll occurs. I think Apple needs to do a bit more tinkering with Airport!

[Lancetx]

Here's a fix for those that lost their AirPort card after applying this update.

http://docs.info.apple.com/article.html?artnum=306879

[ATMB]

I get the airport always switched op on restart/switching on of Mac with leopard... I think I'll post a new thread regarding it...

[Loge]

That happened to me too. First time it froze so I switched it off. Tried again and it froze. Third time lucky though.

This happened to me as well. But now my Mac will only restart if I switch it off and leave it for a moment. If I just try and restart it sticks on the grey screen. :mad:

[0s and 1s]

A little help, please!


I've tried to install it through Software Update, and when you click the Install Item button, it tells me that I could not install it because I do not have sufficient privileges. I'm the Admin of the computer.


Where did I go wrong? :confused:

[Loge]

OK, problem solved. :) Removed APE 2.0.3, although this did not affect my original Leopard upgrade.

[twoodcc]

i keep forgetting to do this update. i need to do this when i get home.

[MoSha]

i'm not sure if this is related to the keychain update (i have installed it) but i'm having problems with my keychain... things like mail passwords don't save to the kc even though i've asked for them too. and I had an error signing on to .mac... i get this error

Keychain Error
There was a problem saving to your keychain. please try again or use keychain access to verify your keychain. Error: -25299.


this message pops at twice, one after the other.... anyone know what's going on.. when i look at the key chain i have two 'system' keychains that appear to be identical? is that the problem? :(

thanks.



I had a similar problem and found this on the apple support site and worked well for me. Keychain now back to as it should be.
http://docs.info.apple.com/article.html?artnum=306862
Hope this helps.

[vigsanghjai]

The thread you quoted was a bug with Aperture getting messed up because of Time Machine. Seems a bit bigger, as Aperture is one of Apple's major media products.