From: "Paul Smedley" Received: from [192.168.100.201] (HELO mail.2rosenthals.com) by 2rosenthals.com (CommuniGate Pro SMTP 5.4.10) with ESMTP id 10602021 for ecs-isp@2rosenthals.com; Thu, 15 Aug 2024 21:52:48 -0400 Received: from [192.168.200.201] (port=52247 helo=mail2.2rosenthals.com) by mail.2rosenthals.com with esmtp (Exim 4.97.1) (envelope-from ) id 1sem8u-000000006Hm-0iKZ for ecs-isp@2rosenthals.com; Thu, 15 Aug 2024 21:52:40 -0400 Received: from firebrick.ash.relay.mailchannels.net ([23.83.222.59]:25275) by mail2.2rosenthals.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.97.1) (envelope-from ) id 1sem8n-000000007EK-1n5j for ecs-isp@2rosenthals.com; Thu, 15 Aug 2024 21:52:34 -0400 X-Sender-Id: perthwebhosting|x-authuser|paul@smedley.id.au Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 55AB3106265 for ; Fri, 16 Aug 2024 01:52:32 +0000 (UTC) Received: from colossiansvm.perthwebhosting.net.au (unknown [127.0.0.6]) (Authenticated sender: perthwebhosting) by relay.mailchannels.net (Postfix) with ESMTPA id 8B7F5108200 for ; Fri, 16 Aug 2024 01:52:31 +0000 (UTC) ARC-Seal: i=1; s=arc-2022; d=mailchannels.net; t=1723773152; a=rsa-sha256; cv=none; b=gcdLo5x1nzXSPwLLUING3CzeqmsFjChTnvC6dYkSfq93NBs2ql+9X5xtHTWHfh0FIoUYJt ZKnBS7/JAPYxkeRJlrHwPvorBzfDzPwK04oL0DztLXVzGiXSEzbQJhCG8YDlRwA0L2uKls bL/p+5DvO8oyRlA/9nyghC6EerdNCOxVVhF+TM/TUuk4DGTEWpk0VpTeFWe5qlbPd9NnEU WERC+Z7SjlNAC0iDn5zLg9saxvtE+3PxvUcZEnFEBeplYu0pRzaC54cDF+YAHCMI6fsNlg SZfjLNm63KoxAxpTqpIZ+yKv5+6Fb2ZtdCjiGqwgL2NCXYrJkBfhvcwdyFnAMQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=mailchannels.net; s=arc-2022; t=1723773152; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=4K11RDN5Rb/zsVLu2TS+q90gc2Y8Wgqv1+IIavzq+Rw=; b=wuYKR+5NwjTiAjWT8mAB4IT/5fLlvdrzE8nliMCv9KO8KedRFx8gmQg2N8YzrJBvOsmpk4 oYmLDwqXOsmDzEX1wiwelhNDYpaP+NsOIJOepWGuP4s9mW4U9zWLug3hPcV4u9579LMnWY aWBJt5EHb09XR0KQ/X1vdjvrLCw/yC8/+DJ8FW5kkCRd4NeLvIv6Hn0b5MoMDUbTk3XF0W mqaUF0OzjJtSzo2XhY/1mMAGyXrDCwlz97qxruCumCIhE0hXQtdcsgu6/nigiKVcc775I0 GN+u+XAbEz3Pga8+hLWI8Iu8NuqSnsJPAjdIykIPMCA2ku0Vf6kT5BNunnPFLQ== ARC-Authentication-Results: i=1; rspamd-587694846-kfb92; auth=pass smtp.auth=perthwebhosting smtp.mailfrom=paul@smedley.id.au X-Sender-Id: perthwebhosting|x-authuser|paul@smedley.id.au X-MC-Relay: Neutral X-MailChannels-SenderId: perthwebhosting|x-authuser|paul@smedley.id.au X-MailChannels-Auth-Id: perthwebhosting X-Society-Glossy: 04cf306b53a90c6e_1723773152202_2661578224 X-MC-Loop-Signature: 1723773152202:960586926 X-MC-Ingress-Time: 1723773152202 Received: from colossiansvm.perthwebhosting.net.au (colossiansvm.perthwebhosting.net.au [103.13.84.198]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384) by 100.110.76.118 (trex/7.0.2); Fri, 16 Aug 2024 01:52:32 +0000 Received: from smedley.org ([45.249.117.21]:55526 helo=[192.168.1.159]) by colossiansvm.perthwebhosting.net.au with esmtpsa (TLS1.3) tls TLS_AES_128_GCM_SHA256 (Exim 4.97.1) (envelope-from ) id 1sem8k-0000000C4OI-0Qrm for ecs-isp@2rosenthals.com; Fri, 16 Aug 2024 09:52:29 +0800 Content-Type: multipart/alternative; boundary="------------GVe7lueuurtO2Ungfgrf0w6p" Message-ID: <006ef4e0-ae2a-42ec-9e12-b5dd73126ec6@smedley.id.au> Date: Fri, 16 Aug 2024 11:22:28 +0930 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [eCS-ISP] Apache HTTPS To: eCS ISP Mailing List References: <5F99CECB-7FA2-4E11-AC5A-C4052431A062@smedley.id.au> Content-Language: en-AU In-Reply-To: <5F99CECB-7FA2-4E11-AC5A-C4052431A062@smedley.id.au> X-AuthUser: paul@smedley.id.au This is a multi-part message in MIME format. --------------GVe7lueuurtO2Ungfgrf0w6p Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Further to this - 1.2.4 DOES use open_memstream.... On 14/8/24 06:23, Paul Smedley wrote: > No, it does not make sense to add additional complexity whilst we're > trying to resolve usability defects with the current port. > > > On 14 August 2024 5:00:16 am ACST, "Massimo S." > wrote: > > Il 13/08/2024 11:49, Paul Smedley ha scritto: > > Hi Steven, On 13/8/24 01:22, Steven Levine wrote: > > uacme hardcodes the configuration directory to > /etc/ssl/uacme.  Most of us use the libc path rewriter > which with default settings will map this path to > %ETC/ssl/uacme. Perhaps the next build should use > /@unixroot/etc/ssl rather than /etc/ssl? This generally > works better with apps built against kLIBC? > > With https://smedley.id.au/tmp/uacme-1.0.19-os2-20240813.zip - > it should look in /@unixroot/etc I'll aim to create a github > repo for this later in the week. Cheers, Paul > > Hi Paul, should not better to rebuild 1.2.4 instead of the old > 1.0.19? thanks massimo > ------------------------------------------------------------------------ > This message is sent to you because you are subscribed to the > mailing list . To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail > to To switch to the INDEX mode, > E-mail to Send administrative > queries to To subscribe (new > addresses), E-mail to: and reply to > the confirmation email. Web archives are publicly available at: > http://lists.2rosenthals.com This list is hosted by Rosenthal & > Rosenthal, LLC P.O. Box 281, Deer Park, NY 11729-0281. Non- > electronic communications related to content contained in these > messages should be directed to the above address. (CAN-SPAM Act of > 2003) > ------------------------------------------------------------------------ > --------------GVe7lueuurtO2Ungfgrf0w6p Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit

