Store - typo at my den (have kb-issues)
Thanks and regards
Goetz R Schultz
>8
Quis custodiet ipsos custodes?
/"\
\ / ASCII Ribbon Campaign
X against HTML e-mail
/ \
8<
On 09/11/2022 21:28, Ruben Safir wrote:
This g
Ruben Safir wrote:
> > This got nothing to with LE or own CA. Bottom line is, you need to
> > add your own CA to the cert tore (ideally)
>
> what is a cert tore?
Someone has probably already replied to this, but it's a typo:
the OP wanted to say "store".
The certificate you created was used to
>
> This got nothing to with LE or own CA. Bottom line is, you need to
> add your own CA to the cert tore (ideally)
what is a cert tore?
> - look in DuckDuckGo how
> that works for your distri - Linux is different from BSD - for
> example.
>
> That would be my line in FreeBSD, using a single
On 09/11/2022 18:19, Alexander Dalloz wrote:
Am 09.11.2022 um 18:30 schrieb hi@zakaria.website:
On 2022-11-09 16:59, Alexander Dalloz wrote:
Am 09.11.2022 um 15:58 schrieb Ruben Safir:
Hello
I am getting this error and I have no idea why. openssh is upto date
You have a self-signed certifi
Am 09.11.2022 um 18:30 schrieb hi@zakaria.website:
On 2022-11-09 16:59, Alexander Dalloz wrote:
Am 09.11.2022 um 15:58 schrieb Ruben Safir:
Hello
I am getting this error and I have no idea why. openssh is upto date
You have a self-signed certificate in place. The connecting client
cannot v
On 2022-11-09 16:59, Alexander Dalloz wrote:
Am 09.11.2022 um 15:58 schrieb Ruben Safir:
Hello
I am getting this error and I have no idea why. openssh is upto date
You have a self-signed certificate in place. The connecting client
cannot valide whether to trust to answering server.
Alexan
Am 09.11.2022 um 15:58 schrieb Ruben Safir:
Hello
I am getting this error and I have no idea why. openssh is upto date
You have a self-signed certificate in place. The connecting client
cannot valide whether to trust to answering server.
Alexander
openssl s_client -connect mail.example.com:143 -starttls imap
would probably work much better.
Aki
> On 15/05/2020 20:10 Brandon Roa wrote:
>
>
> Oops, on second glance I don't think that error is actually directly
> related to what I was doing.
>
> I had been testing to see if the certifi
Oops, on second glance I don't think that error is actually directly
related to what I was doing.
I had been testing to see if the certificate chain was installed
properly by running
openssl s_client -connect mail.example.com:143
But there was no certificate reported in stdout. I thought tha
> On 15/05/2020 02:36 Brandon Roa wrote:
>
>
> I just installed a certificate on my mail server to Postfix and Dovecot.
> The certificate is functional on Postfix, but for some reason I keep
> getting this error. Any suggestions on how to fix it?
>
> mail dovecot: imap-login: Error: SSL: S
On 05/30/18 10:41, A. Schulze wrote:
In the third case an administrator has to provide files with
certificates. And these files are required (by best practice)
Do you have any pointers to support such a strong statement?
to include any chain-certificates excluding the self signed root.
Our
Aki Tuomi:
There is already ssl_client_ca, for verifying clients. ssl_ca verifies
certs when dovecot is connecting somewhere.
For clarification:
there is a third use case an admin may need intermediate certificates:
And that's where dovecot act as server providing imap/pop3/lmtp/sieve
vi
On Mon, 28 May 2018 15:03:29 +0300, Aki Tuomi wrote:
>> Sounds good. How about (re)naming them ssl-{client,server}_ca?
>
> There is already ssl_client_ca, for verifying clients. ssl_ca verifies
> certs when dovecot is connecting somewhere.
So there's three? I had no idea...
Cheerio,
hauke
--
On 28.05.2018 14:30, Hauke Fath wrote:
> On Mon, 28 May 2018 13:52:01 +0300, Aki Tuomi wrote:
>> I'm sure. But putting it as ssl_ca makes no sense, since it becomes
>> confused what it is for.
> I guess - I haven't had a need for client certs, and only ever used
> ssl_ca for the server ca chain.
On Mon, 28 May 2018 13:52:01 +0300, Aki Tuomi wrote:
> I'm sure. But putting it as ssl_ca makes no sense, since it becomes
> confused what it is for.
I guess - I haven't had a need for client certs, and only ever used
ssl_ca for the server ca chain.
> We can try restoring this as ssl_cert_chain
On 28.05.2018 13:05, Hauke Fath wrote:
> On 05/28/18 11:08, Aki Tuomi wrote:
>>
>>
>> On 28.05.2018 12:06, Hauke Fath wrote:
>>> On 05/21/18 17:55, Aki Tuomi wrote:
ssl_ca is used only for validating client certificates.
>>>
>>> But it was used (though not documented, IIRC) for validating se
On 05/28/18 11:08, Aki Tuomi wrote:
On 28.05.2018 12:06, Hauke Fath wrote:
On 05/21/18 17:55, Aki Tuomi wrote:
ssl_ca is used only for validating client certificates.
But it was used (though not documented, IIRC) for validating server
certs, too. Since intermediate CA certs are usually vali
On 28.05.2018 12:06, Hauke Fath wrote:
> On 05/21/18 17:55, Aki Tuomi wrote:
>> ssl_ca is used only for validating client certificates.
>
> But it was used (though not documented, IIRC) for validating server
> certs, too. Since intermediate CA certs are usually valid a lot longer
> than the serve
On 05/21/18 17:55, Aki Tuomi wrote:
ssl_ca is used only for validating client certificates.
But it was used (though not documented, IIRC) for validating server
certs, too. Since intermediate CA certs are usually valid a lot longer
than the server certs, having to concat the certs is awkward,
You forgot to cc the list.
ssl_ca is used only for validating client certificates.
---Aki TuomiDovecot oy
Original message From: Marc Perkel Date:
21/05/2018 18:25 (GMT+02:00) To: Aki Tuomi Subject:
Re: SSL error after upgrading to 2.31
On 05/21/2018 07:54
Does ssl_cert file contain intermediates?
---Aki TuomiDovecot oy
Original message From: Marc Perkel Date:
21/05/2018 16:32 (GMT+02:00) To: dovecot@dovecot.org Subject: SSL error after
upgrading to 2.31
After upgrading to 2.31 I'm getting this
error. Not sure what
On Thu, Oct 13, 2016 at 10:30 AM Christian Kivalo
wrote:
>
>
>
>
> On 2016-10-13 10:12, arnaud gaboury wrote:
>
> > On Thu, Oct 13, 2016 at 8:48 AM Christian Kivalo
>
> > wrote:
>
> >
>
> >>
>
> >>
>
> >>
>
> >>
>
> >> Am 13. Oktober 2016 08:41:06 MESZ, schrieb arnaud gaboury <
>
> >> arnaud.gab
On 2016-10-13 10:12, arnaud gaboury wrote:
On Thu, Oct 13, 2016 at 8:48 AM Christian Kivalo
wrote:
Am 13. Oktober 2016 08:41:06 MESZ, schrieb arnaud gaboury <
arnaud.gabo...@gmail.com>:
>I run dovecot + postfix as my email server. Everything is working as
>expected, but I see an error
On Thu, Oct 13, 2016 at 8:48 AM Christian Kivalo wrote:
>
>
>
>
> Am 13. Oktober 2016 08:41:06 MESZ, schrieb arnaud gaboury <
> arnaud.gabo...@gmail.com>:
>
> >I run dovecot + postfix as my email server. Everything is working as
>
> >expected, but I see an error in the dovecot logs:
>
> >
>
> >lm
Am 13. Oktober 2016 08:41:06 MESZ, schrieb arnaud gaboury
:
>I run dovecot + postfix as my email server. Everything is working as
>expected, but I see an error in the dovecot logs:
>
>lmtp(7331): Error: SSL context initialization failed, disabling SSL:
>ENGINE_init(dynamic) failed
>
>Dovecot is
25 matches
Mail list logo
