On Tue, Sep 28, 1999 at 12:01:16PM +1000, Herbert Xu wrote:
> On Mon, Sep 27, 1999 at 05:30:51PM -0700, Joey Hess wrote:
> > >
> > > Actually, it should be critical if it's a root exploit. Grave only
> > > includes
> > > those that only comprise the user's account.
> >
> > Last I checked, root
Steve Greenland wrote:
> It's clear to you, but perhaps not to the user who submitted it;
> for him/her, it "makes the package in question unuseable". You look
> at it, realize that it's unique to that user, and send a message to
> [EMAIL PROTECTED] to re-priotize it. What's the big deal?
Aside fr
On 27-Sep-99, 11:33 (CDT), Joey Hess <[EMAIL PROTECTED]> wrote:
> grave
> makes the package in question unuseable or mostly so, or causes data
> loss, or introduces a security hole allowing access to the accounts of
> users who use the package.
>
> I've noticed that in many of
On Mon, Sep 27, 1999 at 05:30:51PM -0700, Joey Hess wrote:
> >
> > Actually, it should be critical if it's a root exploit. Grave only includes
> > those that only comprise the user's account.
>
> Last I checked, root is a user. This is not a formal definition we're
> working from, please use com
In article <[EMAIL PROTECTED]> you wrote:
> What do other think, and have you seen seeing the same runaway bug severity
> inflation I have?
Yes. Submitters seem to think that if they crank up the severity, the bug
will get more/quicker attention. At least in my case, that just isn't true.
I'm
* "Joey" == Joey Hess <[EMAIL PROTECTED]> wrote:
Joey> (Note: grave is a _higher_ priotity than critical.
I don't think so.
http://www.debian.org/Bugs/Developer#severities
The severity levels are:
critical
makes unrelated software on the system (or the whole system)
break, or caus
Herbert Xu wrote:
> Joey Hess <[EMAIL PROTECTED]> wrote:
> > Herbert Xu wrote:
> >>
> >> I disagree. If a package causes a remote root exploit to be available,
> >> even
> >> if it's only in a very specific configuration, I would say that it is
> >> critical.
>
> > No, it's grave. All security
Joey Hess <[EMAIL PROTECTED]> wrote:
> Herbert Xu wrote:
>>
>> I disagree. If a package causes a remote root exploit to be available, even
>> if it's only in a very specific configuration, I would say that it is
>> critical.
> No, it's grave. All security bugs are grave, it's part of the defini
Herbert Xu wrote:
> Joey Hess <[EMAIL PROTECTED]> wrote:
> >
> > Similarly, I don't think a bug is grave if it makes a package unusable by
> > just one person in an odd sitution. On the other hand, I think all security
> > and data loss bugs are grave, even if only a few people can trigger them.
>
Joey Hess <[EMAIL PROTECTED]> wrote:
>
> Similarly, I don't think a bug is grave if it makes a package unusable by
> just one person in an odd sitution. On the other hand, I think all security
> and data loss bugs are grave, even if only a few people can trigger them.
I disagree. If a package cau
I've been saying the same thing now for a while... I get peeved at some of
the > normal bugs I've seen reported..
On Mon, Sep 27, 1999 at 09:33:39AM -0700, Joey Hess wrote:
> http://www.debian.org/Bugs/Developer#severities talks about bug severities:
>
> critical
> makes unrelated softwar
Le Mon, Sep 27, 1999 at 09:33:39AM -0700, Joey Hess écrivait:
> What do other think, and have you seen seeing the same runaway bug severity
> inflation I have?
I do. I think that we should clarify that bug reporting is good but only
if people have time/knowledge to submit "good reports" aka :
- ch
12 matches
Mail list logo
