[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: ACLs in Kivio
From:       Shawn Gordon <shawn () thekompany ! com>
Date:       2001-05-01 15:51:01
[Download RAW message or body]

At 10:44 AM 5/1/2001, you wrote:
>On Monday 30 April 2001 23:37, Carsten Pfeiffer wrote:
> > On Montag, 30. April 2001 21:51 Martin Konold wrote:
> > > I do not buy this. This is about the CVS version not about a stable 1.0
> > > release. IMHO it is better to deal with the relevant problems which might
> > > be caused by some check in by talking/mailing to the relevant developer
> > > not via ACL.
> > >
> > > What is so special about kivio compared to stuff like konqueror etc?
> >
> > what I'm wondering about: there is kde-cvs, you can monitor each and every
> > commit and those connectors are somehow a really basic feature, so someone
> > should have noticed this really soon, no?
> >
> > Working on KDE CVS gives you some responsibility, especially when working
> > on other people's code. But maintaining an application in CVS also means
> > taking the responsibility to have a look at it once in a while, especially
> > before a release, not after.
> >
> > I really dislike putting ACLs onto all sorts of modules, where just a
> > handful of people have access. (I agree that the www module is special
> > tho.) It's just the wrong solution for the problem here.
>
>Same opinion here.
>I'm also against putting ACL's on _any_ kind of module.
>It will only slow down our project.
>People who get CVS-rights should be chosen carefully enough to prevent
>misusage.
>
>Greetings,
>Tackat
>
> > Cheers,
> > Carsten Pfeiffer

keeping in mind that I spent 17 years doing software security (among other 
things), the first reaction to a problem is "lock it down".  I don't care 
so much about ACL as doing my best to avoid wasted time on silly problems.

Regards,

Shawn Gordon
President
theKompany.com
www.thekompany.com
949-713-3276

[prev in list] [next in list] [prev in thread] [next in thread]