Re: golang-go.crypto / CVE-2019-11841
- To: Emilio Pozuelo Monfort <pochu@debian.org>, Utkarsh Gupta <utkarsh@debian.org>
- Cc: Ola Lundqvist <ola@inguza.com>, Debian LTS <debian-lts@lists.debian.org>
- Subject: Re: golang-go.crypto / CVE-2019-11841
- From: Brian May <bam@debian.org>
- Date: Mon, 09 Nov 2020 09:32:15 +1100
- Message-id: <[🔎] 87blg7fpjk.fsf@canidae.wired.pri>
- In-reply-to: <[🔎] 87k0v0g3y6.fsf@canidae.wired.pri>
- References: <87k0xes8kr.fsf@canidae.wired.pri> <874ko9p70k.fsf@canidae.wired.pri> <CABY6=0nbk71vcgXX3yHeKmm1kYZi=+PduFCbiyNCDx8WXDwEQA@mail.gmail.com> <871rjbq50z.fsf@canidae.wired.pri> <CABY6=0mSxsXpjhz-X+=p2wSSeXFuffVf=7X3AQ0GEyy1YRF9-A@mail.gmail.com> <87k0x2edaf.fsf@canidae.wired.pri> <CABY6=0=xDdOo1RH9iJiG=xS0T=GaQ48k+w-RSoLPSbTDcZxCUA@mail.gmail.com> <871rj6m8jr.fsf@canidae.wired.pri> <CABY6=0ku8-9tztUoYS_nU=jX_aUP_VVhyGyZefS+a3jh=tv--A@mail.gmail.com> <87a6x1ism5.fsf@canidae.wired.pri> <CAPP0f95wioPcjGJcdr5-asTvnF2Wfq-JC+fhL=7ORiKnr1P97A@mail.gmail.com> <877ds5ir5a.fsf@canidae.wired.pri> <CAPP0f95oKvN+F2mZrscoGx-Ji+=PUcGopL+HusTd47gp6oakQQ@mail.gmail.com> <87y2kjghen.fsf@canidae.wired.pri> <0f05e2e5-a26d-179f-18d4-c4abdddc5fec@debian.org> <87k0w15edd.fsf@silverfish.pri> <3722204c-542e-7be2-f4a5-49c1cfbcc472@debian.org> <87h7r55dd9.fsf@silverfish.pri> <3388c95b-f3dc-f63c-a927-453c3380c088@debian.org> <87lfgggxw5.fsf@canidae.wired.pri> <[🔎] 87k0v0g3y6.fsf@canidae.wired.pri>
Brian May <bam@debian.org> writes:
> This produced the following output to STDOUT:
>
> === cut ===
> obfs4proxy salsa20
> packer ssh/keys
> rclone salsa20
> restic ssh/keys
> snapd salsa20
> === cut ===
snapd seems to reproduce test failures, even without my security
updates. :-(
What is the process for rebuilding these in stretch LTS? Do I need to
add entries to dla-needed.txt and claim these entries?
--
Brian May <bam@debian.org>
Reply to: