From: Aaron Jensen <aaronjensen@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 26835@debbugs.gnu.org
Subject: bug#26835: 26.0.50; url-retrieve no longer raises certificate errors
Date: Mon, 8 May 2017 12:44:52 -0700 [thread overview]
Message-ID: <CAHyO48z5yEe4hXHrrTzZvzT+ZaS=HZZati3YYwPXYxWG2bE=Gg@mail.gmail.com> (raw)
In-Reply-To: <8337cfcgr2.fsf@gnu.org>
On Mon, May 8, 2017 at 12:04 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Aaron Jensen <aaronjensen@gmail.com>
>> Date: Mon, 8 May 2017 11:42:45 -0700
>>
> I seem to be unable to reproduce any of the wrong behavior in the
> current master build. Could you please provide more details about
> what errors you see and what failures you expected, but didn't see?
>
> In my testing, Emacs asks me whether to continue connecting, when it
> discovers a bad certificate, and it's up to me to decide. Did it ask
> you, and if it did, what alternative did you select?
>
> Also, did you try all this in "emacs -Q"? It looks like you did this
> in a customized session (e.g., because in "emacs -Q" there's no 'loop'
> function, which the above snippet uses). So the problems could have
> something to do with your customizations.
It repros in `emacs -Q', just set:
(setq gnutls-verify-error t)
(url-retrieve-synchronously "https://wrong.host.badssl.com/")
In Emacs 25.2, this causes an error to be thrown when you use
url-retrieve, in 26, it silently proceeds.
Also, I can confirm that if gnutls-verify-error is nil, it prompts as
you described. I'll leave it as that for now in my config.
next prev parent reply other threads:[~2017-05-08 19:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 18:42 bug#26835: 26.0.50; url-retrieve no longer raises certificate errors Aaron Jensen
2017-05-08 19:04 ` Eli Zaretskii
2017-05-08 19:44 ` Aaron Jensen [this message]
2017-05-09 17:51 ` Eli Zaretskii
2017-05-10 14:24 ` Lars Ingebrigtsen
2017-05-10 16:48 ` Eli Zaretskii
2017-09-02 13:42 ` Eli Zaretskii
2017-09-13 18:11 ` Lars Ingebrigtsen
2017-09-13 18:44 ` Eli Zaretskii
2017-09-13 17:51 ` Lars Ingebrigtsen
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='CAHyO48z5yEe4hXHrrTzZvzT+ZaS=HZZati3YYwPXYxWG2bE=Gg@mail.gmail.com' \
--to=aaronjensen@gmail.com \
--cc=26835@debbugs.gnu.org \
--cc=eliz@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/emacs.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).