From: Ted Zlatanov <tzz@lifelogs.com>
To: 10904@debbugs.gnu.org
Subject: bug#10904: 24.0.93; Infinite loop in GnuTLS code during Gnus nnimap-initiated SSL handshake
Date: Thu, 02 Jun 2016 10:21:12 -0400 [thread overview]
Message-ID: <87eg8fllif.fsf@lifelogs.com> (raw)
In-Reply-To: <m3obsjg7i0.fsf@ducky.fitzsim.org>
On Fri, 05 Feb 2016 18:26:46 +1100 Lars Ingebrigtsen <larsi@gnus.org> wrote:
LI> Hm. But then those stores parameters should be used the next time in
LI> network-stream, and it doesn't have access to those stored parameters.
Specific security-related could be saved in network-security.data on the
fly. This would serve the use case of "I just want to override this
right now."
They could also be provided by auth-source.el, so you could say
server specialserver priority-string "PERFORMANCE"
This would serve the use case of "I want to override the priority string
every time but without customizing variables".
Finally, `gnutls-algorithm-priority' can be extended similarly to
`gnutls-verify-error' to work per host. So that would provide for the
third use case of the Customize user.
I think the better way is to make a top-level `gnutls-boot-parameters'
variable that has all the relevant settings per host, and make the
function `gnutls-boot-parameters' simply look inside that variable (the
name may not be right). Then we could obsolete
`gnutls-algorithm-priority', `gnutls-verify-error' and
`gnutls-min-prime-bits' in favor of that variable, and provide the
corresponding auth-source.el glue so the settings could also be
retrieved from auth-source.
Ted
prev parent reply other threads:[~2016-06-02 14:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 23:51 bug#10904: 24.0.93; Infinite loop in GnuTLS code during Gnus nnimap-initiated SSL handshake Thomas Fitzsimmons
2012-03-03 14:56 ` Lars Magne Ingebrigtsen
2012-03-19 13:54 ` Ted Zlatanov
2012-03-21 15:40 ` Thomas Fitzsimmons
2012-03-22 21:29 ` Lars Magne Ingebrigtsen
2012-03-24 22:04 ` Thomas Fitzsimmons
2012-03-30 12:13 ` Ted Zlatanov
2012-03-30 21:52 ` Thomas Fitzsimmons
2012-04-08 17:46 ` Thomas Fitzsimmons
2012-04-09 0:37 ` Ted Zlatanov
2012-04-09 13:14 ` Ted Zlatanov
2012-04-10 3:07 ` Thomas Fitzsimmons
2012-04-10 11:54 ` Ted Zlatanov
2012-04-10 17:44 ` Lars Magne Ingebrigtsen
2012-04-11 12:02 ` Ted Zlatanov
2014-12-08 20:06 ` Lars Magne Ingebrigtsen
2014-12-10 16:10 ` Ted Zlatanov
2016-02-05 7:26 ` Lars Ingebrigtsen
2016-06-02 14:21 ` Ted Zlatanov [this message]
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=87eg8fllif.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=10904@debbugs.gnu.org \
--cc=bug-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.