From: Glenn Morris <rgm@gnu.org>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: Oleksii Shevchuk <alxchk@gmail.com>,
13374@debbugs.gnu.org, Ted Zlatanov <tzz@lifelogs.com>
Subject: bug#13374: 24.?; open-gnutls-stream insecurity
Date: Mon, 07 Jan 2013 23:27:23 -0500 [thread overview]
Message-ID: <3fhamscn9w.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <m3ehhw2tn3.fsf@stories.gnus.org> (Lars Magne Ingebrigtsen's message of "Tue, 08 Jan 2013 05:20:00 +0100")
Lars Magne Ingebrigtsen wrote:
> Well, the issue is what we do when we get a certificate we can't
> validate.
>
> The traditional thing to do is to query the user for whether to connect
> anyway, and whether to record a permanent exception for that
> certificate.
>
> The code to do that hasn't been written yet.
>
> It's very common for SMTP and IMAP servers to use self-signed
> certificates, so just forcing ":validate t" for all connections would
> essentially mean that Emacs would be unusable for reading/sending email
> (using encryption) before that code has been written.
Ah well, ok, thanks for the explanation. It sounds then like it's
probably better to leave this for trunk rather than try and force it
into 24.3 at this relatively late stage.
next prev parent reply other threads:[~2013-01-08 4:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 10:20 bug#13374: 24.?; open-gnutls-stream insecurity Oleksii Shevchuk
2013-01-08 1:05 ` Glenn Morris
2013-01-08 4:20 ` Lars Magne Ingebrigtsen
2013-01-08 4:27 ` Glenn Morris [this message]
2013-01-08 4:42 ` Lars Magne Ingebrigtsen
2013-01-08 14:43 ` Ted Zlatanov
2013-01-08 14:49 ` Lars Magne Ingebrigtsen
2013-01-08 15:24 ` Ted Zlatanov
2013-01-08 17:06 ` Stefan Monnier
2013-12-18 22:50 ` Ted Zlatanov
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=3fhamscn9w.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=13374@debbugs.gnu.org \
--cc=alxchk@gmail.com \
--cc=larsi@gnus.org \
--cc=tzz@lifelogs.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.
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).