[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#10904: 24.0.93; Infinite loop in GnuTLS code during Gnus nnimap-init
bug#10904: 24.0.93; Infinite loop in GnuTLS code during Gnus nnimap-initiated SSL handshake
Thu, 02 Jun 2016 10:21:12 -0400
Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux)
On Fri, 05 Feb 2016 18:26:46 +1100 Lars Ingebrigtsen <address@hidden> 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
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.
|[Prev in Thread]
||[Next in Thread]|
- bug#10904: 24.0.93; Infinite loop in GnuTLS code during Gnus nnimap-initiated SSL handshake,
Ted Zlatanov <=