Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 5 Aug 2019 22:32:11 +0200 (CEST)
From:      =?UTF-8?Q?Trond_Endrest=C3=B8l?= <trond.endrestol@ximalas.info>
To:        freebsd-current@freebsd.org
Cc:        Konstantin Belousov <kostikbel@gmail.com>
Subject:   Re: r350484 and ASLR enabled - init died (signal 6, exit 0)
Message-ID:  <alpine.BSF.2.21.99999.352.1908052219550.31116@enterprise.ximalas.info>
In-Reply-To: <20190805192305.GC2731@kib.kiev.ua>
References:  <alpine.BSF.2.21.99999.352.1908051436050.31116@enterprise.ximalas.info> <20190805130255.GA1121@albert.catwhisker.org> <alpine.BSF.2.21.99999.352.1908051947580.31116@enterprise.ximalas.info> <20190805192305.GC2731@kib.kiev.ua>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 5 Aug 2019 22:23+0300, Konstantin Belousov wrote:

> On Mon, Aug 05, 2019 at 08:10:43PM +0200, Trond Endrestøl wrote:
> 
> > I'm going home and see if VBox 6.0.10 exhibits the same behaviour.
> 
> Try r350608. There was a mis-merge in the committed patch (more serious
> part), and some limits were not applied, which I did not see in my
> testing due to the mismatch between stock FreeBSD and my testing
> environment.

I'm now at r350609, and booting with ASLR enabled works in VBox.
I'll try the Citrix Hypervisor VM tomorrow

Thank you, Konstantin.

-- 
Trond.
From owner-freebsd-current@freebsd.org  Tue Aug  6 07:00:32 2019
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.nyi.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5BC8FBAEF0
 for <freebsd-current@mailman.nyi.freebsd.org>;
 Tue,  6 Aug 2019 07:00:32 +0000 (UTC)
 (envelope-from kostikbel@gmail.com)
Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3])
 by mx1.freebsd.org (Postfix) with ESMTP id 462lrw1Bvcz3FS4
 for <freebsd-current@freebsd.org>; Tue,  6 Aug 2019 07:00:32 +0000 (UTC)
 (envelope-from kostikbel@gmail.com)
Received: by mailman.nyi.freebsd.org (Postfix)
 id 2702CBAEEF; Tue,  6 Aug 2019 07:00:32 +0000 (UTC)
Delivered-To: current@mailman.nyi.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.nyi.freebsd.org (Postfix) with ESMTP id 25A60BAEEC
 for <current@mailman.nyi.freebsd.org>; Tue,  6 Aug 2019 07:00:32 +0000 (UTC)
 (envelope-from kostikbel@gmail.com)
Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 server-signature RSA-PSS (4096 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 462lrv1N5vz3FS3
 for <current@freebsd.org>; Tue,  6 Aug 2019 07:00:30 +0000 (UTC)
 (envelope-from kostikbel@gmail.com)
Received: from tom.home (kib@localhost [127.0.0.1])
 by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id x7670MBV085984
 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO);
 Tue, 6 Aug 2019 10:00:25 +0300 (EEST)
 (envelope-from kostikbel@gmail.com)
DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua x7670MBV085984
Received: (from kostik@localhost)
 by tom.home (8.15.2/8.15.2/Submit) id x7670MMw085979;
 Tue, 6 Aug 2019 10:00:22 +0300 (EEST)
 (envelope-from kostikbel@gmail.com)
X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com
 using -f
Date: Tue, 6 Aug 2019 10:00:22 +0300
From: Konstantin Belousov <kostikbel@gmail.com>
To: current@freebsd.org
Subject: NIS maps value length increase to 16m
Message-ID: <20190806070022.GE2731@kib.kiev.ua>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.12.1 (2019-06-15)
X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00,
 DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FROM,
 NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on tom.home
X-Rspamd-Queue-Id: 462lrv1N5vz3FS3
X-Spamd-Bar: -
Authentication-Results: mx1.freebsd.org; dkim=none;
 dmarc=fail reason="No valid SPF, No valid DKIM" header.from=gmail.com
 (policy=none); 
 spf=softfail (mx1.freebsd.org: 2001:470:d5e7:1::1 is neither permitted nor
 denied by domain of kostikbel@gmail.com) smtp.mailfrom=kostikbel@gmail.com
X-Spamd-Result: default: False [-1.99 / 15.00]; ARC_NA(0.00)[];
 NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; RCVD_TLS_ALL(0.00)[];
 FROM_HAS_DN(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com];
 TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain];
 TO_DN_NONE(0.00)[]; HAS_XAW(0.00)[];
 R_SPF_SOFTFAIL(0.00)[~all:c]; RCPT_COUNT_ONE(0.00)[1];
 IP_SCORE_FREEMAIL(0.00)[];
 IP_SCORE(0.00)[ip: (-2.67), ipnet: 2001:470::/32(-4.50), asn: 6939(-2.92),
 country: US(-0.05)]; NEURAL_HAM_SHORT(-0.99)[-0.995,0];
 FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[];
 MIME_TRACE(0.00)[0:+];
 ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US];
 RCVD_COUNT_TWO(0.00)[2]; FREEMAIL_ENVFROM(0.00)[gmail.com];
 DMARC_POLICY_SOFTFAIL(0.10)[gmail.com : No valid SPF, No valid DKIM,none]
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>;
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2019 07:00:32 -0000

Apparently, NIS is still in use even in large enterprise environments,
not everything was consumed by LDAP.  And there, Linux added a quirk
very long time ago, in 2013 at least, see
https://marc.info/?l=fedora-extras-commits&m=136675043230000&w=2

What they did is the increase of the longest allowed key value (and
key name) in a map, from Sun-defined 1024 to 16M.  This change is
backward-compatible, in the sense that either old NIS master or old
NIS client are protocol-compatible with the updated masters and
clients, assuming that the maps only export values limited to 1024
bytes in length.  On the other hand, a new client can use much larger
values.  This works because values are specified in yp XDR as opaque
variadic-length arrays.

An example where this is useful is the environment with very large
automount maps exported by NIS.  For obvious reasons, FreeBSD cannot
function in such settings.

I wrote the patch to bump the limit in FreeBSD NIS implementation,
both in client and in servers, see
https://reviews.freebsd.org/D20900
If you are interested in the NIS code, please review.  I want to commit
the change into HEAD in approximately two weeks from now.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.21.99999.352.1908052219550.31116>