On Thu, 28 Aug 2008, intrigeri wrote:
> I have login 1:4.1.1-3 and libpam-modules 1.0.1-3.
>
> This obviously does not happen when logging via ssh/gdm/..., since
> these do not use /etc/pam.d/login at all.
Then, strictly speaking, the file lastlog is not always created when needed,
as there are
> On Sat, 28 Jun 2008, intrigeri wrote:
>> ,
>> | /var/log/lastlog
>> `
>>
>> I could find no authoritative document saying if it has to exist or
>> not. Anyway, the default /etc/pam.d/login provided by the login
>> package enables the pam_lastlog.so module, that not only "prints the
>> l
On Sat, 28 Jun 2008, intrigeri wrote:
> ,
> | /var/log/lastlog
> `
>
> I could find no authoritative document saying if it has to exist or
> not. Anyway, the default /etc/pam.d/login provided by the login
> package enables the pam_lastlog.so module, that not only "prints the
> last login
Hello,
Santiago Vila wrote (06 Aug 2008 15:04:28 GMT) :
> I would feel better if only this change (and not the one in
> logrotate) were done for lenny. What's the status of the proposed
> logrotate change?
The proposed logrotate change (I guess you mean #488365) was an error,
it’s been tagged won
Oops, forgot the rationale for my previous message: At least the
logrotate changes may be disabled by the user just by changing
a configuration file.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Hi.
I would feel better if only this change (and not the one in logrotate)
were done for lenny. What's the status of the proposed logrotate change?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
tags 488376 + patch
thanks
Hello,
intrigeri wrote (28 Jun 2008 15:47:58 GMT) :
> Santiago Vila wrote (28 Jun 2008 14:23:46 GMT) :
>> I would be willing to change base-files postinst so that those
>> files are only created in the initial install (performed by
>> debootstrap from debian installer),
Santiago Vila wrote (28 Jun 2008 14:23:46 GMT) :
> I would be willing to change base-files postinst so that those files
> are only created in the initial install (performed by debootstrap
> from debian installer), and not on every upgrade. There is already
> a block of code which only runs in the i
Hello,
Santiago Vila wrote (28 Jun 2008 14:28:52 GMT) :
> Hmm, what about this from utmp(5)?
>Unlike various other systems, where utmp logging can be
>disabled by removing the file, utmp must always exist
>on Linux.
Right. As far as my research has gone, this is only true
severity 488376 wishlist
thanks
Hmm, what about this from utmp(5)?
Unlike various other systems, where utmp logging can be disabled by
removing the file, utmp must always exist on Linux.
I'm starting to think that base-files should not be blamed for creating
those files.
--
I would be willing to change base-files postinst so that those files
are only created in the initial install (performed by debootstrap
from debian installer), and not on every upgrade. There is already
a block of code which only runs in the initial install, it would
be just a matter of moving the o
Package: base-files
Version: 4.0.4
Severity: normal
Tags: security
Hello,
Context #1 : there is some work being done to to give the system
administrator the means to implement site-logging policies ; today’s
focus is to allow a Debian system administrator to disable, « the
Debian way », login rec
12 matches
Mail list logo
