A function returning a default and a list which defined the value of "default"
disagreed. Switch both to a macro to make it harder for them to fall out of
sync.
Find and fix by Gavan. Although NetBSD is not a supported platform for
4.94 this bug could affect other platforms.
Find and fix by Gavan. Although NetBSD is not a supported platform for
4.94 this bug could affect other platforms.
+PP/01 Fix default prime selection to be consistent.
+ One path used ike23 still, instead of exim.dev.20160529.3; now both
+ execution flows will use the same DH primes (currently
+ exim.dev.20160529.3).
+
Exim version 4.94
-----------------
Exim version 4.94
-----------------
+#define EXIM_DH_PRIME_DEFAULT dh_exim_20160529_3
+
/* KEEP SORTED ALPHABETICALLY;
* duplicate PEM are okay, if we want aliases, but names must be alphabetical */
static struct dh_constant dh_constants[] = {
/* label pem */
/* KEEP SORTED ALPHABETICALLY;
* duplicate PEM are okay, if we want aliases, but names must be alphabetical */
static struct dh_constant dh_constants[] = {
/* label pem */
- { "default", dh_exim_20160529_3 },
+ { "default", EXIM_DH_PRIME_DEFAULT },
{ "exim.dev.20160529.1", dh_exim_20160529_1 },
{ "exim.dev.20160529.2", dh_exim_20160529_2 },
{ "exim.dev.20160529.3", dh_exim_20160529_3 },
{ "exim.dev.20160529.1", dh_exim_20160529_1 },
{ "exim.dev.20160529.2", dh_exim_20160529_2 },
{ "exim.dev.20160529.3", dh_exim_20160529_3 },
const char *
std_dh_prime_default(void)
{
const char *
std_dh_prime_default(void)
{
+ return EXIM_DH_PRIME_DEFAULT;