From owner-freebsd-security@FreeBSD.ORG  Tue Jan 28 12:32:20 2014
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Delivered-To: freebsd-security@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 CDD0068F
 for <freebsd-security@freebsd.org>; Tue, 28 Jan 2014 12:32:20 +0000 (UTC)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com
 [66.111.4.28])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 9D9BE185D
 for <freebsd-security@freebsd.org>; Tue, 28 Jan 2014 12:32:20 +0000 (UTC)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44])
 by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 32A9620EF9
 for <freebsd-security@freebsd.org>; Tue, 28 Jan 2014 07:32:19 -0500 (EST)
Received: from web3 ([10.202.2.213])
 by compute4.internal (MEProxy); Tue, 28 Jan 2014 07:32:19 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=
 messagingengine.com; h=message-id:from:to:mime-version
 :content-transfer-encoding:content-type:in-reply-to:references
 :subject:date; s=smtpout; bh=CAYNhen4h7dN9ZG/86iRmWcW6+M=; b=sGa
 Pf/Xo5Ru+ng1MrWFaF//aczLsrJGkMg+TZTYpTuteNoKlFOf5fnTQFyzH7TSVK4R
 z9pzHLRdbNV/y8ulOixh6XZ2rFABgEnHQ1J/U7bDMRe2wAuWXDHb3BfA/ghU7tPR
 SpZJlsnnE2HfWEU0rFUGmkiMS4eHl4TvmHOZuSZI=
Received: by web3.nyi.mail.srv.osa (Postfix, from userid 99)
 id 11CB710709F; Tue, 28 Jan 2014 07:32:19 -0500 (EST)
Message-Id: <1390912339.18287.76258365.0317802C@webmail.messagingengine.com>
X-Sasl-Enc: ODOanWMo93kq7aBCP5NbISjjk4QyaGCeAgkcvCmR9JAV 1390912339
From: Mark Felder <feld@FreeBSD.org>
To: freebsd-security@freebsd.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
X-Mailer: MessagingEngine.com Webmail Interface - ajax-1b692d69
In-Reply-To: <D5AFDA9E-4BC0-4E2A-8986-FD4283CEE918@elstel.org>
References: <4BA27CDF.1040107@gmail.com>
 <D5AFDA9E-4BC0-4E2A-8986-FD4283CEE918@elstel.org>
Subject: Re: online cheksum verification for FreeBSD
Date: Tue, 28 Jan 2014 06:32:19 -0600
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Security issues \[members-only posting\]"
 <freebsd-security.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-security/>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Help: <mailto:freebsd-security-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 12:32:20 -0000

On Mon, Jan 27, 2014, at 22:41, Elmar Stellnberger wrote:
>  However locally stored
> checksums are not of use as they can
> be manipulated arbitrarily.
> 

This shouldn't be a concern when using signed packages, correct? Or if
that's still a problem couldn't we just teach `pkg check` to confirm
signature of the repository matches before verifying checksums?