From 63d0d895a2ed1d0b04508d9cc645791f063607ac Mon Sep 17 00:00:00 2001 From: Rainer Gerhards Date: Wed, 12 Jun 2013 14:11:39 +0200 Subject: imrelp: add capability to directly specify GnuTLS priority string --- doc/imrelp.html | 11 +++++++++++ plugins/imrelp/imrelp.c | 6 ++++++ 2 files changed, 17 insertions(+) diff --git a/doc/imrelp.html b/doc/imrelp.html index 80117299..3795fb76 100644 --- a/doc/imrelp.html +++ b/doc/imrelp.html @@ -59,6 +59,17 @@ to changes/upgrades in GnuTLS (to check at config processing time, we would need to hardcode the supported bits and keep them in sync with GnuTLS - this is even impossible when custom GnuTLS changes are made...). +
  • tls.prioritystring (not mandatory, string)
    +This parameter permits to specify the so-called "priority string" to +GnuTLS. This string gives complete control over all crypto parameters, +including compression setting. For this reason, when the prioritystring +is specified, the "tls.compression" parameter has no effect and is +ignored. +
    Full information about how to construct a priority string can be +found in the GnuTLS manual. At the time of this writing, this +information was contained in +section 6.10 of the GnuTLS manual. +
  • Caveats/Known Bugs: