Re: Document correct buildd chroot setup somewhere?

To: Philipp Kern <pkern@debian.org>
Cc: Stefan Fritsch <sf@debian.org>, debian-wb-team@lists.debian.org, team@security.debian.org
Subject: Re: Document correct buildd chroot setup somewhere?
From: Andreas Barth <aba@not.so.argh.org>
Date: Mon, 5 Apr 2010 12:38:04 +0200
Message-id: <[🔎] 20100405103804.GP19557@mails.so.argh.org>
Mail-followup-to: Andreas Barth <aba@not.so.argh.org>, Philipp Kern <pkern@debian.org>, Stefan Fritsch <sf@debian.org>, debian-wb-team@lists.debian.org, team@security.debian.org
In-reply-to: <[🔎] 20100405101812.GA18055@kelgar.0x539.de>
References: <[🔎] 201004051131.11557.sf@debian.org> <[🔎] 20100405101812.GA18055@kelgar.0x539.de>

* Philipp Kern (pkern@debian.org) [100405 12:18]:
> https is IMHO orthogonal, this setting breaks verification of the plain archive
> instead, not just the security parts which are shipped encrypted to the buildds
> when https is used.  (OTOH the log is still transmitted unencrypted, FWIW.)

yes. If we could have "allow unauthenticated" on an per-archiv-basis
then it'd work.



Andi

Reply to:

References:
- Document correct buildd chroot setup somewhere?
  - From: Stefan Fritsch <sf@debian.org>
- Re: Document correct buildd chroot setup somewhere?
  - From: Philipp Kern <pkern@debian.org>

Prev by Date: Re: Document correct buildd chroot setup somewhere?
Next by Date: Re: Document correct buildd chroot setup somewhere?
Previous by thread: Re: Document correct buildd chroot setup somewhere?
Next by thread: Re: Document correct buildd chroot setup somewhere?
Index(es):
- Date
- Thread