dovecot - Mar 2019 - dovecot 2.3.5 - tests fail: http payload echo (ssl)

On 2019-03-08 18:40, Stephan Bosch via dovecot wrote:
> Since you're compiling it anyway, maybe you should first try to
increase
> the CLIENT_PROGRESS_TIMEOUT in src/lib-http/test-http-payload.c. It is
> currently 10 seconds.
I've increased the value to 30. This worked. No more timeout.

However, I also tried to link dovecot against a self compiled dynamic
openssl 1.1.1 and in that case, there's no issue at all. (With timeout
value 10.)

Another issue is that linking against a static openssl 1.1.1 fails
miserably. But apparently there are more and more products that ignore
the premise that linking against a static openssl is safer. dovecot is
not the only SW that does not work with a static openssl variant.

Cheers,
  K. C.

-- 
regards Helmut K. C. Tessarek              KeyID 0x172380A011EF4944
Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944

/*
   Thou shalt not follow the NULL pointer for chaos and madness
   await thee at its end.
*/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL:
<https://dovecot.org/pipermail/dovecot/attachments/20190318/f2d0de9a/attachment.sig>

On Mon, 18 Mar 2019 17:14:24 -0400
"Helmut K. C. Tessarek via dovecot" <dovecot at dovecot.org>
wrote:
> On 2019-03-08 18:40, Stephan Bosch via dovecot wrote:
> > Since you're compiling it anyway, maybe you should first try to
> > increase the CLIENT_PROGRESS_TIMEOUT in
> > src/lib-http/test-http-payload.c. It is currently 10 seconds.
> 
> I've increased the value to 30. This worked. No more timeout.
> 
> However, I also tried to link dovecot against a self compiled dynamic
> openssl 1.1.1 and in that case, there's no issue at all. (With timeout
> value 10.)
> 
> Another issue is that linking against a static openssl 1.1.1 fails
> miserably. But apparently there are more and more products that ignore
> the premise that linking against a static openssl is safer. dovecot is
> not the only SW that does not work with a static openssl variant.
Just a guess ... maybe it is lack of entropy on the build machine?
Try running haveged.


-- 
          openSUSE - SUSE Linux is my linux
              openSUSE is good for you
                  www.opensuse.org

On 2019-03-18 19:04, Marcus Rueckert via dovecot wrote:
> Just a guess ... maybe it is lack of entropy on the build machine?
> Try running haveged.
Nope, the entropy is just fine. But thanks for the idea.

Cheers,
  K. C.


-- 
regards Helmut K. C. Tessarek              KeyID 0x172380A011EF4944
Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944

/*
   Thou shalt not follow the NULL pointer for chaos and madness
   await thee at its end.
*/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL:
<https://dovecot.org/pipermail/dovecot/attachments/20190326/a0eb32cb/attachment.sig>