23 Jan 2010
Sorry that I’m later than I’m supposed to be with this blogpost, but my new day job needs all the attention at the moment. The good news is there are not much problems when you update your Mac with the latest security update. Read more about it in Apple’s Knowledge base article.
On Leopard there is a small known issue with postfix. To correct it comment out or delete the following line from ‘/etc/postfix/main.cf‘:
Restart postfix (reloading config does not work) with:
sudo postfix start
And all should be fine. If you find another issue please use the comments.



4:01 am
After the update broke access to a secure (SSL) Web resource protocol https. Error is very interesting, because access to the SSL does not work only for the external addresses received by PPTP, on the internal address everything is fine …
The test was run the following query:
openssl s_client -connect my_external_ip:443 -ssl2
openssl s_client -connect my_external_ip:443 -ssl3
openssl s_client -connect my_external_ip:443 -tls1
1:12 pm
I didn’t notice any problem when using SSL over HTTP or with IMAP and SMTP over SSL. Where would you encounter this problem in our setup ?
5:13 pm
HTTPS is broken where content renegociation is used. This typically occurs when you use a Directory or a Location section in your Apache configuration requiring to renegociate the SSL connection (such as requiring client certificates for certain part of a website).