Hi,

On 2024-04-03 12:37, Philipp Kern wrote:
> Hi,
> 
> On Tue, Apr 02, 2024 at 06:58:35AM +0200, Aurelien Jarno wrote:
> > On 2024-04-02 09:21, Sean Whitton wrote:
> > > Hello,
> > > 
> > > On Mon 01 Apr 2024 at 05:29pm +02, Aurelien Jarno wrote:
> > > 
> > > > The debian policy, section 4.9, forbids network access for packages in
> > > > the main archive, which implicitly means they are authorized for
> > > > packages in contrib and non-free (and non-free-firmware once #1029211 is
> > > > fixed).
> > > >
> > > > This gives constraints on the build daemons infrastructure and also
> > > > brings some security concerns. Would it be possible to extend this
> > > > restriction to all archives?
> > > 
> > > We need to know if this is going to break existing packages and allow
> > > some input from their maintainers.  Are you able to prepare a list of
> > > the affected packages?
> > 
> > Fair enough. I can work on that, but help would be welcome as my
> > resources are limited.
> 
> I did a test rebuild of contrib, non-free and non-free-firmware packages
> in sid with both stable sbuild schroot and unshare backends and could
> not find a difference in build success (i.e. what failed failed in both,
> what succeeded succeeded in both).

Thanks Philipp. Following that result, please find a patch proposal: 

--- a/policy/ch-source.rst
+++ b/policy/ch-source.rst
@@ -338,9 +338,9 @@
 For example, the build target should pass ``--disable-silent-rules``
 to any configure scripts.  See also :ref:`s-binaries`.
 
-For packages in the main archive, required targets must not attempt
-network access, except, via the loopback interface, to services on the
-build host that have been started by the build.
+Required targets must not attempt network access, except, via the
+loopback interface, to services on the build host that have been started
+by the build.
 
 Required targets must not attempt to write outside of the unpacked
 source package tree.  There are two exceptions.  Firstly, the binary

Regards
Aurelien

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurel...@aurel32.net                     http://aurel32.net

Attachment: signature.asc
Description: PGP signature

Reply via email to