* Nikolaus Rath , 2016-09-30, 14:07:
Luckily, glibc has a way to disable DNS queries without LD_PRELOAD trickery:
$ RES_OPTIONS=attempts:0 wget http://www.example.com/
Wow, I wonder many people have used this innocent environment variable name
and been bitten by weird network failures..
The
* 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.
On Sep 29 2016, Jakub Wilk wrote:
> Luckily, glibc has a way to disable DNS queries without LD_PRELOAD trickery:
>
> $ RES_OPTIONS=attempts:0 wget http://www.example.com/
Wow, I wonder many people have used this innocent environment variable
name and been bitten by weird network failures.. Couldn
❦ 29 septembre 2016 22:54 CEST, Jakub Wilk :
>>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_OPT
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
On 07/09/16 08:43, Christian Seiler wrote:
> There's a piece of software called nss_wrapper, written by the
> Samba people, that allows you to modify glibc's DNS functions'
> (getaddrinfo, gethostbyname, ...) behavior via an LD_PRELOAD
> library. It's called nss_wrapper;
This is an excellent sugg
* 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
On Wed, Sep 7, 2016 at 9:07 PM, Thomas Goirand wrote:
> This seem a pretty good solution to the problem. Could you show an
> example in a package that does that, or maybe a patch for this kind of
> bug that Lamby opened?
build-rdeps says that varnish-modules and sssd use nss-wrapper.
--
bye,
pa
On 09/07/2016 07:43 AM, Christian Seiler wrote:
> 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
* 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:43 AM, Christian Seiler wrote:
> However, instead of disabling the test via a patch, [...]
Yet another solution would be to upstream a patch that adds the
@unittest.skipIf(os.getenv('TESTS_NO_NETWORK_ACCESS') == '1',
'No network access allowed in test suite')
de
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
On Fri, Sep 23, 2005 at 04:54:56PM +0200, Gernot Salzer wrote:
>
> Well, the problem has been around since at least 2002, so I'd prefer to start
> doing something about it.
Ok, ok. Just for the sake of those being bitten by this bug I've made
portreserve packages and sent and ITP. Packages are cu
15 matches
Mail list logo
