On Jan 3, 2008 2:36 AM, Marc Haber <<a href="mailto:mh+gnutls-devel@zugschlus.de">mh+gnutls-devel@zugschlus.de</a>> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br><br>Simon writes:<br>> Appears to be an unreprodicible problem with a specific<br>> certificate/key which the user cannot reveal. Another certificate/key<br>> from the same CA works fine. Theory: could it be CRLF problems? Other
<br>> non-ASCII characters in the file? Nothing indicates a real GnuTLS<br>> problem here.<br>> Conclusion: Likely not a GnuTLS problem.<br><br>I think that this conclusion was built too fast, but we do not have<br>
sufficient information to know this.<br><br>The original reporter has said in the mean time that there are no<br>non-ascii chars in the file and that there are no CRLF issues here.<br>Currently, it is suspected that GnuTLS has issues with the fact that
<br>the certificate is a wildcard certificate.</blockquote><div><br>By reading this report, I'm really curious which gnutls version is used, and <br>whether the gnutls-serv and exim are linked on the same version of gnutls.
<br>Does this occur if exim is linked on gnutls 2.2?<br><br>regards,<br>Nikos<br><br><br></div></div>