* Ian Jackson , 2016-09-30, 15:03:
you can completely disable external network with socket_wrapper
... which is a pretty heavy-weight solution, and in fact it breaks asyncssh's
tests.
Then that is clearly a bug in asyncssh's tests
... or in socket_wrapper, or in the way I used socket_wrapper.
2016-09-29 22:54 GMT+02:00 Jakub Wilk :
> * Jakub Wilk , 2016-09-07, 23:49:
>
>> you can completely disable external network with socket_wrapper
>>
>
> ... which is a pretty heavy-weight solution, and in fact it breaks
> asyncssh's tests.
>
> Luckily, glibc has a way to disable DNS queries without
Jakub Wilk writes ("Re: Alternative solution (was: Re: Network access during
build)"):
> * Jakub Wilk , 2016-09-07, 23:49:
> >you can completely disable external network with socket_wrapper
>
> ... which is a pretty heavy-weight solution, and in fact it breaks
> asy
* Jakub Wilk , 2016-09-07, 23:49:
you can completely disable external network with socket_wrapper
... which is a pretty heavy-weight solution, and in fact it breaks asyncssh's
tests.
Luckily, glibc has a way to disable DNS queries without LD_PRELOAD trickery:
$ RES_OPTIONS=attempts:0 wget h
* Christian Seiler , 2016-09-07, 07:43:
That way, you can force host name resolution to not use DNS for your
test suite (via just using a hosts file), then there will be no network
access during package build, and you don't have to keep rebasing a
patch. And, even better, IF there is a host nam
* Christian Seiler , 2016-09-07, 07:43:
And, even better, IF there is a host name called 'fail' on the local
network
...or when your ISP hijacks all NXDOMAIN responses...
, using nss_wrapper the package build will still succeed.
--
Jakub Wilk
On 09/07/2016 07:17 AM, Vincent Bernat wrote:
> One of the package that I maintain (python-asyncssh) makes a DNS request
> during build and expects it to fail. Since Policy 4.9 forbids network
> access (in a rather confusing wording "may not"), I got this serious
> bug:
> https://bugs.debian.org/c
7 matches
Mail list logo
