John Goerzen <[EMAIL PROTECTED]> wrote: > Now, whenever a client attempts to use TLS, I see:
> 2006-10-21 22:00:08 TLS error on connection from xxx (yyy) [x.x.x] (DH params > import): Base64 decoding error. On 2006-10-22 John Goerzen <[EMAIL PROTECTED]> wrote: > After quite some time, I discovered the problem to be > /var/spool/exim4/gnutls-params. > On my systems that hadn't been running exim4 before, but had freshly > installed this version, it was a happy ASCII text file. > On the system with the problem, it had binary data in it. > On a whim, I ran /usr/share/exim4/exim4_refresh_gnutls-params, which > solved the problem. > No idea why it was a problem, or why this fixed it. The internal format of the file was changed to make it possible to re-generate it offline (with certtool or openssl). Exim used to be able to still read the old format iirc, some later change must have broken this. cu andreas -- The 'Galactic Cleaning' policy undertaken by Emperor Zhark is a personal vision of the emperor's, and its inclusion in this work does not constitute tacit approval by the author or the publisher for any such projects, howsoever undertaken. (c) Jasper Ffforde -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
