Comments on: Mac OS X Security Update 2010-001 http://diymacserver.com/2010/01/23/mac-os-x-security-update-2010-001/ Thu, 29 Jul 2010 19:40:56 +0000 http://wordpress.org/?v=2.9.1 hourly 1 By: ybart http://diymacserver.com/2010/01/23/mac-os-x-security-update-2010-001/comment-page-1/#comment-6841 ybart Sat, 10 Apr 2010 16:13:04 +0000 http://diymacserver.com/?p=1164#comment-6841 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). 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).

]]> By: Richard http://diymacserver.com/2010/01/23/mac-os-x-security-update-2010-001/comment-page-1/#comment-6506 Richard Sat, 06 Feb 2010 12:12:27 +0000 http://diymacserver.com/?p=1164#comment-6506 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 ? 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 ?

]]> By: Pavel V Subach http://diymacserver.com/2010/01/23/mac-os-x-security-update-2010-001/comment-page-1/#comment-6504 Pavel V Subach Sat, 06 Feb 2010 03:01:25 +0000 http://diymacserver.com/?p=1164#comment-6504 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 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

]]>