On Wed, Apr 22, 2020 at 11:02:47AM +0200, Michael Tuexen wrote:
> > On 22. Apr 2020, at 10:38, Matt Caswell wrote:
> >
> >
> >
> > On 21/04/2020 23:45, Michael Tuexen wrote:
> >>> Looks like the failing call is here:
> >>>
> >>> if (setsockopt(sock, IPPROTO_IPV6, IPV6_V6ONLY,
> >>>
> On 22. Apr 2020, at 10:38, Matt Caswell wrote:
>
>
>
> On 21/04/2020 23:45, Michael Tuexen wrote:
>>> Looks like the failing call is here:
>>>
>>> if (setsockopt(sock, IPPROTO_IPV6, IPV6_V6ONLY,
>>> (const void *), sizeof(on)) != 0) {
>> Can you provide a pointer
On Tue, Apr 21, 2020, Matt Caswell wrote:
> changes in this area. Were you successfully able to run the tests with
> previous versions of OpenSSL?
It's the first time I compiled 1.1.1 on that host. Just to check I
tried 1.1.1d and it shows the same problem, so it's not a regression.
On 21/04/2020 23:45, Michael Tuexen wrote:
>> Looks like the failing call is here:
>>
>>if (setsockopt(sock, IPPROTO_IPV6, IPV6_V6ONLY,
>> (const void *), sizeof(on)) != 0) {
> Can you provide a pointer to the code?
Yes, its here:
On 2020-04-21 18:45, Michael Tuexen wrote:
On 21. Apr 2020, at 23:49, Matt Caswell wrote:
On 21/04/2020 18:34, Claus Assmann wrote:
Thanks for the reply, below is the output, It seems it only fails
because the host doesn't support IPv6?
Yes - it does seem to be an IPv6 problem. I don't
> On 21. Apr 2020, at 23:49, Matt Caswell wrote:
>
>
>
> On 21/04/2020 18:34, Claus Assmann wrote:
>> Thanks for the reply, below is the output, It seems it only fails
>> because the host doesn't support IPv6?
>
> Yes - it does seem to be an IPv6 problem. I don't recall any recent
> changes
On Tue, Apr 21, 2020 at 10:49:25PM +0100, Matt Caswell wrote:
>
> Looks like the failing call is here:
>
> if (setsockopt(sock, IPPROTO_IPV6, IPV6_V6ONLY,
>(const void *), sizeof(on)) != 0) {
>
> To which we get an errno indicating "Invalid argument". So it looks
On 21/04/2020 18:34, Claus Assmann wrote:
> Thanks for the reply, below is the output, It seems it only fails
> because the host doesn't support IPv6?
Yes - it does seem to be an IPv6 problem. I don't recall any recent
changes in this area. Were you successfully able to run the tests with
Summary: The OpenSSL 1.1.1g test suite contains at least two bugs:
TestBug#1: Test suite fails if local network has no IPv6, error message
(non-
verbose) doesn't say that's the issue. [ Testing IPv6 makes sense,
rejecting
regression tests on inadequate machines is important to avoid
On Tue, Apr 21, 2020, Benjamin Kaduk via openssl-users wrote:
> On Tue, Apr 21, 2020 at 07:22:38PM +0200, Claus Assmann wrote:
> > ../test/recipes/80-test_ssl_old.t ..
> > Dubious, test returned 1 (wstat 256, 0x100)
> Please run again with `make V=1 TESTS=test_ssl_old test` and
On Tue, Apr 21, 2020 at 07:22:38PM +0200, Claus Assmann wrote:
> Note sure whether this is already known (a search didn't bring up
> anything meaningful):
>
> ../test/recipes/80-test_ssl_old.t ..
> Dubious, test returned 1 (wstat 256, 0x100)
> Failed 1/6 subtests
> Test Summary
Note sure whether this is already known (a search didn't bring up
anything meaningful):
../test/recipes/80-test_ssl_old.t ..
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/6 subtests
Test Summary Report
---
../test/recipes/80-test_ssl_old.t
12 matches
Mail list logo
