From: "Steven Levine" Received: from [192.168.100.201] (HELO mail.2rosenthals.com) by 2rosenthals.com (CommuniGate Pro SMTP 5.4.10) with ESMTP id 11570292 for ecs-isp@2rosenthals.com; Wed, 25 Dec 2024 01:25:49 -0500 Received: from [192.168.200.201] (port=35724 helo=mail2.2rosenthals.com) by mail.2rosenthals.com with esmtp (Exim 4.97.1) (envelope-from ) id 1tQKpw-000000002lC-1XHJ for ecs-isp@2rosenthals.com; Wed, 25 Dec 2024 01:25:40 -0500 Received: from mta-202b.earthlink-vadesecure.net ([51.81.232.241]:52699 helo=mta-202a.earthlink-vadesecure.net) by mail2.2rosenthals.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.97.1) (envelope-from ) id 1tQKpt-000000006EV-16dT for ecs-isp@2rosenthals.com; Wed, 25 Dec 2024 01:25:37 -0500 DKIM-Signature: v=1; a=rsa-sha256; bh=JM2b+TgAopTrLvEBbDgIN9/0Sg7OTz6yQk5s80 QFcWU=; c=relaxed/relaxed; d=earthlink.net; h=from:reply-to:subject: date:to:cc:resent-date:resent-from:resent-to:resent-cc:in-reply-to: references:list-id:list-help:list-unsubscribe:list-unsubscribe-post: list-subscribe:list-post:list-owner:list-archive; q=dns/txt; s=dk12062016; t=1735107936; x=1735712736; b=kGGE9kEIqdluPN5RmVsJ5+iXvKc xA9VZvyxbjiIns9eGu8/ptIBR3cpm/mkRyFSQQV2GcOCy4YT5+0/xfvHpuL9H48+QlH+e4O rT12qAK0lXaAtXfl0KQ0qLmR9kpcueT94PCBrtFm0bZprUGiZfqjdH82DMp7YsrViyCvAvs YR2BEuo52DqLr04ilkBbTMC8u1Z5Mgz14wqsJDCHPxyMNDvw19fCjIwbEBQ2pUdMn2itrLd zNSnk5MUu11jFydm8bvCOWkWCP/hVfHanqTlYcM5sd5NDONfz2FoU82UK/WHwmSixn31MbA F7FETVaSQN7RDVI/kFJ/I6/FIb68REQ== Received: from slamain ([172.56.178.196]) by vsel2nmtao02p.internal.vadesecure.com with ngmta id bcbf7b16-1814577992cb3f36; Wed, 25 Dec 2024 06:25:36 +0000 Message-ID: <676ba02d.13.mr2ice.fgrirsq@earthlink.net> Date: Tue, 24 Dec 2024 22:03:25 -0800 To: "eCS ISP Mailing List" In-Reply-To: Subject: Re: [eCS-ISP] Getting started with Let's Encrypt X-Mailer: MR/2 Internet Cruiser Edition for OS/2 v3.00.11.24/60 In , on 12/19/24 at 07:21 PM, "Peter Moylan" said: Hi Peter, >You're right. I hadn't even heard of groups.io. I've just done some >googling about it, and got as far as getting a list of all groups, but I >couldn't find any mention of OS/2. The list name tend to say warp, rather than OS/2 Mailing-List: list main@warp.groups.io; contact main+owner@warp.groups.io List-Id: List-Subscribe: List-Help: Mailing-List: list warp-technical@warp.groups.io; contact warp-technical+owner@warp.groups.io List-Id: List-Subscribe: List-Help: >The problem, I guess, is that I >stopped reading the OS/2 Usenet newsgroups a few years ago, after the >traffic started dying. Most of the traffic these days is on the os2world forums. There's also facebook, discord and bluesky groups, but I don't really have enough unused time to monitor them. >While rewriting the manual, I had a closer look at what I had received >from Let's Encrypt. (It's confusing having two files called key.pem, and >multiple files all called cert.pem, but I guess there's no way around >that. It just how the author chose to name things. The folder names that contain cert.pem and key.pem are the named after the domains. Not a big deal once you get used to it. >Is this form of bundling the two standard practice? Yes. It's probably documented somewhere in the RFCs. The PEM file is just a type of container. It can contain any number and combination of keys and certificates and other kind of data as long as the data is encoded according to the PEM file rules. For example, on your OS/2 box you should have \etc\pki\ca-trust\extracted\pem\tls-ca-bundle.pem Steven -- ---------------------------------------------------------------------- "Steven Levine" Warp/DIY/BlueLion etc. www.scoug.com www.arcanoae.com www.warpcave.com ----------------------------------------------------------------------