On Mar 28, Martin Schulze <[EMAIL PROTECTED]> wrote:
> - critical security fix:2 days.
I think those fixes should be uploaded as fast as possible by anyone
willing, if a remote root exploit for some package like apache or ssh
is published users can't just shut down their machines fo
Previously Branden Robinson wrote:
> Well, we could concievably follow the FHS in every other respect, though,
> right? From a standards-compliance point-of-view, it's less egregious to
> have an extra directory in /var (/var/lib) than to fail to have directories
> the FHS says should be there.
I
On Sun, 28 Mar 1999, Darren O. Benham wrote:
> On Sun, Mar 28, 1999 at 05:21:55PM -0700, Jason Gunthorpe wrote:
> > Eh? You can't be a Debian developer without an account on master, if Lars
> Sure you can. Lars is.
Ah, let us be a little more clear here.
If we move to using a central directory
On Sun, Mar 28, 1999 at 05:21:55PM -0700, Jason Gunthorpe wrote:
> Eh? You can't be a Debian developer without an account on master, if Lars
Sure you can. Lars is.
> How are you going to do it any other way, the only thing every maintainer
> has to do is access the machines, some people never upl
On Mon, 29 Mar 1999, Wichert Akkerman wrote:
> Previously Darren O. Benham wrote:
> > I *hate* expiring passwords!
>
> There is another problem: not all developers have an account on master.
> (simple example: Lars Wirzenius).
>
> Can't we do this in the LDAP database?
Eh? You can't be a Debia
Previously Darren O. Benham wrote:
> I *hate* expiring passwords!
There is another problem: not all developers have an account on master.
(simple example: Lars Wirzenius).
Can't we do this in the LDAP database?
Wichert.
--
===
On Sun, Mar 28, 1999 at 02:47:37PM -0700, Jason Gunthorpe wrote:
> I am hoping to get a mechanism to detect absent maintainers as we move to
> having our maintainer database in a directory. My current thought is to
> just turn on shadow password aging, you have to set your password once a
> year or
7 matches
Mail list logo
