I don't really know how to test this, but did you look into whether the aws-lc
patches from i.e. lang/deno apply and fix the problems you're seeing?
There's a chance that these are an easier solution than the Cargo.lock
gymnastics..
On 3/23/26 10:02 PM, Christoph Liebender wrote:
On 3/11/26 17:53, Christoph Liebender wrote:
On 3/2/26 19:31, Christoph Liebender wrote:
Am 24.02.26 um 21:28 schrieb Christoph Liebender:
Good evening ports@,
I hereby submit a patch that integrates the 1.7.0 release of mollysocket.
Among other changes, upstream finally supports terminating the service with
SIGTERM, so rc does not have to escalate to SIGKILL. However, some patches
were necessary since a transitive dependency introduced aws-lc-rs, which
made the program segfault. Telling the reqwest crate to use native-tls
instead makes it work for me.
Last but not least, I added some unveil restrictions as well for good measure.
comments, testers, ok?
Ping!
pinggg
Hi again. I'm sorry to beat a dead horse - but I can confidently say that this
has been running for me without issue since I initially submitted the patch. I
had a look again to see whether or not it is affected by the recent pledge/
unveil changes, and it is - probably obviously - not, as it only calls unveil.
So, is there a chance for this to make it into 7.9?
- christoph
