Is it safe to remove read rights from all /var/log files for others?
up vote
0
down vote
favorite
Am I supposed to be able to revoke read access recursively to /var/log/
for others
or will it break some applications which rely on being able to read from /var/log/
with other
rights?
linux logging access-control
add a comment |
up vote
0
down vote
favorite
Am I supposed to be able to revoke read access recursively to /var/log/
for others
or will it break some applications which rely on being able to read from /var/log/
with other
rights?
linux logging access-control
What applications do you have installed that read /var/log as another user?
– Ramhound
Nov 22 at 16:09
@Ramhound That basically is the question. Are application developers required to gain the necessary privileges to read from /var/log/* or is it normal to expect to be able to read from /var/log/* with the other privilege?
– Senkaku
Nov 22 at 16:24
What is preventing you from trying your idea?
– Ramhound
Nov 22 at 16:34
@Ramhound Some application could fail silently. I guess I will do it anyway and report here later.
– Senkaku
Nov 22 at 16:36
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Am I supposed to be able to revoke read access recursively to /var/log/
for others
or will it break some applications which rely on being able to read from /var/log/
with other
rights?
linux logging access-control
Am I supposed to be able to revoke read access recursively to /var/log/
for others
or will it break some applications which rely on being able to read from /var/log/
with other
rights?
linux logging access-control
linux logging access-control
edited Nov 22 at 16:23
harrymc
248k10257548
248k10257548
asked Nov 22 at 15:31
Senkaku
3141315
3141315
What applications do you have installed that read /var/log as another user?
– Ramhound
Nov 22 at 16:09
@Ramhound That basically is the question. Are application developers required to gain the necessary privileges to read from /var/log/* or is it normal to expect to be able to read from /var/log/* with the other privilege?
– Senkaku
Nov 22 at 16:24
What is preventing you from trying your idea?
– Ramhound
Nov 22 at 16:34
@Ramhound Some application could fail silently. I guess I will do it anyway and report here later.
– Senkaku
Nov 22 at 16:36
add a comment |
What applications do you have installed that read /var/log as another user?
– Ramhound
Nov 22 at 16:09
@Ramhound That basically is the question. Are application developers required to gain the necessary privileges to read from /var/log/* or is it normal to expect to be able to read from /var/log/* with the other privilege?
– Senkaku
Nov 22 at 16:24
What is preventing you from trying your idea?
– Ramhound
Nov 22 at 16:34
@Ramhound Some application could fail silently. I guess I will do it anyway and report here later.
– Senkaku
Nov 22 at 16:36
What applications do you have installed that read /var/log as another user?
– Ramhound
Nov 22 at 16:09
What applications do you have installed that read /var/log as another user?
– Ramhound
Nov 22 at 16:09
@Ramhound That basically is the question. Are application developers required to gain the necessary privileges to read from /var/log/* or is it normal to expect to be able to read from /var/log/* with the other privilege?
– Senkaku
Nov 22 at 16:24
@Ramhound That basically is the question. Are application developers required to gain the necessary privileges to read from /var/log/* or is it normal to expect to be able to read from /var/log/* with the other privilege?
– Senkaku
Nov 22 at 16:24
What is preventing you from trying your idea?
– Ramhound
Nov 22 at 16:34
What is preventing you from trying your idea?
– Ramhound
Nov 22 at 16:34
@Ramhound Some application could fail silently. I guess I will do it anyway and report here later.
– Senkaku
Nov 22 at 16:36
@Ramhound Some application could fail silently. I guess I will do it anyway and report here later.
– Senkaku
Nov 22 at 16:36
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
Many Linux distributions give only limited access to the files under /var/log
. However, the directories are mostly accessible.
As far as programs that use files under var/log
, getting info for last logins with last
requires (read) access to /var/log/wtmp
, so revoking access would break that functionality.
Thanks for pointing that out to me. Nevertheless I think that is expected behavior because/usr/bin/last
tries to access/var/log/lastlog
with the permissions of the caller. If executed as root or a member of utmp in Ubuntulast
is still able to perform.
– Senkaku
Nov 22 at 21:18
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
Many Linux distributions give only limited access to the files under /var/log
. However, the directories are mostly accessible.
As far as programs that use files under var/log
, getting info for last logins with last
requires (read) access to /var/log/wtmp
, so revoking access would break that functionality.
Thanks for pointing that out to me. Nevertheless I think that is expected behavior because/usr/bin/last
tries to access/var/log/lastlog
with the permissions of the caller. If executed as root or a member of utmp in Ubuntulast
is still able to perform.
– Senkaku
Nov 22 at 21:18
add a comment |
up vote
1
down vote
Many Linux distributions give only limited access to the files under /var/log
. However, the directories are mostly accessible.
As far as programs that use files under var/log
, getting info for last logins with last
requires (read) access to /var/log/wtmp
, so revoking access would break that functionality.
Thanks for pointing that out to me. Nevertheless I think that is expected behavior because/usr/bin/last
tries to access/var/log/lastlog
with the permissions of the caller. If executed as root or a member of utmp in Ubuntulast
is still able to perform.
– Senkaku
Nov 22 at 21:18
add a comment |
up vote
1
down vote
up vote
1
down vote
Many Linux distributions give only limited access to the files under /var/log
. However, the directories are mostly accessible.
As far as programs that use files under var/log
, getting info for last logins with last
requires (read) access to /var/log/wtmp
, so revoking access would break that functionality.
Many Linux distributions give only limited access to the files under /var/log
. However, the directories are mostly accessible.
As far as programs that use files under var/log
, getting info for last logins with last
requires (read) access to /var/log/wtmp
, so revoking access would break that functionality.
answered Nov 22 at 20:59
Ljm Dullaart
54925
54925
Thanks for pointing that out to me. Nevertheless I think that is expected behavior because/usr/bin/last
tries to access/var/log/lastlog
with the permissions of the caller. If executed as root or a member of utmp in Ubuntulast
is still able to perform.
– Senkaku
Nov 22 at 21:18
add a comment |
Thanks for pointing that out to me. Nevertheless I think that is expected behavior because/usr/bin/last
tries to access/var/log/lastlog
with the permissions of the caller. If executed as root or a member of utmp in Ubuntulast
is still able to perform.
– Senkaku
Nov 22 at 21:18
Thanks for pointing that out to me. Nevertheless I think that is expected behavior because
/usr/bin/last
tries to access /var/log/lastlog
with the permissions of the caller. If executed as root or a member of utmp in Ubuntu last
is still able to perform.– Senkaku
Nov 22 at 21:18
Thanks for pointing that out to me. Nevertheless I think that is expected behavior because
/usr/bin/last
tries to access /var/log/lastlog
with the permissions of the caller. If executed as root or a member of utmp in Ubuntu last
is still able to perform.– Senkaku
Nov 22 at 21:18
add a comment |
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%2fsuperuser.com%2fquestions%2f1377606%2fis-it-safe-to-remove-read-rights-from-all-var-log-files-for-others%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
What applications do you have installed that read /var/log as another user?
– Ramhound
Nov 22 at 16:09
@Ramhound That basically is the question. Are application developers required to gain the necessary privileges to read from /var/log/* or is it normal to expect to be able to read from /var/log/* with the other privilege?
– Senkaku
Nov 22 at 16:24
What is preventing you from trying your idea?
– Ramhound
Nov 22 at 16:34
@Ramhound Some application could fail silently. I guess I will do it anyway and report here later.
– Senkaku
Nov 22 at 16:36