Re: more pigs in the %$^# barn

On Mon, 30 Apr 2012 16:03:52 -0400, Aragorn <stryder@xxxxxxxxxxxxxxxxxx> wrote:

And my guess is that nobody's really interested in finding out about it
either, despite the fact that this is clearly a security breach by
escalation of privileges.

It isn't necessarily an escalation of privileges. Something that is
running as root, is writing to / instead of /root, but it needs
root authority for either.

can't be bothered. They find the introduction of new features in the
next KDE release far more important than fixing bugs.

No. They don't want to spend time digging into possible causes, when
they've already done that, and haven't been able to find the cause.

Until someone provides a consistent method of recreating the bug, and
more info to help track down the cause, there is no point in repeating
something that takes a lot of time, and hasn't worked in the past.

Simply reporting the bug again, without adding new information that
actually helps locate the cause, is a waste of their time.

I've looked into it myself, quite a bit, but have run out of ideas on
how to figure out exactly where the problem is, let alone what the actual
problem is. There are more productive things I can do with my time, rather
then repeating the steps I've already done, to try and track down the cause.

Even if I thought I'd found a cause and a fix, how can I confirm it, if
I can't consistently recreate the problem? There may actually be multiple
causes, unrelated to each other, but resulting in the same symptom.

Having a program (whichever one it is), that's running as root writing
to / instead of /root is not a security issue. It's an annoyance, that
will get a very low priority, by people who have other things to do.

Regards, Dave Hodgins

--
Change nomail.afraid.org to ody.ca to reply by email.
(nomail.afraid.org has been set up specifically for
use in usenet. Feel free to use it yourself.)
.

Relevant Pages