From nobody Thu Sep 09 14:52:33 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id A434817A95AC for ; Thu, 9 Sep 2021 14:52:36 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4H526X4NNRz4lCY; Thu, 9 Sep 2021 14:52:36 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from aniel.nours.eu (nours.eu [IPv6:2001:41d0:8:3a4d::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: bapt) by smtp.freebsd.org (Postfix) with ESMTPSA id 6325726AB4; Thu, 9 Sep 2021 14:52:36 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: by aniel.nours.eu (Postfix, from userid 1001) id D9D2AB3F31; Thu, 9 Sep 2021 16:52:33 +0200 (CEST) Date: Thu, 9 Sep 2021 16:52:33 +0200 From: Baptiste Daroussin To: Stefan Esser Cc: FreeBSD CURRENT Subject: Re: fetch -v error output broken? Message-ID: <20210909145233.bx5yp3ghj2qaadbb@aniel.nours.eu> References: List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam: Yes X-ThisMailContainsUnwantedMimeParts: N On Thu, Sep 09, 2021 at 04:00:39PM +0200, Stefan Esser wrote: > I have just opened PR 258387 for this issue, which occurred during testing > of a port with invalid MASTER_SITE. > > The error output of "fetch -v" should be server messages, but it appears that > the buffer gets overwritten with data of unknown origin (mostly NUL bytes), e.g.: > I figured the same this morning and fixed it in: 635eb7ac799 Best regards, Bapt