From: Brian Inglis <Brian.Inglis@SystematicSW.ab.ca>
To: cygwin@cygwin.com
Subject: Re: ca-certificates{,-letsencrypt}
Date: Fri, 2 Feb 2024 10:54:01 -0700 [thread overview]
Message-ID: <f963e7d4-ee9f-4c9c-bd37-04b91fd09277@SystematicSW.ab.ca> (raw)
In-Reply-To: <Zb0e7efOIpti5bUA@ingber.com>
Hi Lester,
You should see those other directories on both machines.
I suggest re-installing those packages using latest setup-x86_64 with admin rights;
ensure in Task Manager that nothing is running from Cygwin bin paths before
starting until postinstall scripts have completed;
after check for errors in /var/log/setup.log.full.
On 2024-02-02 09:57, Lester Ingber via Cygwin wrote:
> Yes, I am using the latest package versions.
> I am not running letsencrypt on her machine (I am on mine).
> When I perform:
> 08:41:18 @LouiseLG:/etc/pki/ca-trust:% ls -dl /etc/pki/ca-trust/**/
> drwxr-xr-x 1 lingber None 0 Feb 1 08:28 /etc/pki/ca-trust/extracted/
> drwxr-xr-x 1 lingber None 0 Feb 1 08:28 /etc/pki/ca-trust/source/
> When I perform:
> ls -dglo /etc/pki/ca-trust/**/
> I get the same results.
> I added letsencrypt as you suggested.
> I now see:
> Package: _/ca-certificates-letsencrypt
> ca-certificates-letsencrypt.sh exit code 1
> Package: _/Unknown package
> ca-certificates.sh exit code 1
> On 2024-02-01 08:40, Lester Ingber via Cygwin wrote:
>> Yes, a Reinstall is the first thing I tried.
>> I just tried that again after installing 3.5.0-1, with the same negative
>> result.
>
> Presumably you are installing the latest package versions?
>
> There used to be a problem where the programs made the directories read only so
> updates failed.
>
> Check /var/log/setup.log.full for errors perhaps from
> ca-certificates/-letsencrypt or p11-kit.
>
> Try checking permissions by running `ls -dl /etc/pki/ca-trust/**/`:
>
> $ ls -dglo /etc/pki/ca-trust/**/
> drwxr-xr-x 1 0 Jan 8 07:36 /etc/pki/ca-trust/
> drwxr-xr-x 1 0 Jan 8 07:31 /etc/pki/ca-trust/extracted/
> drwxr-xr-x 1 0 Jan 8 07:36 /etc/pki/ca-trust/extracted/edk2/
> drwxr-xr-x 1 0 Jan 8 07:36 /etc/pki/ca-trust/extracted/java/
> drwxr-xr-x 1 0 Jan 8 07:36 /etc/pki/ca-trust/extracted/openssl/
> drwxr-xr-x 1 0 Jan 8 07:36 /etc/pki/ca-trust/extracted/pem/
> dr-xr-xr-x 1 0 Jan 8 07:36 /etc/pki/ca-trust/extracted/pem/directory-hash/
> drwxr-xr-x 1 0 Jan 8 07:36 /etc/pki/ca-trust/source/
> drwxr-xr-x 1 0 Sep 6 2022 /etc/pki/ca-trust/source/anchors/
> drwxr-xr-x 1 0 Sep 6 2022 /etc/pki/ca-trust/source/blacklist/
>
> note only directory-hash is read only [used -go to omit ids and reduce width].
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
prev parent reply other threads:[~2024-02-02 17:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 16:57 Lester Ingber
2024-02-02 17:54 ` Brian Inglis [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f963e7d4-ee9f-4c9c-bd37-04b91fd09277@SystematicSW.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).