From: Ted Zlatanov <tzz@lifelogs.com>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: 16784@debbugs.gnu.org, sb@dod.no
Subject: bug#16784: 24.3; Problems opening NNTP connection: failing starttls because of a non-verified certificate
Date: Fri, 21 Mar 2014 06:23:16 -0400 [thread overview]
Message-ID: <87ob0z3l63.fsf@lifelogs.com> (raw)
In-Reply-To: <m3ior8x6h1.fsf@stories.gnus.org> (Lars Magne Ingebrigtsen's message of "Thu, 20 Mar 2014 15:58:02 +0100")
On Thu, 20 Mar 2014 15:58:02 +0100 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
LMI> Ted Zlatanov <tzz@lifelogs.com> writes:
SB> I would like one of the following solutions:
SB> 1. The possibility to switch off the attempted upgrade to STARTTLS for
SB> NNTP connections
>>
>> I think Lars has to give an opinion here.
LMI> I think we should always do encryption, even though we can't do validation.
So the answer is "no" to Steinar's question. I have to agree, although
it may be noisier, in 2014 it's the right way.
>> So basically customize that variable and add :trustfiles and :hostname
>> for the respective verifications, or nil to disable them.
LMI> When doing opportunistic upgrades (where the user hasn't asked for the
LMI> connection to be encrypted), bothering the user with warnings about not
LMI> being able to establish the identity of the server doesn't make much
LMI> sense.
I can only suggest overriding `gnutls-log-level' but that doesn't make
much sense if you're planning to use that connection, in which case you
care about those warnings. Do we need a way to defer GnuTLS warnings
(put them in a variable temporarily)?
Ted
next prev parent reply other threads:[~2014-03-21 10:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-17 17:50 bug#16784: 24.3; Problems opening NNTP connection: failing starttls because of a non-verified certificate sb
2014-02-18 15:43 ` Ted Zlatanov
2014-03-20 14:48 ` Ted Zlatanov
2014-03-20 14:58 ` Lars Magne Ingebrigtsen
2014-03-21 10:23 ` Ted Zlatanov [this message]
2014-03-21 10:33 ` Steinar Bang
2014-03-24 12:14 ` Lars Magne Ingebrigtsen
2014-12-08 20:07 ` Lars Magne 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=87ob0z3l63.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=16784@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=sb@dod.no \
/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).