From: Stefan Monnier <monnier@iro.umontreal.ca>
To: help-gnu-emacs@gnu.org
Subject: Re: Unable to use `package-refresh-contents`: Bad signature from GNU ELPA Signing Agent
Date: Sat, 09 Mar 2019 15:15:56 -0500 [thread overview]
Message-ID: <jwvlg1nvmau.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: alpine.NEB.2.21.1903090256170.27575@panix1.panix.com
> It was because I didn't have the latest tls package installed.
> This didn't used to be necessary but now appears necessary.
I don't know of any `tls.el` package other than a very old one that
should be considered deprecated nowadays (and still comes bundled with
Emacs in `lisp/obsolete/tls.el`). The SSL/TLS handling in Emacs
nowadays is handled by the libgnutls code, so it doesn't require any
Elisp package. If that doesn't work well for you please `M-x
report-emacs-bug`.
Stefan
next prev parent reply other threads:[~2019-03-09 20:15 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-09 8:46 Unable to use `package-refresh-contents`: Bad signature from GNU ELPA Signing Agent Nicky Chorley
2019-02-10 12:40 ` Robert Pluim
2019-02-10 15:05 ` Stefan Monnier
2019-03-09 6:52 ` Nicky Chorley
2019-03-09 7:57 ` Jude DaShiell
2019-03-09 20:15 ` Stefan Monnier [this message]
2019-03-09 20:34 ` Jude DaShiell
2019-06-13 7:25 ` Nicky Chorley
2019-06-13 12:23 ` Van L
2019-04-01 16:49 ` usenet qqk8
2019-04-01 22:03 ` usenet Emanuel Berg
-- strict thread matches above, loose matches on Subject: below --
2019-06-22 7:26 Unable to use `package-refresh-contents`: Bad signature from GNU ELPA Signing Agent Nicky Chorley
2019-06-22 13:04 ` VanL
2019-06-23 4:50 ` Nicky Chorley
2019-06-23 11:50 ` VanL
2019-06-23 14:19 ` Nicky Chorley
2019-06-24 8:13 ` VanL
2019-06-24 19:00 ` Nicky Chorley
2019-06-25 10:26 ` VanL
2019-06-24 12:50 ` Stefan Monnier
2019-06-23 18:21 ` Jude DaShiell
2019-06-24 12:49 ` Stefan Monnier
2019-06-24 18:58 ` Nicky Chorley
2019-06-24 20:38 ` Jude DaShiell
2019-06-22 16:15 ` Stefan Monnier
2019-06-25 14:45 Nicky Chorley
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=jwvlg1nvmau.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=help-gnu-emacs@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.