From owner-freebsd-security@freebsd.org  Mon Oct  8 13:58:11 2018
Return-Path: <owner-freebsd-security@freebsd.org>
Delivered-To: freebsd-security@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9D85F10BFF23
 for <freebsd-security@mailman.ysv.freebsd.org>;
 Mon,  8 Oct 2018 13:58:11 +0000 (UTC) (envelope-from des@des.no)
Received: from smtp.des.no (smtp.des.no [194.63.250.102])
 by mx1.freebsd.org (Postfix) with ESMTP id 384978B6D2
 for <freebsd-security@freebsd.org>; Mon,  8 Oct 2018 13:58:11 +0000 (UTC)
 (envelope-from des@des.no)
Received: from next.des.no (smtp.des.no [194.63.250.102])
 by smtp.des.no (Postfix) with ESMTP id F172086B9;
 Mon,  8 Oct 2018 13:58:09 +0000 (UTC)
Received: by next.des.no (Postfix, from userid 1001)
 id A11E0B6B8; Mon,  8 Oct 2018 15:58:10 +0200 (CEST)
From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no>
To: Konstantin Belousov <kostikbel@gmail.com>
Cc: freebsd-security@freebsd.org
Subject: Re: [FreeBSD-Announce] FreeBSD Security Advisory FreeBSD-SA-18:12.elf
In-Reply-To: <20181008112032.GJ5335@kib.kiev.ua> (Konstantin Belousov's
 message of "Mon, 8 Oct 2018 14:20:32 +0300")
References: <20180912054309.61C6B13269@freefall.freebsd.org>
 <20181006173525.GC813@lena.kiev> <20181006182104.GS5335@kib.kiev.ua>
 <86sh1hs81t.fsf@next.des.no> <20181007224611.GI5335@kib.kiev.ua>
 <86pnwkhhzm.fsf@next.des.no> <20181008112032.GJ5335@kib.kiev.ua>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (berkeley-unix)
Date: Mon, 08 Oct 2018 15:58:10 +0200
Message-ID: <86lg78h765.fsf@next.des.no>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: "Security issues \[members-only posting\]"
 <freebsd-security.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-security/>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Help: <mailto:freebsd-security-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Oct 2018 13:58:11 -0000

Konstantin Belousov <kostikbel@gmail.com> writes:
> Dag-Erling Sm=C3=B8rgrav <des@des.no> writes:
> > Ah, I see.  The port used sed to edit the file in-place instead of using
> > a tool that understands Elf and would have adjusted the section length.
> Really this cannot be done, as well as overriding the interpreter name
> with the longer string, since other segments are not movable.

If there is sufficient padding, it could use some of that, and adjust
the length so the binary is still valid.

But none of this matters, since the linux_base ports provide ld-lsb.so.3
and the sed hack has been removed...

DES
--=20
Dag-Erling Sm=C3=B8rgrav - des@des.no