From owner-freebsd-security Mon Jan 13 8:50:49 2003 Delivered-To: freebsd-security@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BA73537B401 for ; Mon, 13 Jan 2003 08:50:46 -0800 (PST) Received: from relay.pair.com (relay.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 878AB43F5F for ; Mon, 13 Jan 2003 08:50:40 -0800 (PST) (envelope-from njyoder@gummibears.nu) Received: (qmail 2424 invoked from network); 13 Jan 2003 16:50:34 -0000 Received: from roc-24-59-189-237.rochester.rr.com (HELO catbert) (24.59.189.237) by relay.pair.com with SMTP; 13 Jan 2003 16:50:34 -0000 X-pair-Authenticated: 24.59.189.237 Date: Mon, 13 Jan 2003 11:50:32 -0500 From: "Nathan J. Yoder" X-Mailer: The Bat! (v1.61) Educational Reply-To: "Nathan J. Yoder" X-Priority: 3 (Normal) Message-ID: <183161149721.20030113115032@gummibears.nu> To: "Jacques A. Vidrine" Cc: freebsd-security@FreeBSD.org Subject: Re: digital signatures for downloads In-Reply-To: <20030113145330.GA78337@madman.nectar.cc> References: <6121584208.20030113005107@gummibears.nu> <20030113145330.GA78337@madman.nectar.cc> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Monday, January 13, 2003, 9:53:30 AM, Jacques A. Vidrine wrote: > Patches are also signed. For example, from the latest advisory: Right, my mistake. Anyway, someone pointed out to me that this discussion had been done 2 years ago and gave me this link: http://razor.bindview.com/publish/papers/os-patch.html . There is section on FreeBSD in the middle. I'm reading up further on SFSRO : http://www.fs.net/sfs/@new-york.lcs.mit.edu,u83s4uk49nt8rmp4uwmt2exvz6d3cavh/pub/sfswww/ With this new information I'll see what I can do to help. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message