<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">I have no problem loading websocket-driver via Quicklisp on macOS Monterey.<div class=""><br class=""></div><div class="">The error below is caused by cl+ssl trying to load libcrypto without a specific version which is no longer allowed by macOS. Apparently, cl+ssl was updated a while back to explicitly try specific versions to avoid this. So, check to make sure that all your distributions are up-to-date (ql:update-all-dists).</div><div class=""><br class=""><div class="">
<div style="color: rgb(0, 0, 0); font-variant: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); font-variant: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><span class="Apple-style-span" style="border-collapse: separate; font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; line-height: normal; border-spacing: 0px; -webkit-text-decorations-in-effect: none;"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-variant: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; border-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-stroke-width: 0px;"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""> - Gary Palter</div><div class=""> Principal Software Engineer</div><div class=""> Clozure Associates</div><div class=""><br class=""></div></div></div></span></div></span></div></div><br class="Apple-interchange-newline">
</div>
<div><br class=""><blockquote type="cite" class=""><div class="">On Oct 27, 2021, at 10:06 AM, Christopher Stacy <<a href="mailto:cstacy@dtpq.com" class="">cstacy@dtpq.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" class="">
<div class="">
On 10/26/21 4:44 PM, Christopher Stacy wrote:<br class="">
> System Version: macOS 12.0.1 (21A559)<br class="">
> Kernel Version: Darwin 21.1.0<br class="">
> System Integrity Protection: Disabled<br class="">
><br class="">
> Clozure Common Lisp Version 1.12 (v1.12) DarwinX8664<br class="">
> ; Loading "websocket-driver"<br class="">
> ? WARNING: /usr/local/src/ccl/dx86cl64 is loading libcrypto in
an unsafe way<br class="">
> Process inferior-lisp abort trap:<br class="">
> 6<br class="">
<br class="">
I suspect this may be a code-signing issue.<br class="">
<br class="">
MacOS has a feature to prevent "DLL hijacking" called "Library
Validation". This cannot be disabled without a kernel patch (and you
don't want to do that).<br class="">
<br class="">
<br class="">
<blockquote class=""><font face="monospace" class="">Starting in iOS 8 and macOS
10.10, the system offers library validation as a policy for the
dynamic libraries that a process links against. The policy is
simple: A program may link against any library with the same
team identifier in its code signature as the main executable, or
with any Apple system library. Requests to link against other
libraries are denied.</font><br class="">
<br class="">
<font face="monospace" class="">The team identifier is the 10-character
alphanumeric string, such as YH9SZ5LKR4, associated with your
developer account, and recorded in your Apple-issued signing
certificate.</font><br class="">
</blockquote>
<br class="">
I didn't see this issue at all in the last version of Big Sur. But
when I installed Monterey I get the above error right away when I
tried to load the CCL program I was working on (fine) before the OS
reboot.<br class="">
<br class="">
The protection is supposed to be enabled at the app level by a
codesign option. (Since I'm running the same binaries, I don't know
why this wasn't a problem before. Something to do with the new OS
obviously.)<br class="">
<br class="">
I might be off-track with this, because the sample error message for
failing this doesn't look like the one I am getting from CCL. (Maybe
that has something to do with CCL using an older API or something,
though. I have no idea what I am talking about.)<br class="">
<br class="">
<blockquote class=""><font face="monospace" class="">The error string includes the
name of the process, the pid, and the path to the dynamic
library. For example, the process ls with pid 528 trying to load
the library /private/tmp/libncurses.5.4.dylib generates the
following output:</font><br class="">
<br class="">
<font face="monospace" class="">AMFI: ls(pid 528) - [deny-mmap] mapped file
does not have a matching team identifier: /private/
tmp/libncurses.5.4.dylib</font><br class="">
<br class="">
<font face="monospace" class="">AMFI: ls(pid 528) - [deny-mmap] process has
team identifier BGHDFMN54X: /private/tmp/ libncurses.5.4.dylib</font><br class="">
<br class="">
<font face="monospace" class="">AMFI: ls(pid 528) - [deny-mmap] mapped file
has team identifier GDASFLKMKO: /private/tmp/
libncurses.5.4.dylib</font><br class="">
<br class="">
</blockquote><p class="">Does anyone know what's actually going on and how to work around
it?</p><p class="">I am just trying to use quicklisp to load the web drivers I need.</p><p class="">Dead in the water.</p><p class="">As I guess everyone is who upgrades to Monterey.</p><p class="">Btw, Monterey seems quite zippy on this 2014 Mini!<br class="">
</p><p class=""><br class="">
</p>
</div>
_______________________________________________<br class="">Openmcl-devel mailing list<br class=""><a href="mailto:Openmcl-devel@clozure.com" class="">Openmcl-devel@clozure.com</a><br class="">https://lists.clozure.com/mailman/listinfo/openmcl-devel<br class=""></div></blockquote></div><br class=""></div></body></html>