From owner-freebsd-current@freebsd.org Thu Jan 4 14:26:41 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8701EEB80A4 for ; Thu, 4 Jan 2018 14:26:41 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from dec.sakura.ne.jp (dec.sakura.ne.jp [210.188.226.8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 26DCC6BA0A for ; Thu, 4 Jan 2018 14:26:40 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from fortune.joker.local (124-18-70-98.dz.commufa.jp [124.18.70.98]) (authenticated bits=0) by dec.sakura.ne.jp (8.15.2/8.15.2/[SAKURA-WEB]/20080708) with ESMTPA id w04EQVDc047310 for ; Thu, 4 Jan 2018 23:26:32 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Thu, 4 Jan 2018 23:26:31 +0900 From: Tomoaki AOKI To: freebsd-current@freebsd.org Subject: Re: Intel CPU design flaw - FreeBSD affected? Message-Id: <20180104232631.3d163448d7ac2a3bc82fe5af@dec.sakura.ne.jp> In-Reply-To: References: <9dda0496-be16-35c6-6c45-63d03b218ccb@protected-networks.net> Organization: Junchoon corps X-Mailer: Sylpheed 3.6.0 (GTK+ 2.24.31; amd64-portbld-freebsd11.1) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit 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: Thu, 04 Jan 2018 14:26:41 -0000 And now official announcement from Intel... https://security-center.intel.com/advisory.aspx?intelid=INTEL-SA-00088&languageid=en-fr On Wed, 3 Jan 2018 19:51:40 -0500 Mark Heily wrote: > On Jan 2, 2018 19:05, "Warner Losh" wrote: > > The register article says the specifics are under embargo still. That would > make it hard for anybody working with Intel to comment publicly on the flaw > and any mitigations that may be underway. It would be unwise to assume that > all the details are out until the embargo lifts. > > > Details of the flaws are now published at: > > https://meltdownattack.com > > > Warner > > On Jan 2, 2018 4:13 PM, "Michael Butler" wrote: > > > Has any impact assessment been made as to FreeBSD's exposure or > > mitigation strategies? > > > > 'Kernel memory leaking' Intel processor design flaw forces Linux, > > Windows redesign - The Register > > > > Other OSes will need an update, performance hits loom A fundamental > > design flaw in Intel's processor chips has forced a significant redesign > > of the Linux and Windows kernels to defang the chip-level security bug.… > > Programmers are scrambling to overhaul the open-source Linux kernel's > > virtual memory system. Meanwhile, Microsoft is expected to publicly > > introduce necessary changes to its Windows operating system in this > > month's Patch Tuesday ... > > > > https://www.theregister.co.uk/2018/01/02/intel_cpu_design_flaw/ > > > > imb > > > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > -- Tomoaki AOKI