From: Tobias Geerinckx-Rice <me@tobias.gr>
To: help-guix@gnu.org
Subject: Re: Guix and clamav, freshclam doesn't dowload
Date: Fri, 03 Apr 2020 18:25:38 +0200 [thread overview]
Message-ID: <87d08o4juw.fsf@nckx> (raw)
In-Reply-To: <86090f22-76ad-47c5-a2d8-cbb12e786bc8@localhost>
[-- Attachment #1: Type: text/plain, Size: 948 bytes --]
白い熊,
白い熊 写道：
> Now, running freshclam, I get:
>
> ClamAV update process started at Fri Apr 3 14:28:23 2020
> daily database available for download (remote version: 25770)
> WARNING: Download failed (60) WARNING: Message: SSL peer
> certificate or SSH remote key was not OK
This means that (lib)curl couldn't local trust store against which
to verify the server's certificate.
freshclam uses libcurl to download files, and the libcurl authors
have for better or worse decreed that every user has to take care
of pointing libcurl to the local store (instead of honouring
CURL_CA_BUNDLE in the library).
On most systems this isn't a problem because the default (/etc/…)
location exists. Not so on Guix: we rely entirely on
CURL_CA_BUNDLE being set to the correct location in /gnu/store.
Let's see how we can patch freshclam to point libcurl in the right
direction…
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2020-04-03 16:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 12:57 Guix and clamav, freshclam doesn't dowload 白い熊
2020-04-03 16:25 ` Tobias Geerinckx-Rice [this message]
2020-04-03 16:53 ` Marius Bakke
2020-04-03 17:04 ` Tobias Geerinckx-Rice
-- strict thread matches above, loose matches on Subject: below --
2020-04-03 17:50 白い熊
2020-04-04 10:48 ` 白い熊
2020-04-04 11:53 ` Marius Bakke
2020-04-04 12:19 ` 白い熊
2020-04-04 17:36 ` Marius Bakke
2020-04-05 5:29 ` 白い熊
2020-04-17 10:31 ` 白い熊
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d08o4juw.fsf@nckx \
--to=me@tobias.gr \
--cc=help-guix@gnu.org \
/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).