Re: Access rights for system logs

2011-03-04 Thread Matthias Runge
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/03/11 23:07, Cleaver, Japheth wrote: >> On Friday, February 25, 2011 03:13:31 am Matthias Runge wrote: >>> - change systems logs owners from root:root mode 600 to root:adm mode >>> 640 (or something similar) >> snip > One benefit of setgid over s

RE: Access rights for system logs

2011-03-01 Thread Cleaver, Japheth
> On Friday, February 25, 2011 03:13:31 am Matthias Runge wrote: > > - change systems logs owners from root:root mode 600 to root:adm mode > > 640 (or something similar) > > So, what would be the implementation of this? How would logcheck or any log > reader > work. Would they be setgid applicati

Re: Access rights for system logs

2011-02-28 Thread Matthias Runge
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/28/11 17:46, Steve Grubb wrote: > On Friday, February 25, 2011 03:13:31 am Matthias Runge wrote: >> - change systems logs owners from root:root mode 600 to root:adm mode >> 640 (or something similar) > > So, what would be the implementation of t

Re: Access rights for system logs

2011-02-28 Thread Till Maas
On Mon, Feb 28, 2011 at 08:26:05PM +1030, Glen Turner wrote: > On Sun, 2011-02-27 at 23:20 +0100, Till Maas wrote: > > On Sun, Feb 27, 2011 at 12:30:43PM -0700, Kevin Fenzi wrote: > > > > > Were you thinking of just /var/log/messages? or all log files? > > > Or all syslog written files? or ? > >

Re: Access rights for system logs

2011-02-28 Thread Till Maas
On Mon, Feb 28, 2011 at 11:46:13AM -0500, Steve Grubb wrote: > On Friday, February 25, 2011 03:13:31 am Matthias Runge wrote: > > - change systems logs owners from root:root mode 600 to root:adm mode > > 640 (or something similar) > > So, what would be the implementation of this? How would logchec

Re: Access rights for system logs

2011-02-28 Thread Steve Grubb
On Friday, February 25, 2011 03:13:31 am Matthias Runge wrote: > - change systems logs owners from root:root mode 600 to root:adm mode > 640 (or something similar) So, what would be the implementation of this? How would logcheck or any log reader work. Would they be setgid applications or would

Re: Access rights for system logs

2011-02-28 Thread Glen Turner
On Sun, 2011-02-27 at 23:20 +0100, Till Maas wrote: > On Sun, Feb 27, 2011 at 12:30:43PM -0700, Kevin Fenzi wrote: > > > Were you thinking of just /var/log/messages? or all log files? > > Or all syslog written files? or ? > > > > If you are talking all log files, I would suggest making this into

Re: Access rights for system logs

2011-02-27 Thread Till Maas
On Sun, Feb 27, 2011 at 12:30:43PM -0700, Kevin Fenzi wrote: > Were you thinking of just /var/log/messages? or all log files? > Or all syslog written files? or ? > > If you are talking all log files, I would suggest making this into a > feature for f16, since it's going to require coordinating a

Re: Access rights for system logs

2011-02-27 Thread Kevin Fenzi
On Sat, 26 Feb 2011 10:44:05 +0100 Matthias Runge wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 02/25/11 17:21, Till Maas wrote: ...snip... > > I like a special group just for accounts that should be able to > > read all log files, too, e.g. a group logread. > > > > Regards

Re: Access rights for system logs

2011-02-26 Thread Matthias Runge
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/25/11 17:21, Till Maas wrote: > On Fri, Feb 25, 2011 at 03:50:57PM +0100, Matej Cepl wrote: >> Dne 25.2.2011 10:39, Mogens Kjaer napsal(a): >>> create 640 root wheel >>> >>> to /etc/logrotate.d/syslog and have added bbuser to the wheel group. >>>

Re: Access rights for system logs

2011-02-25 Thread Till Maas
On Fri, Feb 25, 2011 at 03:50:57PM +0100, Matej Cepl wrote: > Dne 25.2.2011 10:39, Mogens Kjaer napsal(a): > > create 640 root wheel > > > > to /etc/logrotate.d/syslog and have added bbuser to the wheel group. > > > > That file is owned by rsyslog in Fedora and sysklogd in RHEL. > > I am not sur

Re: Access rights for system logs

2011-02-25 Thread Matej Cepl
Dne 25.2.2011 10:39, Mogens Kjaer napsal(a): > create 640 root wheel > > to /etc/logrotate.d/syslog and have added bbuser to the wheel group. > > That file is owned by rsyslog in Fedora and sysklogd in RHEL. I am not sure whether wheel is the correct group ... I don't think we should mix togethe

Re: Access rights for system logs

2011-02-25 Thread Mogens Kjaer
On 02/25/2011 09:13 AM, Matthias Runge wrote: > yum provides "*/messages" did not list it. Is it really unowned? In order to give Big Brother read access to /var/log/messages I have added: create 640 root wheel to /etc/logrotate.d/syslog and have added bbuser to the wheel group. That file is ow

Re: Access rights for system logs

2011-02-25 Thread Matej Cepl
Dne 25.2.2011 09:13, Matthias Runge napsal(a): > What do you think? Did I miss something? Has anybody of you another hint? No detailed analysis, but just brief +1 (unless some terrible issue is discovered in further discussion) ... I really liked this on Debian. Matěj -- devel mailing list deve

Access rights for system logs

2011-02-25 Thread Matthias Runge
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, currently, I'm the maintainer of logcheck. It parses system logs and sends mails defined by regular expressions. It's a package mostly adopted for debian. The README says, it is recommended to create an own user and put it into adm group. This le