i’m having the same issues, is there any way to fix the certs, or a db that needs updating so ichat, apache, etc, can get their collective heads out of their collective posteriors?
this is driving me insane.
i had a self-signed cert, working ok after several days of back and forth.. at some point it just locked in ok on the self-signed… perhaps it was 10.5.2..? can’t remember.
then i had my cert signed by godaddy and everything broke.
apache and postfix seem ok with the new signed cert, but ichat has always been hiccup-y, and now it won’t login with the new cert at all.
i see the new certs in the etc/certs folder, with ‘chkey’ suffixes, etc. if i remove them, jabber makes them when it launches… but it won’t successfully log anyone in with it. this may indeed be a password wrapper issue, but WTF? isn’t there anyway to fix this without commenting out things in the certs files??? like a password app via cli/terminal or something smart and unix-y like that?
i see some possibly related items on the upcoming 10.5.3 fix list, but i’m not holding my breath.
any help appreciated, tia!
Recent Comments