From owner-freebsd-current@freebsd.org Tue Apr 17 23:43:27 2018 Return-Path: Delivered-To: freebsd-current@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 328BFFA5A87 for ; Tue, 17 Apr 2018 23:43:27 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: from mail-wr0-x233.google.com (mail-wr0-x233.google.com [IPv6:2a00:1450:400c:c0c::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A46AE810B0 for ; Tue, 17 Apr 2018 23:43:26 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: by mail-wr0-x233.google.com with SMTP id v24so22869223wra.8 for ; Tue, 17 Apr 2018 16:43:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardenedbsd-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=oCA0MPy4yzbhTIhU5OXiSfPFcXRpVCszrT9VXaJQL9w=; b=ndjSLwajvGOw7w4ZOjY/+EhLlXB8ynBRke7xkWQvou+hbQoEPMCB4D5Tuw0Nbg+rkd AO0C1glmxhaApvDCkGgUDlnB1YQLLZA1FMzvcyoBGk5gvYxVNlsoG7zY/VHw/ucGDw0V fn5RFTjQQyIbn7Bv14Tm6uEdsl9TbwoaZRNA+/5VaawNfrOVbYi5IIewQRtkNJG+KHLX zLzH+b3xFCxHeCrZBlAYs+KiRPFm/sio+FEGcJw5PzDsw6oXZiEAMW2YVP3KTJOEeOYW t0bgiY5Uzt94aEIqRJxRjtRQdg2dHPZmbN+TxS2zMr5SsihJIjJ8pZKTeefMLscJaHTK 8NsA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=oCA0MPy4yzbhTIhU5OXiSfPFcXRpVCszrT9VXaJQL9w=; b=rBQyw/DlE6UkvDSNnOc2sobX1hE+UeUzVvIfWzD7bU9HlAMMcNT8vtASQjrYcDUVeI +bsx2iQ8lx0lGiuQZGxsmsTeMv84CbE96Q0huQi1AIkAyxvz8dtXUoHmEjP1ibZ0dmsj uim0zAwobJlu/7rA19ZVB2hBuVUplpuv53WbE/BLBH7FLlDIwCyHzohgWa76MncdKOh1 LiLRrl4JcDQUsSpQyw8wNiyRNTs9IFWqO5RldQPM5W2+vHhlbfweQ9+NM0g2vOu+2QlE xSbwtt2rtAXMvbBTOy1iu2LanY7mMy6PQECJk7WYVHTLp3fkquA1hhVf823Xmsr+Q/vG /neA== X-Gm-Message-State: ALQs6tBM01FWhODsnZOqK3T5Cyi1C8BwPZqLIbJ6AwfUdgqoejCNZAhc N3rZAPNSdaKM8k58vwCwfzfBc7268gg= X-Google-Smtp-Source: AIpwx4+Qiv/mL1TQqA8l8P9mHUadzSXUY8nHH4nxtxQ0S+VmnnIwDW6s/0HapV9gQ/Z+aOw2+LBz3A== X-Received: by 10.28.24.76 with SMTP id 73mr139056wmy.24.1524008604880; Tue, 17 Apr 2018 16:43:24 -0700 (PDT) Received: from mutt-hbsd ([192.36.27.7]) by smtp.gmail.com with ESMTPSA id 64sm406079wmb.2.2018.04.17.16.43.22 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 17 Apr 2018 16:43:23 -0700 (PDT) Date: Tue, 17 Apr 2018 19:43:16 -0400 From: Shawn Webb To: Beeblebrox Cc: FreeBSD Current Subject: Re: snapshot of april 12th wont boot at all Message-ID: <20180417234316.gaoyz6kix26m4rez@mutt-hbsd> References: <20180417104700.4d6110b9@rsbsd.rsb.ber> <20180417145040.w4cqluxeozg2nubw@mutt-hbsd> <20180417111342.287459ed@rsbsd.rsb.ber> <20180417151701.gxwj4b2oh3eisd73@mutt-hbsd> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="zu4bu3hgw34zvrtm" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD mutt-hbsd 12.0-CURRENT FreeBSD 12.0-CURRENT X-PGP-Key: http://pgp.mit.edu/pks/lookup?op=vindex&search=0x6A84658F52456EEE User-Agent: NeoMutt/20171215 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Apr 2018 23:43:27 -0000 --zu4bu3hgw34zvrtm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 17, 2018 at 10:52:40PM +0000, Beeblebrox wrote: > My proposed plan did not work anyway, as both MINIMAL and GENERIC fail to= build. > I'll have to clone the FreeBSD repo unless Shawn has something to comment= on this. Due to our changing of certain kernel structures, GENERIC likely won't build anymore. FreeBSD's kernel source code contains compile-time assertions that detect when offsets of values within certain key structures are different than expected (example commit f9f820f2e418f9b68f9d94631171135bfb79989f in hardened/current/master). I'm unsure why PTI causes issues in these cases. I would love to attempt to make an effort to debug it myself, but I would need some way to replicate the issue on my end. Thanks, --=20 Shawn Webb Cofounder and Security Engineer HardenedBSD Tor-ified Signal: +1 443-546-8752 Tor+XMPP+OTR: lattera@is.a.hacker.sx GPG Key ID: 0x6A84658F52456EEE GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 6EEE --zu4bu3hgw34zvrtm Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEKrq2ve9q9Ia+iT2eaoRlj1JFbu4FAlrWhpAACgkQaoRlj1JF bu6z9w/+K6dL78fcZXW9GMwTCkBL29U/nNXDi9/ASlzSFSm5TOrI0eF1bjYEZAep TE35PrrfYMWdovACMDZUC1PiC3JKr4oa97c5l7KLgIckshoGYbpFTTJ5upPImjXe 3McVuxL+j3/+x2HkR5pYr8uwXsTB+4G0oj1o6p37+BKP8ZmvE7qE4EecU0hdfoc1 MvEOiHacDUH6b+2hwI6udDZQEf8EjJW2d2j9X0yrT/OyJTBwkLUlPV+YeFw6SQTx mmqeHDxExLtRj0GsRnSWOPprXBRgyvfxiJfLHkp08yLfhm0/aGRlt5CTcOtY3h/J PkosJ2MHy4gst5AXoW9mnW8MldVf4HDOlGSdY1pTZjhyXcgDHRRfY0mw2gengHA5 1Xc9x98UoZC//HIlVX7IfAakHROx0mVBTbRexLvnw0AuZNN084IR535K/jsXjAi4 /C9S7Em86i3wWdA7zF/B5lwjs/ObTBVMXDw0Hh+xEyAy4LXeKc3ZpAM4Uy/jQp+m decMH7rQnpCizpBljX3Es9vwj94m3e0KkXF4ZHPv/YN8shfKnQ9G4tNI22zO5n+H tnmZoPizwZ42XuDKZBo4JutJG5nMs1szNBLr4Y0+4XtJs8yxZY71YvEuC5suQFuP Iun4yH/VUxyS5EvItTCOovNWY753CTyci+Twgrbydoz+pe7H5q0= =d7ZF -----END PGP SIGNATURE----- --zu4bu3hgw34zvrtm--