https://bugs.exim.org/show_bug.cgi?id=1895

Git Commit <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED
                 CC|                            |[email protected]

--- Comment #5 from Git Commit <[email protected]> ---
Git commit:
http://git.exim.org/exim.git/commitdiff/317e40ac8b1b816f4a22620a5647c6258de61598

commit 317e40ac8b1b816f4a22620a5647c6258de61598
Author:     Phil Pennock <[email protected]>
AuthorDate: Sun May 29 02:31:18 2016 -0400
Commit:     Phil Pennock <[email protected]>
CommitDate: Sat Oct 8 19:23:37 2016 -0400

    dh parameters update, new values & default

    * add three new exim-specific dh parameter constants; state provenance,
      but no way for others to verify; this is a signed commit, which is
      about as much as we can do for the truly paranoid: provide an audit
      trail.
    * add the rfc 7919 dh primes
      + no tls feature negotiation, per 7919, but the dh primes can be used
        if folks so choose
    * fixed broken format string in util/gen_pkcs3.c
    * tried to make gen_pkcs3.c support q values.
      + turns out, q doesn't affect the pem and that's not a mistake in my
        initialisation; i've checked with a cryptographer, we're losing some
        server-side optimizations but not any security properties for our
        scenario.

    fixes: 1895
----
 doc/doc-docbook/spec.xfpt |  38 +++-
 doc/doc-txt/ChangeLog     |   3 +
 doc/doc-txt/NewStuff      |   2 +
 src/scripts/source_checks |   1 +
 src/src/std-crypto.c      | 503 +++++++++++++++++++++++++++++++++++++++++++++-
 src/util/.gitignore       |   2 +
 src/util/gen_pkcs3.c      |  41 +++-
 7 files changed, 574 insertions(+), 16 deletions(-)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-- 
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim 
details at http://www.exim.org/ ##

Reply via email to