[Wocky] Jabber on Mac OS X 10.4

[Albert Willis]

On Oct 17, 2005, at 1:30 PM, Jonathan Reed wrote:

> At 1:34 PM -0400 10/11/05, Greg Hudson wrote:
>
>> I no longer believe this behavior originates from the server.
>> Certainly, the text "not secure" does not appear in the source  
>> code we
>> are running.
>>
>> Al, you can go ahead and file a bug with Apple.  As I mentioned
>> before, we are running jabberd 2.0s4 at the moment.  The only  
>> relevant
>> configuration I know of is that the server requires SSL for logins.
>>
>
> Ooops, I screwed up.  I thought this was on the server, because  
> when I looked in the resource bundle for iChat, and even the binary  
> itself, I didn't find that.  I didn't think to check for a  
> framework, and sure enough, the text appears in iChatAgent in  
> InstantMessage.Framework.
>
> There's also a bunch of stuff about certificates in there, so I  
> wonder if it's merely failing to verify the certificate chain.   
> Does jabber.mit.edu have a real cert signed by the MIT CA, or is it  
> a self-signed cert?  Regardless, even if the cause is failed CA  
> verification, it's still a bug, since the error message should be  
> more verbose.
>
> I have the MIT CA in my keychain, so it should work, unless for  
> some reason iChatAgent doesn't use the Keychain.
>
> -Jon

The response I received from Apple is that it's a known issue that is  
being investigated by engineering.

I also thought about the certificate possibility as well; so far,  
having the MIT CA in the X509Anchors keychain and having my personal  
certificate in the login keychain hasn't made a difference.

   -- Al