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

List:       kde-linux
Subject:    Re: [kde-linux] Dolphin opening a text file as root with Kwrite.
From:       Anne Wilson <cannewilson () googlemail ! com>
Date:       2010-02-20 10:38:38
Message-ID: 201002201038.41967.cannewilson () googlemail ! com
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Saturday 20 February 2010 02:38:49 James Tyrer wrote:
> Anne Wilson wrote:
> > On Friday 19 February 2010 04:24:36 Duncan wrote:
> >> Anne Wilson posted on Thu, 18 Feb 2010 20:01:32 +0000 as excerpted:
> >>> On Thursday 18 February 2010 18:35:32 James Tyrer wrote:
> >>>> This is not intended behavior.  You have to stop telling people that
> >>>> everything is OK when there is a problem.
> >>> 
> >>> I was told specifically that it was intended behaviour, and the reason
> >>> was security.  I do not deny that problems exist.  I frequently point
> >>> out that the problem is in the user's setup, not the software.  If it
> >>> has been shown to be a bug, I say so.  Do not mis-represent me.
> >> 
> >> FWIW, I expect the lack of a shipped pre-configured kmenu and context
> >> menu option is intended, due to deliberate (kde) choice, because yes,
> >> there are certain security issues.
> >> 
> >> However, it should still work when started properly from the command
> >> line (or if the user configures a menu item appropriately), provided
> >> all the authorization stuff is in order.  If it's not working, then
> >> either something's broken with the authorization, or the command wasn't
> >> formed properly due to incomplete understanding of the required
> >> authorization, etc.
> >> 
> >> So both of you are correct.  It's just that you're talking about
> >> slightly different aspects of the same thing.  The choice not to ship
> >> the preconfigured options was AFAIK deliberate and is intended
> >> behavior.  But it should still work if the user issues the command or
> >> sets up the menu options manually.  A breakage there would /not/ be
> >> intended behavior, simply (deliberately) out of the scope of what's
> >> normally shipped.
> > 
> > Following up on this - if I tried 'kdesu dolphin' then attempted to edit
> > a file, I got the result reported.  However, if I tried 'kdesu kwrite
> > /etc/fstab' I got an editable file.  Perhaps that gives you something to
> > compare, to find what's really happening (or not).
> 
> Did you try, after opening Dolphin as root, opening a Konsole with:
> 
> 	Tools -> Open Terminal
> 
> and running:
> 
> 	kdeinit4
> ??
> 
> Does that fix the problem?

Yes, it seems to.  So are you saying that 'kdesu kwrite
/etc/fstab' must do this in the background, somehow?

Anne
-- 
KDE Community Working Group
New to KDE Software? - get help from http://userbase.kde.org

["signature.asc" (application/pgp-signature)]

___________________________________________________
This message is from the kde-linux mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde-linux.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

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