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=-6.5 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no 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 D3540C4338F for ; Wed, 4 Aug 2021 20:06:09 +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 6AA4560187 for ; Wed, 4 Aug 2021 20:06:09 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 6AA4560187 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=1628107568; 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=grxyOGxdj9fxIanXnn2lx+b/Zooxjb6fGi32iILJhAQ=; b=NyGomBsIWLKNjPWb7yJ4cjFIp9R1BX8HIZ8LDgcMS0W82yctSeW/T4X1CYuzVK4OG3uS6y 6LAfLo/uAanGaoVJf0zt03JBw+7Nh/jAY0lZ+BnmZj2VpBr4HyFuE0YPuJ4ccH6cP2/KM4 a7JT6N8RHD1lNYtvFaVLZ/hudQv08Lw= 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-584--Wluggv7O1yxIIa0bj9Efw-1; Wed, 04 Aug 2021 16:06:07 -0400 X-MC-Unique: -Wluggv7O1yxIIa0bj9Efw-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 D981518C89CF; Wed, 4 Aug 2021 20:06:03 +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 4AF3C781EA; Wed, 4 Aug 2021 20:06:03 +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 AEC8118095C2; Wed, 4 Aug 2021 20:06:01 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) by lists01.pubmisc.prod.ext.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id 174K2uUs027792 for ; Wed, 4 Aug 2021 16:02:56 -0400 Received: by smtp.corp.redhat.com (Postfix) id E70EF5C3E0; Wed, 4 Aug 2021 20:02:56 +0000 (UTC) Received: from x2.localnet (unknown [10.22.9.50]) by smtp.corp.redhat.com (Postfix) with ESMTP id A12EE5C1B4; Wed, 4 Aug 2021 20:02:52 +0000 (UTC) From: Steve Grubb To: Linux Audit Subject: Re: last restart of auditd - in EPOCH time Date: Wed, 04 Aug 2021 16:02:51 -0400 Message-ID: <2791176.e9J7NaK4W3@x2> Organization: Red Hat In-Reply-To: References: MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 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 Hello, On Wednesday, August 4, 2021 3:25:40 PM EDT warron.french wrote: > Is there a hidden switch option to auditctl that would tell me the last > time auditd was restart specifically in epoch (down to the second)? Not auditctl, but maybe ausearch: ausearch --start boot -m daemon_start -i Or... systemctl status auditd.service | grep Active And if you need this in the epoch: date --date="$(systemctl status auditd.service|grep Active|awk '{printf "%s %s", $6, $7}')" +"%s" > If my rules are changed to non-immutable ( -e 1 ) rebooted, and then > changed back to immutable ( -e 2 ), then I discover this weeks later, then > I will not know for sure which was most recently updated/restarted. That might be one issue with using ausearch...it might have scrolled away. Maybe this could be collected at start and printed as part of the auditd state report? I could see this being useful information for various reasons. > That is the reason for the question. I am doing this for a hardening > script that will tell me based on known recent changes (as of script > execution), but I cannot properly/successfully assess for dates outside of > a day or so. :-/ systemctl should be able to get you the info you need. I might add this info to the state report, though. -Steve -- Linux-audit mailing list Linux-audit@redhat.com https://listman.redhat.com/mailman/listinfo/linux-audit