From owner-freebsd-security@FreeBSD.ORG  Mon Sep  3 17:15:50 2012
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Delivered-To: freebsd-security@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 6E6EA1065674;
	Mon,  3 Sep 2012 17:15:50 +0000 (UTC)
	(envelope-from arthurmesh@gmail.com)
Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com
	[209.85.160.54])
	by mx1.freebsd.org (Postfix) with ESMTP id 2531A8FC0C;
	Mon,  3 Sep 2012 17:15:50 +0000 (UTC)
Received: by pbbrp2 with SMTP id rp2so8254772pbb.13
	for <multiple recipients>; Mon, 03 Sep 2012 10:15:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=date:from:to:cc:subject:message-id:references:mime-version
	:content-type:content-disposition:in-reply-to:user-agent;
	bh=8vlEnwdQBZeMBCNCq88D/Kj40Xe9YUI9ScoTbs1wmps=;
	b=Nb/2Zjhlv96ocHGGVZWVUk+DspC21LeCCW+y3oeyQ+iBcpiuqgi6gN1+oFV/IrbC1d
	PiJazy9bYSyV3hibRaNKmMfABtUszlnM9p9NKE6bRkCMJWbtOilgLoIMiaZRULoBk7qQ
	jT8FYLqGh0bBm+hdhJaoGcCMB/fhl1ifmychOPaSQZ2bZ4h03EWoTNdOUNxxp+Pb6MYe
	TXQEp5XPyB6JVq1wnOjdOEIJ8Oc+NFBiQGUY7UAqb4wxOwy43OOB7uhSskylY7Gp/N3g
	Ut9ZXdFdvkVtmZvoThNFtP04MJim20lfb4ZlCX/5jV1r1rVuiLEJ0oTQRen67XF/QA8z
	u6Hw==
Received: by 10.68.242.231 with SMTP id wt7mr39195290pbc.99.1346692544022;
	Mon, 03 Sep 2012 10:15:44 -0700 (PDT)
Received: from x96.org (x96.org. [64.85.165.177])
	by mx.google.com with ESMTPS id qw6sm10286698pbc.26.2012.09.03.10.15.40
	(version=SSLv3 cipher=OTHER); Mon, 03 Sep 2012 10:15:42 -0700 (PDT)
Date: Mon, 3 Sep 2012 10:15:38 -0700
From: Arthur Mesh <arthurmesh@gmail.com>
To: Doug Barton <dougb@FreeBSD.org>
Message-ID: <20120903171538.GM1464@x96.org>
References: <201208221843.q7MIhLU4077951@svn.freebsd.org>
	<5043DBAF.40506@FreeBSD.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5043DBAF.40506@FreeBSD.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Mailman-Approved-At: Mon, 03 Sep 2012 17:30:00 +0000
Cc: freebsd-security@FreeBSD.org, freebsd-rc@FreeBSD.org,
	Mark Murray <markm@FreeBSD.org>, "David E. O'Brien" <obrien@FreeBSD.org>
Subject: Re: svn commit: r239569 - head/etc/rc.d
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Security issues \[members-only posting\]"
	<freebsd-security.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/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: Mon, 03 Sep 2012 17:15:50 -0000

Doug,

On Sun, Sep 02, 2012 at 03:20:31PM -0700, Doug Barton wrote:
> In the third case, the system boots, but is then rebooted again before
> the cron interval has had a chance to replace even 1 file. This is the
> case where removing the old entropy is particularly pathological. It

I believe you're missing the point that we don't just cleanup old
entropy file -- we re-generate it via "/etc/rc.d/random fastsaveseed" call in
postrandom_start()

> > +extra_commands="saveseed"
> > +saveseed_cmd="${name}_stop"
> 
> I don't understand the need for this.

That's how "/etc/rc.d/random fastsaveseed" translates in to "/etc/rc.d/random
stop", which does the jobs of re-generating seed file.

In the end, assuming machine boots up passed postrandom script, we're left with
no stale seed files, but a freshly generated ${entropy_file_confirmed}, which
should be sufficient to seed next bootup.

Thanks