Audit.rules seem to be ignored
I am on Ubuntu 18.04 on x86-64.
As noted in various places, chromium generates huge numbers of audit events whenever it does just about anything:
type=SECCOMP msg=audit(1546823297.836:2406): auid=1000 uid=1000 gid=1000 ses=2 pid=4952 comm="chromium-browse" exe="/usr/lib/chromium-browser/chromium-browser" sig=0 arch=c000003e syscall=257 compat=0 ip=0x7f9607138db1 code=0x50000
This has been discussed elsewhere but there are no working solution.
What should work is to disable audit logging of chromium-browser events.
I have made a file /etc/audit/rules.d/z-chromium.rules with the contents:
-a never,exit -F exe=/usr/lib/chromium-browser/chromium-browser -S all
-a never,exit -F path=/usr/lib/chromium-browser/chromium-browser -S all
and run augenrules --load, which seems to work fine but the logging is unchanged. I have verified that the rules are loaded via auditctl -l. I have also tried manually loading the rules via auditctl. Nothing works. The events appear in both /var/log/audit/audit.log and in journald.
Is this a bug with auditd or am I missing something?
chromium
asked Jan 7 at 1:21
Jonathan GancJonathan Ganc
215
add a comment |
I am on Ubuntu 18.04 on x86-64.
As noted in various places, chromium generates huge numbers of audit events whenever it does just about anything:
type=SECCOMP msg=audit(1546823297.836:2406): auid=1000 uid=1000 gid=1000 ses=2 pid=4952 comm="chromium-browse" exe="/usr/lib/chromium-browser/chromium-browser" sig=0 arch=c000003e syscall=257 compat=0 ip=0x7f9607138db1 code=0x50000
This has been discussed elsewhere but there are no working solution.
What should work is to disable audit logging of chromium-browser events.
I have made a file /etc/audit/rules.d/z-chromium.rules with the contents:
-a never,exit -F exe=/usr/lib/chromium-browser/chromium-browser -S all
-a never,exit -F path=/usr/lib/chromium-browser/chromium-browser -S all
and run augenrules --load, which seems to work fine but the logging is unchanged. I have verified that the rules are loaded via auditctl -l. I have also tried manually loading the rules via auditctl. Nothing works. The events appear in both /var/log/audit/audit.log and in journald.
Is this a bug with auditd or am I missing something?
chromium
asked Jan 7 at 1:21
Jonathan GancJonathan Ganc
215
add a comment |
I am on Ubuntu 18.04 on x86-64.
As noted in various places, chromium generates huge numbers of audit events whenever it does just about anything:
type=SECCOMP msg=audit(1546823297.836:2406): auid=1000 uid=1000 gid=1000 ses=2 pid=4952 comm="chromium-browse" exe="/usr/lib/chromium-browser/chromium-browser" sig=0 arch=c000003e syscall=257 compat=0 ip=0x7f9607138db1 code=0x50000
This has been discussed elsewhere but there are no working solution.
What should work is to disable audit logging of chromium-browser events.
I have made a file /etc/audit/rules.d/z-chromium.rules with the contents:
-a never,exit -F exe=/usr/lib/chromium-browser/chromium-browser -S all
-a never,exit -F path=/usr/lib/chromium-browser/chromium-browser -S all
and run augenrules --load, which seems to work fine but the logging is unchanged. I have verified that the rules are loaded via auditctl -l. I have also tried manually loading the rules via auditctl. Nothing works. The events appear in both /var/log/audit/audit.log and in journald.
Is this a bug with auditd or am I missing something?
chromium
asked Jan 7 at 1:21
Jonathan GancJonathan Ganc
215
I am on Ubuntu 18.04 on x86-64.
As noted in various places, chromium generates huge numbers of audit events whenever it does just about anything:
type=SECCOMP msg=audit(1546823297.836:2406): auid=1000 uid=1000 gid=1000 ses=2 pid=4952 comm="chromium-browse" exe="/usr/lib/chromium-browser/chromium-browser" sig=0 arch=c000003e syscall=257 compat=0 ip=0x7f9607138db1 code=0x50000
This has been discussed elsewhere but there are no working solution.
What should work is to disable audit logging of chromium-browser events.
I have made a file /etc/audit/rules.d/z-chromium.rules with the contents:
-a never,exit -F exe=/usr/lib/chromium-browser/chromium-browser -S all
-a never,exit -F path=/usr/lib/chromium-browser/chromium-browser -S all
and run augenrules --load, which seems to work fine but the logging is unchanged. I have verified that the rules are loaded via auditctl -l. I have also tried manually loading the rules via auditctl. Nothing works. The events appear in both /var/log/audit/audit.log and in journald.
Is this a bug with auditd or am I missing something?
chromium
chromium
asked Jan 7 at 1:21
Jonathan GancJonathan Ganc
215
asked Jan 7 at 1:21
Jonathan GancJonathan Ganc
215
asked Jan 7 at 1:21
Jonathan GancJonathan Ganc
215
asked Jan 7 at 1:21
Jonathan GancJonathan Ganc
215
asked Jan 7 at 1:21
Jonathan GancJonathan Ganc
215
215
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1107572%2faudit-rules-seem-to-be-ignored%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1107572%2faudit-rules-seem-to-be-ignored%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
