Conversation

Notices

1. Embed this notice
   Ryan Castellucci :nonbinary_flag: (ryanc@infosec.exchange)'s status on Wednesday, 10-Apr-2024 16:52:15 JST Ryan Castellucci :nonbinary_flag:

   From tcpdump's configure scripts:

   Apple, bless their pointy little heads, apparently ship libcrypto as a library, but not the header files, in El Capitan, probably because they don't want you writing nasty portable code that could run on other UN*Xes, they want you writing code that uses their Shiny New Crypto Library and that only runs on macOS.

   • Embed this notice
     David Chisnall (david_chisnall@infosec.exchange)'s status on Wednesday, 10-Apr-2024 17:24:38 JST David Chisnall

     in reply to

     @ryanc I suspect it’s more that they want to be able to upgrade those libraries when they without breaking third-party things. FreeBSD also ships a few shared libraries without headers (though we stick them in a separate directory with rpath linkage so you can’t accidentally link them) because we don’t want them to be treated as part of the stable ABI. I’m not sure how stable the libcrypto ABIs are, but the rest of OpenSSL has a habit of breaking even source compatibility across versions. Apple almost certainly doesn’t want to be in a situation of having to choose between deploying a security fix or not breaking a load of third-party apps.