On 11/03/2014 04:27 AM, Oswald Buddenhagen wrote:
> On Sun, Nov 02, 2014 at 10:19:41AM +0100, Oswald Buddenhagen wrote:
>
> there is a genuine bug in mbsync - i made a somewhat too optimistic
> assumption about how openssl manages its certificate store. fix is
> upcoming, but not before the next we
On Sun, Nov 02, 2014 at 10:19:41AM +0100, Oswald Buddenhagen wrote:
> but anyway, let's take this off-list. please tell me the real hostnames,
> and attach the cert, so i can do real debugging.
>
there is a genuine bug in mbsync - i made a somewhat too optimistic
assumption about how openssl manag
On Sat, Nov 01, 2014 at 06:49:02PM -0400, Anthony DiSante wrote:
> I tried -CAfile too: it gives the same result as specifying no cert, except
> without the initial "verify error:num=19:self signed cert" error. I gather
> that's probably important,
>
yes, it is.
> Of course, if any of the long
On 11/01/2014 04:50 PM, Oswald Buddenhagen wrote:
> On Sat, Nov 01, 2014 at 11:44:34AM -0400, Anthony DiSante wrote:
>> $ openssl s_client -connect mail.mysite.com:993 -cert
>> /mail/certs/mail.mysite.com
>> unable to load client certificate private key file
>> 140542267004576:error:0906D06C:PEM r
On Sat, Nov 01, 2014 at 11:44:34AM -0400, Anthony DiSante wrote:
> $ openssl s_client -connect mail.mysite.com:993 -cert
> /mail/certs/mail.mysite.com
> unable to load client certificate private key file
> 140542267004576:error:0906D06C:PEM routines:PEM_read_bio:no start
> line:pem_lib.c:696:Expe
On Sat, Nov 01, 2014 at 11:44:34AM -0400, Anthony DiSante wrote:
>
> But when I specify my cert, it fails to connect:
>
> _
>
> $ openssl s_client -connect mail.mysite.com:993 -cert
> /mail/certs/mail.mysite.com
> unable to load client certificate private key file
> 140542267004576:error:09
On 11/01/2014 06:45 AM, Oswald Buddenhagen wrote:
> On Fri, Oct 31, 2014 at 10:17:48PM -0400, Anthony DiSante wrote:
>> Connecting to mail.mysite.com (W.X.Y.Z:993)...
>> Error, certificate owner does not match hostname mail.mysite.com
>>
>> What can I do?
>
On Fri, Oct 31, 2014 at 10:17:48PM -0400, Anthony DiSante wrote:
> Connecting to mail.mysite.com (W.X.Y.Z:993)...
> Error, certificate owner does not match hostname mail.mysite.com
>
> What can I do?
>
continue where the thread y
e.com (W.X.Y.Z:993)...
Opening slave local...
Error, certificate owner does not match hostname mail.mysite.com
---
Here is my config file:
---
Expunge None
Create Slave
MaildirStore local
Path /mail/data/
IMAPStore procremote
Host mail.mysite.com
f
> > validity.''
> >
> > However, I still get the error ``certificate owner does not match
> > hostname''. The error is right in that the domain of the certificate does
> > not match the Host domain in the configuration. It is wrong in that
> > accord
On Sat, Jul 19, 2014 at 08:03:53PM +0200, Mark Pustjens wrote:
> According to the manual on the option CertificateFile:
> ``Directly matched peer certificates are always trusted, regardless of
> validity.''
>
> However, I still get the error ``certificate owner does not
Now with patch.
On Sat, 19 Jul 2014, Mark Pustjens wrote:
Hi,
According to the manual on the option CertificateFile:
``Directly matched peer certificates are always trusted, regardless of
validity.''
However, I still get the error ``certificate owner does not match hostname
Hi,
According to the manual on the option CertificateFile:
``Directly matched peer certificates are always trusted, regardless of
validity.''
However, I still get the error ``certificate owner does not match
hostname''. The error is right in that the domain of the certifi
13 matches
Mail list logo