From owner-freebsd-security@freebsd.org  Wed Feb 24 06:18:35 2016
Return-Path: <owner-freebsd-security@freebsd.org>
Delivered-To: freebsd-security@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 49D5BAB0F2C
 for <freebsd-security@mailman.ysv.freebsd.org>;
 Wed, 24 Feb 2016 06:18:35 +0000 (UTC)
 (envelope-from mgrooms@shrew.net)
Received: from mx2.shrew.net (mx2.shrew.net [38.97.5.132])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 23AC61BA0
 for <freebsd-security@freebsd.org>; Wed, 24 Feb 2016 06:18:34 +0000 (UTC)
 (envelope-from mgrooms@shrew.net)
Received: from mail.shrew.net (mail.shrew.prv [10.24.10.20])
 by mx2.shrew.net (8.14.7/8.14.7) with ESMTP id u1O6ATvQ057019
 for <freebsd-security@freebsd.org>; Wed, 24 Feb 2016 00:10:29 -0600 (CST)
 (envelope-from mgrooms@shrew.net)
Received: from [10.22.200.30] (unknown [136.62.17.204])
 by mail.shrew.net (Postfix) with ESMTPSA id 8415218A794
 for <freebsd-security@freebsd.org>; Wed, 24 Feb 2016 00:10:18 -0600 (CST)
Subject: Re: verify FreeBSD installation
To: freebsd-security@freebsd.org
References: <56CD2EE3.5080009@gmail.com>
From: Matthew Grooms <mgrooms@shrew.net>
Message-ID: <56CD49F6.8050907@shrew.net>
Date: Wed, 24 Feb 2016 00:13:10 -0600
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <56CD2EE3.5080009@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3
 (mx2.shrew.net [10.24.10.11]); Wed, 24 Feb 2016 00:10:29 -0600 (CST)
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: "Security issues \[members-only posting\]"
 <freebsd-security.freebsd.org>
List-Unsubscribe: <https://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: <https://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Feb 2016 06:18:35 -0000

On 2/23/2016 10:17 PM, Robert Ayrapetyan wrote:
> Hi. Is there any reliable way to verify checksums of all local files 
> for some FreeBSD installation? E.g. I'm using a hoster which provides 
> pre-deployed FreeBSD instances, how can I be sure there are no any 
> patches\changes in a kernel\services etc? Does FreeBSD provides any 
> automated tools for such kind of a verification? Thanks.

IYou can try freebsd-update with the IDS option. Have a look at the man 
page for details.

-Matthew