From owner-freebsd-doc@FreeBSD.ORG Wed Dec 18 06:49:08 2013 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3EEEA92 for ; Wed, 18 Dec 2013 06:49:08 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B2FC21B18 for ; Wed, 18 Dec 2013 06:49:07 +0000 (UTC) Received: from [157.181.98.186] ([157.181.98.186]) by mail.gmx.com (mrgmx003) with ESMTPSA (Nemesis) id 0Mgc0l-1W7h7m3pVX-00NwEk for ; Wed, 18 Dec 2013 07:49:06 +0100 Message-ID: <52B14541.5030502@gmx.com> Date: Wed, 18 Dec 2013 07:48:33 +0100 From: dt71@gmx.com User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:23.0) Gecko/20100101 Firefox/23.0 SeaMonkey/2.20 MIME-Version: 1.0 To: freebsd-doc@freebsd.org Subject: =?UTF-8?B?4oCcV2UgY2Fubm90IHRydXN04oCdIEludGVsIGFuZCBWaWHigJlzIGM=?= =?UTF-8?B?aGlwLWJhc2VkIGNyeXB0bywgRnJlZUJTRCBkZXZlbG9wZXJzIHNheQ==?= Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:vBEnxChV4Xt7qvhA/+0SFn8f5mXEuw78/0lNCtmujqFxCMrawa5 rSHjPuwW0gMGrbdxkKN4bnwL9yLWWH3jcObbAkrHaez1X23T6iFqdpcHjLPNZyWTi6QJfFY GO4jmPBAVlAHXyCsJkjTqqli5zedGdqi1nxF37lbQmB40fY3ephu/0TFP11w4gIaCfrrWK0 BIARJhTG/9FToRTsfIraQ== X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Dec 2013 06:49:08 -0000 What happened to the link to [1] from the freebsd.org press page? [1] http://arstechnica.com/security/2013/12/we-cannot-trust-intel-and-vias-chip-based-crypto-freebsd-developers-say/