From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: Oleksii Shevchuk <alxchk@gmail.com>, 13374@debbugs.gnu.org
Subject: bug#13374: 24.?; open-gnutls-stream insecurity
Date: Tue, 08 Jan 2013 12:06:08 -0500 [thread overview]
Message-ID: <jwvd2xf7glb.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <m338ybpw5j.fsf@stories.gnus.org> (Lars Magne Ingebrigtsen's message of "Tue, 08 Jan 2013 15:49:28 +0100")
>> It should default to nil (in other words, we'll ship 24.3 with the same
>> insecure behavior it has right now). But we can recommend to the users
>> to turn it on, and see how well it works in practice, and write the
>> necessary prompts and customization logic that Lars outlined.
> I think we should just leave things as is for 24.3, since it's too close
> to release, and fix this properly for 24.5.
I tend to agree, although, if the patch is sufficiently trivial, it
could be accepted (e.g. define a new custom var, with nil default value
and splice it somewhere in the code where nil makes no difference).
> Instituting an option like that (which will have to be abandoned
> later) as a stop-gap I feel isn't all that helpful.
If the option will have to be abandoned, then it's indeed a loser, but
I thought the idea is that this option will stay and the added code in
24.4 will "simply" be handling errors more cleverly and prompting the
user to update this option on-the-fly.
Stefan
next prev parent reply other threads:[~2013-01-08 17:06 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvd2xf7glb.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=13374@debbugs.gnu.org \
--cc=alxchk@gmail.com \
--cc=larsi@gnus.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.