I've not had any trouble with Safari 5.1 crashing on .mil sites since adding an identity preference for *.mil. I tested between updating to 10.6.8 and updating Safari to 5.1 and only had the problem once I updated to Safari 5.1.
On Jul 26, 2011, at 11:21 AM, John Casebolt wrote:
> Carl -
> Thanks to an off-list suggestion, a little more info if it helps Carl or anyone else debug:
> 1) No identity preference: immediate Safari crash before rendering anything on the page
> 2) Identity preference (https://software.forge.mil/) on the fourth cert in my CAC chain (the PIV one, I think?): Safari says it cannot establish secure connection, but does not crash.
> 3) Identity preference on the first cert in my CAC chain: Safaris crashes after it renders almost the entire page
> Still no joy - trying to decide whether to plow forward to Lion or back to 10.6.8 minus the latest Safari..
> John Casebolt
> On Jul 26, 2011, at 10:06 AM, John Casebolt wrote:
>> Carl -
>> Thanks for the response.
>> I tried:
>> - a different CAC reader
>> - the latest WebKit nightly (see below for stack trace)
>> No difference.
>> I did notice in the stack trace that the Code Type is X86-64 (Native). My desktop machine is an older (2007) iMac incapable of running the 64 bit kernel, so I can't change over to that and try again while running the 64 bit kernel. My laptop is capable of running the 64 bit kernel, but it is still working (running 10.6.8 and older Safari). I'm loathe to mess with that until I get the iMac working again.
>> P.S. - I just got a popup from Software Update RE: a new 10.6.8 fix. I guess I'll give that a try.
>> John Casebolt
>> Process: Safari 
>> Path: /Applications/Safari.app/Contents/MacOS/Safari
>> Identifier: org.webkit.nightly.WebKit
>> Version: r91677 (91677)
>> Code Type: X86-64 (Native)
>> Parent Process: launchd 
>> Date/Time: 2011-07-26 10:00:43.655 -0400
>> OS Version: Mac OS X 10.6.8 (10K540)
>> Report Version: 6
>> Interval Since Last Report: 83360 sec
>> Crashes Since Last Report: 23
>> Per-App Interval Since Last Report: 77 sec
>> Per-App Crashes Since Last Report: 2
>> Anonymous UUID: D1C18DF5-7087-45A6-9506-597895EBF697
>> Exception Type: EXC_BAD_ACCESS (SIGSEGV)
>> Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000019
>> Crashed Thread: 0 Dispatch queue: com.apple.main-thread
>> Thread 0 Crashed: Dispatch queue: com.apple.main-thread
>> 0 libstdc++.6.dylib 0x00007fff8a5df798 __dynamic_cast + 36
>> 1 com.apple.security 0x00007fff8546618d Security::KeychainCore::Identity::required(OpaqueSecIdentityRef*) + 43
>> 2 com.apple.security 0x00007fff8546607e SecIdentityCopyCertificate + 54
>> 3 com.apple.Safari.framework 0x00007fff83c1d9b0 SecIdentityCopySSLClientAuthenticationChain + 70
>> 4 com.apple.Safari.framework 0x00007fff83a60553 Safari::useIdentityForChallenge(OpaqueSecIdentityRef*,
>> On Jul 25, 2011, at 7:07 PM, Carl Ketterling wrote:
>>> I've read of many customers reporting problems after upgrading to Safari
>>> v5.1. Two workarounds that I've read were 1) going back to Safari
>>> v5.0.1 (by reinstalling the Mac OS X v10.6.8 update) or 2) testing the
>>> WebKit Nightly Build (nightly.webkit.org).
>>> Obviously, it would help if someone could test the same sites with our
>>> software on a fresh install of Mac OS X without the
>>> I've been unable to duplicate the problems you've experienced using a
>>> clean installation of Mac OS X v10.6.8 which had PKard installed.
>>> Carl Ketterling
>>> Thursby Software Systems, Inc.
>>> email@hidden | (817) 478-5070
>>> In response to this text from John Casebolt
>>> (email@hidden) sent on Monday, July 25, 2011 at 5:41
>>> PM (-0400):
>>>> I've been cruising along for over a year now using my CAC with
>>>> software.forge.mil every day - no problems.
>>>> Today, I updated to 10.6.8 and to Safari 5.1.
>>>> Every time I access https://software.forge.mi, Safari crashes on me.
>>>> Sometimes immediately, sometimes after rendering almost an entire page.
>>>> I did notice that my DoD issuing intermediate (DoD 25) was not in my
>>>> keychain - it never was, but that did not seem to matter before these
>>>> I installed that cert, and my CAC certs all appear with green check
>>>> marks again.
>>>> Same crashing behavior.
>>>> I have tried, to no avail, all of the following:
>>>> - deleting/re-creating identity prefs
>>>> - reinstalling Safari 5.1
>>>> - repairing disk permissions
>>>> - repairing the startup disk
>>>> - reinstalling tokend NG
>>>> - purchasing, installing and using Thursby Pkcard
>>>> I've sent crash reports to Apple and entered a topic on the Thursby
>>>> support forum.
>>>> Anyone else seeing anything like this?
>>>> Tomorrow I'll try a different CAC reader.
>>>> John Casebolt
Do not post admin requests to the list. They will be ignored.
Fed-talk mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden