unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Kaushal Modi <kaushal.modi@gmail.com>
To: Robert Pluim <rpluim@gmail.com>
Cc: Jude DaShiell <jdashiel@panix.com>,
	Help Gnu Emacs mailing list <help-gnu-emacs@gnu.org>
Subject: Re: Special configuration needed for eww + gnutls? [emacs 28.1]
Date: Fri, 15 Apr 2022 14:00:01 -0400	[thread overview]
Message-ID: <CAFyQvY2avvBcXG4+cH8CR+2S1QYO3VKzSkEYHVY83OiKvpySZw@mail.gmail.com> (raw)
In-Reply-To: <87pmli2r4q.fsf@gmail.com>

On Fri, Apr 15, 2022 at 1:28 PM Robert Pluim <rpluim@gmail.com> wrote:
>
> scripter.co works for me with GnuTLS 3.7.1
>
> This might be the Letʼs Encrypt cross-signing certificate expiry
> issue, which is fixed in GnuTLS >= 3.6.14 See eg
> <https://blog.germancoding.com/2021/04/16/lets-encrypt-and-expired-root-certificates/>

Thanks!

> (although Iʼm wondering why itʼs taken so long for you to notice)

It just means that I haven't used eww in a long time (at least since
April 2021) 😁

I tried updating gnutls locally on my machine (where I don't have root
privileges)
- Tried to update gnutls, but it failed because I don't have libnettle.
- Tried to install libnettle, but if failed because
"downloads/nettle-3.7.3/examples/nettle-openssl.c:408: undefined
reference to `EVP_MD_CTX_new'"

I guess I will have to ask the sysadmin to update the gnutls lib.

Thanks for your help! This explains why eww works for me the last time
it worked (> 2 years back) and why it doesn't work now.



  reply	other threads:[~2022-04-15 18:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-14 16:34 Special configuration needed for eww + gnutls? [emacs 28.1] Kaushal Modi
2022-04-15  2:04 ` Jude DaShiell
2022-04-15 16:53   ` Kaushal Modi
2022-04-15 17:28     ` Robert Pluim
2022-04-15 18:00       ` Kaushal Modi [this message]
2022-04-17 14:14         ` Robert Pluim

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://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAFyQvY2avvBcXG4+cH8CR+2S1QYO3VKzSkEYHVY83OiKvpySZw@mail.gmail.com \
    --to=kaushal.modi@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=jdashiel@panix.com \
    --cc=rpluim@gmail.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).