All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paolo Ciarrocchi" <ciarrocchi@linuxmail.org>
To: albert@users.sourceforge.net
Cc: rml@tech9.net, linux-kernel@vger.kernel.org
Subject: Re: [announce] procps 2.0.13 with NPTL enhancements
Date: Fri, 30 May 2003 16:12:26 +0800	[thread overview]
Message-ID: <20030530081226.13903.qmail@linuxmail.org> (raw)

>>> Well, since I read Albert Cahalan's comment in
>>> Debian bug #172735 [1] I understand the people
>>> maintaining a different branch...
>>
>> Exactly.
>>
>> That bug is fixed in the official tree, fyi.
>> A segfault, as you said, is always a bug.
>> An error message is displayed.
>
>You asked for it...
>
>Nice cheapshot there. So, if I remove some
>critical kernel interfaces from your system,
>nothing should crash? How about I take out
>a few choice system calls or a chunk of libc?

It is not the same thing, I think that you
agree on that, too.

>(note: the "bug" is not exploitable)
>
>Face it. For nearly a decade, /proc has been
>a critical kernel interface. This isn't 1991.
>(embedded systems excepted; they don't use procps)
>
>That said, I may do something about the issue
>simply to please users with messed-up systems.

In my opinion, you have to do something about
the issue, because it is a bug, it is not
a missing feature. But this is just my opinion,
you are the maintainer, you take decisions.

>> Once that bug is fixed, he will probably find
>> that the inability to read files in /proc also
>> causes a crash. Such is the problem with this
>> duplicated effort. It sucks.
>
>I could tell you about some inputs that
>make your programs crash... Nah. Find them
>yourself. I wait for your screams. >:-)

'Find them yourself', nice answer ;-(
It is a pity read this kind of comment,
I still don't understand the reasons 
of this duplications of code and the reason
of this kind of silly sarcastic remarks.

>You finally fixed a SEGV that I fixed well
>over a year ago. Congradulations. You have
>others to fix, and a minor (?) security
>issue as well. Have fun.

Again, you know there is a problem but you
don't say anything about it.
You do not want to fix it, don't you ?
This is fine with me (even if it is hard to 
understand the reason), but you are just
/wrong/ when you know about a problem and
don't provide information about it.
Again, this is just my opinion...

>Oooh... I think you have an exploitable
>buffer overflow as well. Anybody running
>his procps as an i386 binary on IA-64?

Ditto.

Ciao,
          Paolo

-- 
______________________________________________
http://www.linuxmail.org/
Now with e-mail forwarding for only US$5.95/yr

Powered by Outblaze

             reply	other threads:[~2003-05-30  7:58 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-30  8:12 Paolo Ciarrocchi [this message]
2003-05-30  8:20 ` [announce] procps 2.0.13 with NPTL enhancements cosmos
2003-05-30  8:38   ` VFS & DEVFS cosmos
  -- strict thread matches above, loose matches on Subject: below --
2003-05-31  2:36 [announce] procps 2.0.13 with NPTL enhancements Xose Vazquez Perez
2003-05-30 18:59 Xose Vazquez Perez
     [not found] <1054270854.22088.617.camel@cube>
2003-05-30  6:26 ` Adrian Bunk
2003-06-01  4:53   ` Werner Almesberger
2003-05-30 16:56 ` Xose Vazquez Perez
     [not found] ` <3ED788B5.2080203@wanadoo.es>
2003-05-31  1:25   ` Albert Cahalan
2003-05-30  5:30 Albert Cahalan
2003-05-29 17:25 Xose Vazquez Perez
2003-05-29 18:08 ` Adrian Bunk
2003-05-29 11:16   ` Robert Love
2003-05-29 20:01   ` Vincent Hanquez
2003-05-29 15:40     ` Robert Love
2003-05-28 15:09 Robert Love
2003-05-28 23:19 ` Phil Oester
2003-05-28 16:22   ` Robert Love
2003-05-28 23:59     ` Miquel van Smoorenburg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030530081226.13903.qmail@linuxmail.org \
    --to=ciarrocchi@linuxmail.org \
    --cc=albert@users.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@tech9.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.