Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Easily copy passwords to clipboard in Keychain Access' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Easily copy passwords to clipboard in Keychain Access
Authored by: fredkinder on Dec 15, '08 08:23:20AM

Works under 10.4.1 also.



[ Reply to This | # ]
Easily copy passwords to clipboard in Keychain Access
Authored by: Grant Symon on Dec 15, '08 09:01:08AM

Works for Secure Notes too. Very useful.



[ Reply to This | # ]
Easily copy passwords to clipboard in Keychain Access
Authored by: arcticmac on Dec 15, '08 11:46:51AM

Works under 10.4 as you say, but with the caveat that in 10.4, regardless of where you click in the list, it copies the password of the selected item. In 10.5, it selects the item you click on, then copies that item's password. Which is much nicer!



[ Reply to This | # ]
Easily copy passwords to clipboard in Keychain Access
Authored by: jms1 on Dec 15, '08 12:49:55PM

This sounds like a bug in 10.4's keychain manager program. I remember the first time it bit me- I was using the password generator, and chose one of the "other" passwords from the drop list. It showed a line of stars or circles in the item itself, so I closed the generator, copied the new password, and then pasted it into the field for the web site I was registering for.

After that I couldn't log into the web site- turns out the password it actually used was the first one on the list, rather than the fourth or fifth (which I had chosen.) I did a bit of digging, and discovered that, under 10.4, when you close the password generator window, it copied the first item (rather than the selected item) on the drop-list back to the password field of the item you were creating or editing. I was able to see it happen by turning on the "show typing" checkbox.

I'm pretty sure I sent Apple a bug report through their "feedback" web site, although I don't know for sure... I do know it's been fixed in 10.5.



[ Reply to This | # ]