Hi Sebastian,
On Tue, 19 Mar 2019 08:27:32 +0100, Sebastian Andrzej Siewior wrote:
> Yes. The problem was that setting a lower DH key was aborted but instead
> of error the success code was returned. The github issue is
> https://github.com/openssl/openssl/issues/7677
>
> and dovecot was
On 2019-03-19 08:39:37 [+0900], Atsuhito Kohda wrote:
> Hi Sebastian,
Hi, Atsuhito
> On Mon, 18 Mar 2019 20:34:04 +0100, Sebastian Andrzej Siewior wrote:
>
> > I suggest to close this bug becuase I don't think it is an openssl bug
> > nor dovecot. The part about minimal key/cipher requirement is
Hi Sebastian,
On Mon, 18 Mar 2019 20:34:04 +0100, Sebastian Andrzej Siewior wrote:
> I suggest to close this bug becuase I don't think it is an openssl bug
> nor dovecot. The part about minimal key/cipher requirement is already
> documented since 1.1.1-2 in NEWS.Debian.gz. The difference between
On Mon, 18 Mar 2019 12:06:59 +0100, Kurt Roeckx wrote:
> So I assume that somewhere in the past you also did something like
> that, and that the old file was still a 1024 bit file? Or did you
> just not have an ssl_dh line in your config because the old config
> files didn't have it and it wasn't
I suggest to close this bug becuase I don't think it is an openssl bug
nor dovecot. The part about minimal key/cipher requirement is already
documented since 1.1.1-2 in NEWS.Debian.gz. The difference between a and
b release is simply that it now the return code is now set properly in
the error
On Mon, Mar 18, 2019 at 01:55:50PM +0900, Atsuhito Kohda wrote:
> Hi Kurt,
>
> > So from what I understand, the problem is really on the dovecot
> > side. What does dovecot's log show?
> >
> > Dovecot can configure DH, which seems to default to:
> > ssl_dh = >
> > That file should be fine,
Hi Kurt,
> So from what I understand, the problem is really on the dovecot
> side. What does dovecot's log show?
>
> Dovecot can configure DH, which seems to default to:
> ssl_dh =
> That file should be fine, it's 4096 bit.
I generated 4096 bit dh_key:
openssl dhparam -out /path/to/dh.pem
Hi Kurt,
On Sat, 16 Mar 2019 14:59:16 +0100, Kurt Roeckx wrote:
> So from what I understand, the problem is really on the dovecot
> side. What does dovecot's log show?
>
> Dovecot can configure DH, which seems to default to:
> ssl_dh =
> That file should be fine, it's 4096 bit.
Today is
On Sat, Mar 16, 2019 at 09:06:06AM +0900, Atsuhito Kohda wrote:
> Hi Sebastian,
>
> On Fri, 15 Mar 2019 22:08:13 +0100, Sebastian Andrzej Siewior wrote:
>
> > Do you have somewhere more information what failed on the fetchmail
> > side?
>
> Yes, I have error messages of fetchmail but they
Hi Sebastian,
On Fri, 15 Mar 2019 22:08:13 +0100, Sebastian Andrzej Siewior wrote:
> Do you have somewhere more information what failed on the fetchmail
> side?
Yes, I have error messages of fetchmail but they contains
some Japanese characters. (I added simple translations of
them but not
On 2019-03-15 11:42:37 [+0900], Atsuhito Kohda wrote:
> A bit precise info:
> I upgraded openssl on both server and local macheines.
> Then the problem happened so, first, I downgraded openssl
> on local machine but the problem remained. So I downgraded
> openssl on server machine then fetchmail
Package: openssl
Version: 1.1.1b-1
Severity: important
Dear Maintainer,
I updated openssl 1.1.1a-1 to 1.1.1b-1 then fetchmail failed
to get new email.
So I downgraded openssl to 1.1.1a-1 then fetchmail worked
fine again.
I believe there is a bug in openssl 1.1.1b-1 .
I heard that new Debian will
12 matches
Mail list logo
