From owner-freebsd-current@FreeBSD.ORG Sun Apr 19 22:46:07 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B705D1065670 for ; Sun, 19 Apr 2009 22:46:07 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 9007A8FC08 for ; Sun, 19 Apr 2009 22:46:07 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id 1A39946B2E; Sun, 19 Apr 2009 18:46:07 -0400 (EDT) Date: Sun, 19 Apr 2009 23:46:06 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Jakub Lach In-Reply-To: <23127561.post@talk.nabble.com> Message-ID: References: <23127561.post@talk.nabble.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: OpenBSM 1.1 imported (was: svn commit: r191273 - in head: contrib/openbsm contrib/openbsm/bin contrib/openbsm/bin/audit contrib/openbsm/bin/auditd contrib/openbsm/bin/auditfilterd contrib/openbsm/bin/auditreduce contrib/open... (fwd)) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Apr 2009 22:46:07 -0000 On Sun, 19 Apr 2009, Jakub Lach wrote: > After updating to revision 191274, I cannot login. > > "could not determine audit condition" > > Sorry for bothering you, but I don't know how to deal with it. Could you let me know: (1) Do you have options AUDIT compiled into your kernel? It's in GENERIC by default, and it occurs to me I've not tested the !AUDIT case lately. (2) How are you logging in -- using the console, or sshd, or...? Does it work better or worse if you try another way of logging in? (3) ... and could you confirm that your kernel was rebuilt and installed prior to updating userspace? If you switch to an old kernel, are you then able to log in? Robert N M Watson Computer Laboratory University of Cambridge