Comments on: Safari Keychain Woes

By: Daniel Jalkut

Daniel Jalkut — Mon, 01 Aug 2011 11:55:54 +0000

@Britt – Yep, this post led me to report two bugs to Apple.

By: Britt

Britt — Mon, 01 Aug 2011 06:22:17 +0000

Two things…

1) You never posted what “po [$rdi password]” was supposed to be returning. (tee hee hee… I’m awful, ain’t I? ;-)

2) Have you filed a bug about the failure to warn about bad code signing?

By: Jonathan Wight

Jonathan Wight — Sun, 31 Jul 2011 05:46:29 +0000

And this is a fantastic example showing why normal users should NOT poke around with the innards of other people’s applications.

Websites that advise folks do things like “just modify that apps info.plist file, it’s easy” scare me.

By: Jim Matthews

Jim Matthews — Sat, 30 Jul 2011 18:13:15 +0000

Fantastic post — thanks for for writing it up. It would never have occurred to me to check secure.log; I’ll do that next time I see a keychain problem.

By: Daniel Jalkut

Daniel Jalkut — Sat, 30 Jul 2011 01:50:36 +0000

@Lri: would it? It doesn’t say anything about code signing. There are some other responses to the question that mention it, though.

By: Lri

Lri — Sat, 30 Jul 2011 01:47:28 +0000

The first result at Super User would’ve contained the solution: http://superuser.com/search?q=safari+keychain+lion

By: scott lewis

scott lewis — Fri, 29 Jul 2011 22:47:02 +0000

@Daniel A ‘unified’ log view would be extremely useful. Even more so if one could filter it by timestamp. Especially since the line between ‘dialog box’ and ‘log message’ is arbitrary, and will never suit every user.

By: Daniel Jalkut

Daniel Jalkut — Fri, 29 Jul 2011 22:28:18 +0000

@Scott: Agreed. However, in somes cases it’s not obvious *which* log to check. For example, secure.log is kind of obvious in retrospect, but there were no log messages in the regular “console.”

By: scott lewis

scott lewis — Fri, 29 Jul 2011 22:24:38 +0000

The moral I take from this is: When something goes wrong, check the log.

After all, even if the log doesn’t contain the answer, it often contains things that can be punched into Google.

By: Chris

Chris — Fri, 29 Jul 2011 21:19:20 +0000

Very interesting post. I never thought of using instruments to profile other apps than my own. The gdb stuff is a bit beyond me, but the more I am exposed to it’s use, the more likely I am to give it a shot whenever I find myself in a suitable situation :)