unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Timothy Sample <samplet@ngyro.com>
To: Bengt Richter <bokr@bokr.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Feedback from JRES in Dijon
Date: Sat, 07 Dec 2019 23:11:19 -0500	[thread overview]
Message-ID: <87lfrnv4m0.fsf@ngyro.com> (raw)
In-Reply-To: <20191208024849.GA11149@PhantoNv4ArchGx.localdomain> (Bengt Richter's message of "Sat, 7 Dec 2019 18:48:49 -0800")

Hi Bengt,

I omitted a lot of your message, but I hope I have the easy explanation
you’re looking for.  :)

Bengt Richter <bokr@bokr.com> writes:

> On +2019-12-07 11:35:02 -0500, Timothy Sample wrote:
>> 
>> [...]
>> 
>> Unfortunately, I got certificate errors, but VLC lets you temporarily
>> ignore those.
>
> [...]
>
> Anyone see an easy explanation?

After a little more digging, it seems that the certificate sent for
“ccwebcast.in2p3.fr” is signed with an intermediate certificate from
“TERENA”.  This is in turn signed with a DigiCert root certificate.
Unfortunately it looks like “ccwebcast.in2p3.fr” doesn’t send the whole
certificate chain, and the TERENA cert is not part of our “nss-certs”
package, so tools using certs from that package (basically everything on
a normal Guix install) will be unwilling to trust “ccwebcast.in2p3.fr”.
IceCat is okay with it, but it uses its own certificates (it must know
about the TERENA cert, so it doesn’t need the whole chain).

Fortunately, for exceptional situations like this, you can tell most
tools to skip certificate validation (like I mentioned with VLC).  For
youtube-dl, you can use the “--no-check-certificate” option.  Note
however that this is rather dangerous in general, since you are telling
youtube-dl allow anyone to pretend to be anyone else!  In this case,
since it’s just a video and IceCat is okay with the certificate it’s
probably fine.  Just be careful.  :)


-- Tim

  reply	other threads:[~2019-12-08  4:11 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-05 14:16 Feedback from JRES in Dijon Julien Lepiller
2019-12-05 14:34 ` Pierre Neidhardt
2019-12-05 14:42   ` Julien Lepiller
2019-12-05 15:44     ` Konrad Hinsen
2019-12-05 15:52       ` zimoun
2019-12-06  7:07         ` Bengt Richter
2019-12-06 12:24           ` Konrad Hinsen
2019-12-07 16:35             ` Timothy Sample
2019-12-08  2:48               ` Bengt Richter
2019-12-08  4:11                 ` Timothy Sample [this message]
2019-12-08 23:09                   ` Bengt Richter
2019-12-09  5:23                     ` Konrad Hinsen
2019-12-06 12:57         ` Konrad Hinsen
2019-12-10 16:57           ` Ludovic Courtès
2019-12-11 20:48             ` Konrad Hinsen
2020-01-07 16:05           ` Proposal for a blog contribution on reproducible computations Konrad Hinsen
2020-01-09 20:40             ` zimoun
2020-01-10 16:59             ` Ludovic Courtès
2020-01-10 17:19               ` zimoun
2020-01-10 18:53               ` Giovanni Biscuolo
2020-01-11  9:31               ` Konrad Hinsen
2020-01-11 14:05                 ` Giovanni Biscuolo
2020-01-13  8:37                 ` Ludovic Courtès
2020-01-14  9:06               ` Konrad Hinsen
2020-01-14 15:38                 ` Ludovic Courtès
2020-01-14 16:18                   ` Konrad Hinsen
2020-01-14 16:40                     ` Ludovic Courtès
2020-01-10 17:03             ` Ludovic Courtès
2020-01-11  9:39               ` Konrad Hinsen
2020-01-15 22:20                 ` Ludovic Courtès
2019-12-05 15:47     ` Feedback from JRES in Dijon zimoun
2019-12-05 14:39 ` Julien Lepiller
2019-12-05 15:42 ` zimoun
2019-12-10 17:06 ` Ludovic Courtès

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=87lfrnv4m0.fsf@ngyro.com \
    --to=samplet@ngyro.com \
    --cc=bokr@bokr.com \
    --cc=guix-devel@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).