From owner-freebsd-questions@FreeBSD.ORG Sat Aug 25 21:38:38 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C6D2316A41A for ; Sat, 25 Aug 2007 21:38:38 +0000 (UTC) (envelope-from martin.laabs@mailbox.tu-dresden.de) Received: from mailout2.zih.tu-dresden.de (mailout2.zih.tu-dresden.de [141.30.67.73]) by mx1.freebsd.org (Postfix) with ESMTP id 88F2B13C46C for ; Sat, 25 Aug 2007 21:38:38 +0000 (UTC) (envelope-from martin.laabs@mailbox.tu-dresden.de) Received: from rmc67-31.zih.tu-dresden.de ([141.30.67.31] helo=server-n) by mailout2.zih.tu-dresden.de with esmtp (Exim 4.63) (envelope-from ) id 1IP33R-0003n5-4j for freebsd-questions@freebsd.org; Sat, 25 Aug 2007 23:20:27 +0200 Received: from martin (pD9EB59A8.dip.t-dialin.net [217.235.89.168]) by server-n (Postfix) with ESMTP id EC587100A08E for ; Sat, 25 Aug 2007 23:20:24 +0200 (CEST) Date: Sat, 25 Aug 2007 23:25:23 +0200 To: freebsd-questions@freebsd.org From: "Martin Laabs" Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Message-ID: User-Agent: Opera Mail/9.10 (Linux) X-TUD-Virus-Scanned: mailout2.zih.tu-dresden.de Subject: secure /usr/src update X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Aug 2007 21:38:38 -0000 Hello, as far as I know neither CVSup, CTM nor (anonymous) CVS support any kind of (cryptographic) signing or encryption. Now I'd like to know if it is possible to obtain or update the base system in a secure and reliable way at all. For the ports collection there is portsnap which seems for me - in respect to the security issue - well concepted. Also, if I buy a (pressed) DVD I (hopefully) can trust the integrity of the system I install. (And with this DVD I'll receive the keyprint of portsnap on a - hopefull sufficient - secure way.) Solely the update of the /usr/src branch seems to be easily attackable by some standard stream inserting or very simple man in the middle attacks. Do you have any suggestions? Thank you, Martin Laabs