Further to this - 1.2.4 DOES use open_memstream....

On 14/8/24 06:23, Paul Smedley wrote:
No, it does not make sense to add additional complexity whilst we're trying to resolve usability defects with the current port.


On 14 August 2024 5:00:16 am ACST, "Massimo S." <ecs-isp@2rosenthals.com> wrote:
Il 13/08/2024 11:49, Paul Smedley ha scritto:
Hi Steven, On 13/8/24 01:22, Steven Levine wrote:
uacme hardcodes the configuration directory to /etc/ssl/uacme.  Most of us use the libc path rewriter which with default settings will map this path to %ETC/ssl/uacme. Perhaps the next build should use /@unixroot/etc/ssl rather than /etc/ssl? This generally works better with apps built against kLIBC?
With https://smedley.id.au/tmp/uacme-1.0.19-os2-20240813.zip - it should look in /@unixroot/etc I'll aim to create a github repo for this later in the week. Cheers, Paul
Hi Paul, should not better to rebuild 1.2.4 instead of the old 1.0.19? thanks massimo
This message is sent to you because you are subscribed to the mailing list <ecs-isp@2rosenthals.com>. To unsubscribe, E-mail to: <ecs-isp-off@2rosenthals.com> To switch to the DIGEST mode, E-mail to <ecs-isp-digest@2rosenthals.com> To switch to the INDEX mode, E-mail to <ecs-isp-index@2rosenthals.com> Send administrative queries to <ecs-isp-request@2rosenthals.com> To subscribe (new addresses), E-mail to: <ecs-isp-on@2rosenthals.com> and reply to the confirmation email. Web archives are publicly available at: http://lists.2rosenthals.com This list is hosted by Rosenthal & Rosenthal, LLC P.O. Box 281, Deer Park, NY 11729-0281. Non- electronic communications related to content contained in these messages should be directed to the above address. (CAN-SPAM Act of 2003)
--------------GVe7lueuurtO2Ungfgrf0w6p--