From: Jon Ronnenberg <jon.ronnenberg@gmail.com>
To: discuss@mandoc.bsd.lv
Subject: Re: certificate has expired for https://mandoc.bsd.lv according to curl
Date: Wed, 7 Dec 2022 21:27:53 +0100 [thread overview]
Message-ID: <CAPEZGVv3s6sE++dj-3qe4Z0Gb4_32+KsuPCrzUOCLGfsrso2AA@mail.gmail.com> (raw)
In-Reply-To: <e95edc25-f13f-ff14-53d9-c42e6d86e80b@bsd.lv>
Thank you for responding so quickly! Will you write here when the
certificate has been updated? Currently `brew install openssh` is
b0rken - and surely many other other "brews" that depends on mandoc.
On Wed, Dec 7, 2022 at 9:14 PM Kristaps Dzonsons <kristaps@bsd.lv> wrote:
>
> That's my fault for not updating the box in a hot second... I'll get us
> up to speed asap, which will pull the newest ACME certs. Thank you for
> reporting this!
>
> On 12/7/22 11:35, Jon Ronnenberg wrote:
> > Here is what I get from curl 7.54.0:
> >
> > curl -vI https://mandoc.bsd.lv/snapshots/mandoc-1.14.6.tar.gz
> > Trying 66.111.2.12...
> > TCP_NODELAY set
> > Connected to mandoc.bsd.lv (66.111.2.12) port 443 (#0)
> > ALPN, offering h2
> > ALPN, offering http/1.1
> > Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
> > successfully set certificate verify locations:
> > CAfile: /etc/ssl/cert.pem
> > CApath: none
> > TLSv1.2 (OUT), TLS handshake, Client hello (1):
> > TLSv1.2 (IN), TLS handshake, Server hello (2):
> > TLSv1.2 (IN), TLS handshake, Certificate (11):
> > TLSv1.2 (OUT), TLS alert, Server hello (2):
> > SSL certificate problem: certificate has expired
> > stopped the pause stream!
> > Closing connection 0
> > curl: (60) SSL certificate problem: certificate has expired
> > --
> > To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv
> >
> --
> To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv
>
--
To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv
next prev parent reply other threads:[~2022-12-07 20:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 19:35 Jon Ronnenberg
2022-12-07 20:14 ` Kristaps Dzonsons
2022-12-07 20:27 ` Jon Ronnenberg [this message]
2022-12-07 21:51 ` Raf Czlonka
2022-12-08 10:19 ` Jon Ronnenberg
2022-12-08 10:28 ` Raf Czlonka
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=CAPEZGVv3s6sE++dj-3qe4Z0Gb4_32+KsuPCrzUOCLGfsrso2AA@mail.gmail.com \
--to=jon.ronnenberg@gmail.com \
--cc=discuss@mandoc.bsd.lv \
/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 NNTP newsgroup(s).