From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-11.5 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4CE5BC4320A for ; Thu, 29 Jul 2021 16:25:32 +0000 (UTC) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id DE1116023F for ; Thu, 29 Jul 2021 16:25:31 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org DE1116023F Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=redhat.com Authentication-Results: mail.kernel.org; spf=tempfail smtp.mailfrom=redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1627575930; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post; bh=7QSYqZASb46gcvRLfJW2cnne/DjO+SZdaDCc/w+kovg=; b=Bykx5eRWwEpHgX/iYE8wCiqUxBiSFpIfc0wQuFiIE9UvVsYPVidjVkEfSpW+uoclOedDk8 sHU5hdV8n1l+9bYRlIkG+8KGAoaEt/Kf0gW5oicVqgDk7/3SzhkM1J7iS29EtEgdul2vp4 93NBvL9MG3yZ2P9rY3z8Ft2uz67yf0I= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-376-iTeXJzkjO8aNcTzBZixa9A-1; Thu, 29 Jul 2021 12:19:06 -0400 X-MC-Unique: iTeXJzkjO8aNcTzBZixa9A-1 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id BBFAF801AE7; Thu, 29 Jul 2021 16:19:02 +0000 (UTC) Received: from colo-mx.corp.redhat.com (colo-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.20]) by smtp.corp.redhat.com (Postfix) with ESMTPS id E0A1960875; Thu, 29 Jul 2021 16:19:01 +0000 (UTC) Received: from lists01.pubmisc.prod.ext.phx2.redhat.com (lists01.pubmisc.prod.ext.phx2.redhat.com [10.5.19.33]) by colo-mx.corp.redhat.com (Postfix) with ESMTP id 09F45180B7A2; Thu, 29 Jul 2021 16:19:00 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) by lists01.pubmisc.prod.ext.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id 16TGIvXF010553 for ; Thu, 29 Jul 2021 12:18:57 -0400 Received: by smtp.corp.redhat.com (Postfix) id BFE7B69FAD; Thu, 29 Jul 2021 16:18:57 +0000 (UTC) Received: from x2.localnet (ovpn-113-231.phx2.redhat.com [10.3.113.231]) by smtp.corp.redhat.com (Postfix) with ESMTP id 42C2419811; Thu, 29 Jul 2021 16:18:53 +0000 (UTC) From: Steve Grubb To: "linux-audit@redhat.com" , Rakesh Kumar Subject: Re: auditd not logging proper log. Date: Thu, 29 Jul 2021 12:18:53 -0400 Message-ID: <2108221.irdbgypaU6@x2> Organization: Red Hat In-Reply-To: <293734062.1021895.1627546756090@mail.yahoo.com> References: <94614270.1103019.1625898535256.ref@mail.yahoo.com> <4673895.31r3eYUQgx@x2> <293734062.1021895.1627546756090@mail.yahoo.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 X-loop: linux-audit@redhat.com X-BeenThere: linux-audit@redhat.com X-Mailman-Version: 2.1.12 Precedence: junk List-Id: Linux Audit Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=linux-audit-bounces@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit On Thursday, July 29, 2021 4:19:16 AM EDT Rakesh Kumar wrote: > I did not get you, in kernel auditd is enabled like kauditd is running then > what exactly we have to do changes in my system to get full login n log > out info in audit. Log file. Logging in/out is done in 2 places. First, pam records what it knows. But the entry point daemon is also supposed to send USER_LOGIN and USER_LOGOUT events. Complete information is here: https://github.com/linux-audit/audit-documentation/wiki/SPEC-User-Login-Lifecycle-Events Gdm, Kdm, and sshd all have been updated to record these events. All that is needed is to configure --with-audit during the package build. By now, I would expect all distros to do that. -Steve > On Sat, Jul 10, 2021 at 19:57, Steve Grubb wrote: On Saturday, July 10, 2021 2:28:55 AM EDT Rakesh Kumar wrote: > > 1)I am trying to run the auditd (start/stop) without root user as normal > > user , how to achieve this on linux.? > > For security reasons, this is not allowed. > > > 2)i am using kernel version 4.19.97 and i am not getting any > > login/logout, > > authentication fail/pass log data in audit.log file. DOes it need any > > changes in the config or rules.. > > This is hardwired into pam. The rules don't matter. I'd check that pam was > compiled with audit support and that audit is enabled in the kernel. > > -Steve -- Linux-audit mailing list Linux-audit@redhat.com https://listman.redhat.com/mailman/listinfo/linux-audit