Linux-audit Archive mirror
 help / color / mirror / Atom feed
From: "Wieprecht, Karen M." <Karen.Wieprecht@jhuapl.edu>
To: "linux-audit@redhat.com" <linux-audit@redhat.com>
Subject: 128 Character limit on proctitle field?
Date: Fri, 15 Sep 2023 16:15:12 +0000	[thread overview]
Message-ID: <f04d10f4d94c4c2295031fee26dc8082@jhuapl.edu> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 970 bytes --]

All,

We're working with Docker and podman, and I'm working on parsing the audit data we get to flag prohibited and missing command options based on STIG guidelines.   I normally extract the proctitle from the raw auditd data , but these commands are very long with sometimes 23 or more command line parameters ,  and I noticed that all of the auditd proctitle data for the lengthier commands is being cut off at 128 characters.

I'm bringing this up  for two reasons:

     One,  not everyone working with this data may realize that there seems to be a character limit,
     and second, if this is by chance a bug as opposed to intentional,  then I'm hoping we can get a fix cooking for it?

In the meantime,  I may be able to work around this by piecing together the full command from the "a#= "  fields, but it would be much easier if proctitle wasn't cut off after 128 chars.

Thanks, any info you can share would be much appreciated,

Karen Wieprecht

[-- Attachment #1.2: Type: text/html, Size: 3297 bytes --]

[-- Attachment #2: Type: text/plain, Size: 107 bytes --]

--
Linux-audit mailing list
Linux-audit@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-audit

             reply	other threads:[~2023-09-15 16:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-15 16:15 Wieprecht, Karen M. [this message]
2023-09-18  2:38 ` 128 Character limit on proctitle field? Tetsuo Handa
2023-09-19 23:32 ` Steve Grubb
2023-09-20 18:11   ` [EXT] " Wieprecht, Karen M.

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f04d10f4d94c4c2295031fee26dc8082@jhuapl.edu \
    --to=karen.wieprecht@jhuapl.edu \
    --cc=linux-audit@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).