sudoedit - good catch! was [Re: sudo vs. gksu ]

[NoOp]

On 04/06/2008 12:56 AM, Peter Garrett wrote:
> On Sun, 06 Apr 2008 03:37:07 -0400
> "Michael R. Head" <burner at suppressingfire.org> wrote:
> 
>> On Sat, 2008-04-05 at 15:28 +0200, Mario Vukelic wrote:
>> > On Sat, 2008-04-05 at 14:11 +0100, Tony Arnold wrote:
>> > > Can you explain how this problem is avoided with gksu, or gksudo? So far
>> > > as I can see using one of these causes the application to run with UID
>> > > of 0, i.e., root. The app has no knowledge of how it was invoked, so any
>> > > files is creates will be owned by root.
>> > > 
>> > > Your explanation applies to running any app, not just graphical ones.
>> > 
>> > http://www.psychocats.net/ubuntu/graphicalsudo 
>> 
>> That page says that "sudo nano /etc/apt/sources.list"  is a good idea.
>> It isn't, and for the same reason graphical apps shouldn't be run
>> through sudo -- nano will create/edit extra files in your home
>> directory. In fact, there's a command called "sudoedit" which solves the
>> problem.
> 
> Aha! 
> 
> Here I was thinking that there was a bug in nano that made the
> ~/.nano_history file belong to root, and all along it was simply the wrong
> command for the job!
> 
> Do you happen to know under what circumstances the permissions change?
> The above does not always occur, which is one reason that I was confused...
> 
> Thanks - this helps to solve one of the little problems that I have been
> wrestling with in my live CD project.
> 
> :-)
> 
> Peter
> 
> 

Heads up:
https://bugs.launchpad.net/ubuntu/+source/nano/+bug/39866
[Breaks config files by adding hard line breaks]