On 2018-02-13 07:22, Aurelien Jarno wrote:
> On 2018-02-01 22:17, Ansgar Burchardt wrote:
> > Philipp Kern writes:
> > > On 01.02.2018 10:30, Ansgar Burchardt wrote:
> > [...]
> > >> There is already a `buildd-uploader` role account on the upload hosts
> > >> both main and security archive, a
On 2018-02-01 20:45, Philipp Kern wrote:
> On 01.02.2018 10:30, Ansgar Burchardt wrote:
> > Hmm, another issue comes to mind:
> >
> > If we care about encrypted buildd uploads, the buildds should probably
> > also download from the (private) security-buildd archive over an
> > encrypted
On 2018-02-01 22:17, Ansgar Burchardt wrote:
> Philipp Kern writes:
> > On 01.02.2018 10:30, Ansgar Burchardt wrote:
> [...]
> >> There is already a `buildd-uploader` role account on the upload hosts
> >> both main and security archive, a `rsync-ssh-wrap` script, and someone
> >> also set up
Philipp Kern writes:
> On 01.02.2018 10:30, Ansgar Burchardt wrote:
[...]
>> There is already a `buildd-uploader` role account on the upload hosts
>> both main and security archive, a `rsync-ssh-wrap` script, and someone
>> also set up authorized_keys.
>>
>> I'm just not sure if it is already in
On 01.02.2018 10:30, Ansgar Burchardt wrote:
> Philipp Kern writes:
>> On 31.01.2018 01:11, Ansgar Burchardt wrote:
>>> I'm not sure if buildds are already configured to upload to the security
>>> archive via ssh as they do for the main archive. It might be a good
>>> idea to do so.
>>
>> What's
Philipp Kern writes:
> On 31.01.2018 01:11, Ansgar Burchardt wrote:
>> I'm not sure if buildds are already configured to upload to the security
>> archive via ssh as they do for the main archive. It might be a good
>> idea to do so.
>
> What's the requirement here? I think traditionally we use
On 31.01.2018 01:11, Ansgar Burchardt wrote:
> I'm not sure if buildds are already configured to upload to the security
> archive via ssh as they do for the main archive. It might be a good
> idea to do so.
What's the requirement here? I think traditionally we use machine-local
SSH
Kurt Roeckx writes:
> It's been a longstanding problem that the uploads to the security
> archive are not encrypted in any way. I think this is a problem
> for all embargoed uploads that we are doing.
>
> Upstream might actually do all that's possible to keep the
> security issues secret. But it
Package: ftp.debian.org,security.debian.org
It's been a longstanding problem that the uploads to the security
archive are not encrypted in any way. I think this is a problem
for all embargoed uploads that we are doing.
Upstream might actually do all that's possible to keep the
security issues
9 matches
Mail list logo
