Accessing obsolete X509Anchors

[sschwar4]

Version: 2008
Operating System: Mac OS X 10.6 (Snow Leopard)
Processor: Intel
Email Client: Exchange

Last month, Corentin, posted this reply to a user asking about X509Anchors.

"Yeah, no bid deal.
That was already in Leopard. It's warning Entourage that from Leopard
on, certificates for servers are supposed to be in the Login keychain
and not in the X509Anchors where it used to be.

There is a similar post on the exact same topic from last week...

Corentin"

Well Corentin, this is a big deal when it is reported to the console every 10 minutes that Entourage is open. It writes 1-8 lines every 10-20 minutes! So far today, there are 58 lines listed in 5 hours.

If it is "no big deal", as you say, why write them at all. Remove the warning from the console and quite living in the past.

Thanks!

 

[Corentin Cras-Méneur]

Hi Schwar4,

Well Corentin, this is a big deal when it is reported to the console
every 10 minutes that Entourage is open. It writes 1-8 lines every 10-20
minutes! So far today, there are 58 lines listed in 5 hours.

Well it doesn't really slow down your computer and doesn't take up that
much space either (58 lines of plain text in the log??).
When I said I didn't think it was a huge deal, I meant that certificate
support is working just fine at this point and there is nothing to worry
about.

If it is "no big deal", as you say, why write them at all. Remove the
warning from the console and quite living in the past.

It's something Apple did to warn developers that the method they use to
access certificates in the keychain is depreceated and might not work in
"a" future version of the OS. A simple warning to stear future
development in a different direction. Right now, it's working just fine.
The fact is that the current version of Office was developped before
Apple made the change from storing the certificates in the X509Anchors
to the login keychain. My bet is that bridging from X509Anchors to the
login keychain will still be around for quite a few updates of the
System.

I'm not sure I'd want MS to spend hours and hours changing things (and
potentially introduce a new bug) so that the warnings disappear from the
Console logs instead of bringing new features or improve the current
ones in future releases.
Not very high in my own personal list of things I'd like them to do :-\


Corentin