But it's ridiculous that we'd even have to resort to this! Apple needs to fix this!!! (see )Äownload VirtualBox, and install CentOS or another security-enhanced Linux flavor, and just run your server out of that on the Mac. You might be able to get away with just swapping out mod_ssl.so after you do your build. That will almost certainly require disabling System Integrity Protection because you can't modify the core OS files like apache2. In the mean time, the only real option you have, I guess, is to install OpenSSL 1.0.1 or later, download the Apache source code, and then build it linking against OpenSSL 1.0.1, and then replace OS X's Apache with the one you just built. ![]() Even if you could patch Server to work with TLS 1.2, what happens when Apple updates Server again, and it still doesn't support TLS 1.2? When you install that update, will it overwrite whatever you put into place? It's ridiculous that they don't, especially considering that in iOS 9 and El Capitan they require that Apple developers release software that only talks to TLS 1.2 servers. ![]() Go to and send feedback demanding that they update Server and OS X to support TLS 1.2.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |