From: Steve Grubb <sgrubb@redhat.com>
To: Linux Audit <linux-audit@redhat.com>
Subject: [RFC] Drop support for old audit rule API
Date: Fri, 27 Feb 2009 10:15:19 -0500 [thread overview]
Message-ID: <200902271015.20236.sgrubb@redhat.com> (raw)
Hi,
Another thought for the next major release is to drop support for the old
audit rules API in libaudit. A long time ago, the function prototypes for:
extern int audit_request_rules_list(int fd);
extern int audit_add_rule(int fd, struct audit_rule *rule,
int flags, int action);
extern int audit_delete_rule(int fd, struct audit_rule *rule,
int flags, int action);
extern int audit_rule_syscall(struct audit_rule *rule, int scall);
extern int audit_rule_syscallbyname(struct audit_rule *rule,
const char *scall);
extern int audit_rule_fieldpair(struct audit_rule *rule, const char *pair,
int flags);
extern void audit_rule_free(struct audit_rule *rule);
Were moved to a private internal header. This was to encourage any external
apps from using them, but if they had been previously compiled to know about
the API, they would still be able to link and run.
As far as I know, auditctl & autrace are the only apps that would be affected.
There very well may be some 3rd party apps I don't know about that this could
impact. Hopefully they are on this list or moved their function calls when
the prototype disappeared.
The proposal is to drop the above mentioned functions and bump the soname
number so that anything linking against libaudit has to be recompiled to make
sure they have no old function calls. At some point in the future, we can
also remove the kernel's support for the old rule format.
Let's discuss....
-Steve
next reply other threads:[~2009-02-27 15:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-27 15:15 Steve Grubb [this message]
2009-07-28 18:34 ` [RFC] Drop support for old audit rule API Steve Grubb
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=200902271015.20236.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--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