Re: [opensuse] File Manager Super User mode in oS 11.2
On 11/19/2009 1:14 PM, Teruel de Campo MD wrote:
On Thu, 2009-11-19 at 14:26 -0600, Jim Flanagan wrote:
Is there a way to set it to open with root privileges?
Hope I understand what you asked :)
Open the K menu editor /system/Terminal Choose the one you want to open as root /Advance check run as different users username: root
Save
The next time you click it will ask you for the root password and open the terminal as root.
Nope. You completely misunderstood the problem. The OP does not want to ALWAYS open that terminal program as root. The problem is that when you run file manager (Dolphin) in super user mode any task launched from dolphin should also run as super user. So, if you clicked an rpm it should install it without asking for a password again. If you navigated to /root, you should be able to open any text file you have laying around in there by just clicking it. But you can't because the subordinate task is launched from Dolphin as USER instead of Root. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 19 November 2009 02:45:16 pm John Andersen wrote:
The problem is that when you run file manager (Dolphin) in super user mode any task launched from dolphin should also run as super user.
John, Interesting, I have never saw this problem because whenever I have to go to root I do it cli or krusader. After reading your reply and started Dolphin in super user mode even does not lunch a terminal. I will look into it. -=terry=- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 19 November 2009 04:39:30 pm Teruel de Campo MD wrote:
On Thursday 19 November 2009 02:45:16 pm John Andersen wrote:
The problem is that when you run file manager (Dolphin) in super user mode any task launched from dolphin should also run as super user.
John,
Interesting, I have never saw this problem because whenever I have to go to root I do it cli or krusader. After reading your reply and started Dolphin in super user mode even does not lunch a terminal. I will look into it.
-=terry=-
I've tracked it down to dbus-launch not knowing how to do this. Even if you ssh into the the machine as root and type "dplphin" it still can't do this. dbus-launch is broken. If you ssh into an older machine (10.3 before they ripped out Konqueror's guts and replaced it them with the entrails of dolphin) and type konqueror you can open files. -- If stupidity got us into this mess, then why can't it get us out? - Will Rogers -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 19 November 2009 02:45:16 pm John Andersen wrote:
The problem is that when you run file manager (Dolphin) in super user mode any task launched from dolphin should also run as super user.
John, Whenever I'm root, I use cli or krusader so I did not know about those problems. In my case dolphin as regular user works as it supposed to but I just loaded as a super user and I can delete, move or rename files owned by root but terminal does not come neither kwrite editor so it seems that most of the helper programs do not work under super user but they are all OK under user. I have to check this problem in the other machines. -=terry=- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
The problem is that when you run file manager (Dolphin) in super user mode any task launched from dolphin should also run as super user.
i'm not at all sure that what you say there is a true statement.. that is, why would i (or the Dolphin development team) want _every_ task launched with a root powered file manager to have root powers? Dolphin is a *file manager* and as a file manager with root powers it should be able to manage (move, copy, delete, etc) *files* as root, not launch root powered anything.. now, if it were (say) a "root application launch pad" then if i launched kwrite from it, i'd expect that to also have root powers.. but, today if i'm using any root powered file manager i expect it to only have file manager duties root powered.. so, if i'm moving files with root powers and (for some unknown reason) wanna attract root kits with a root powered Firefox i wouldn't find the firefox executable to click on, instead i'd open a terminal and type kdesu firefox.. anyway, my opinion is this 'problem' is not a problem, Dolphin is working as designed.. and, finally: do not log into KDE, GNOME, Xfce or any other *nix GUI system as root....ever...just don't do it...it is like begging for problems: http://en.opensuse.org/SDB:Login_as_root http://docs.kde.org/stable/en/kdebase-runtime/userguide/root.html http://tinyurl.com/6ry6yd ymmv, DenverD -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 19 November 2009 11:20:42 pm DenverD wrote:
The problem is that when you run file manager (Dolphin) in super user mode any task launched from dolphin should also run as super user.
i'm not at all sure that what you say there is a true statement..
that is, why would i (or the Dolphin development team) want _every_ task launched with a root powered file manager to have root powers?
Why? Because you can't even open a file for which USER does not have permissions even after supplying a password for root.
Dolphin is a *file manager* and as a file manager with root powers it should be able to manage (move, copy, delete, etc) *files* as root, not launch root powered anything..
now, if it were (say) a "root application launch pad" then if i launched kwrite from it, i'd expect that to also have root powers..
but, today if i'm using any root powered file manager i expect it to only have file manager duties root powered..
So moving, deleting of files is ok, but opening a text file or pdf is something you have to open a shell for?
anyway, my opinion is this 'problem' is not a problem, Dolphin is working as designed..
I'm not sure it is designed that way. In fact comments in man dbus-launch seem to suggest that this was intended, but has not been yet implemented. As I mentioned in a prior post, using Konqueror in superuser mode on kde3 allowed any operations kong performed, opened files, install rpms, what ever.
and, finally: do not log into KDE, GNOME, Xfce or any other *nix GUI system as root....ever...just don't do it...it is like begging for problems:
Please spare me the pontification . -- If stupidity got us into this mess, then why can't it get us out? - Will Rogers -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 20 Nov 2009 07:20:42 DenverD wrote:
The problem is that when you run file manager (Dolphin) in super user
so, if i'm moving files with root powers and (for some unknown reason) wanna attract root kits with a root powered Firefox i wouldn't find the firefox executable to click on, instead i'd open a terminal and type kdesu firefox..
anyway, my opinion is this 'problem' is not a problem, Dolphin is working as designed..
Dolphin IS a PITA total it makes things so much more difficult it fails almost completely in almost every department. You need to get to files in "/root" it wont let you it wont launch safely if that is how it was designed then send the designer I'll gladly do him a nasty bring back Konqueror far far better by design , I think a lot of these so called devs now see themselfs as moving to a job with M$ Corp hence the complete failure to listen to the USERS and put the blinkers on just plough straight on not hearing any thing at all cus it dont suit them to hear .
and, finally: do not log into KDE, GNOME, Xfce or any other *nix GUI system as root....ever...just don't do it...it is like begging for problems:
Sound advice BUT by no means at all the rule of law you try to insist it is and just to disprove your theory i had a system running as root for several years with a 24/7 internet connection never a single problem the only reason it is not running now is hardware failure the HDD bearings went sounded like a coffee grinder. Pete . -- Powered by openSUSE 11.2 Milestone 2 (x86_64) Kernel: 2.6.30-rc6-git3-4- default KDE: 4.2.86 (KDE 4.2.86 (KDE 4.3 >= 20090514)) "release 1" 09:05 up 12 days 18:31, 3 users, load average: 0.12, 0.05, 0.01
Sound advice BUT by no means at all the rule of law you try to insist it is and just to disprove your theory i had a system running as root for several years with a 24/7 internet connection never a single problem
and you suggest that? no matter their experience or individual networking security expertise? rule of law? no it is your machine, if you want to log into KDE, GNOME, whatever GUI as root 24/7 that is your business...but, if want to propose to the new folks jumping off the Redmond Ship every day that that is the secure way for them to operate their new install, then you have to excuse me for stating my opinion on the matter.. and, imho for them it should be law....at least until the have better idea of the pitfalls....well, at least *know* what a "root kit" is.. but, tell me what task is it that *requires* one to log into the GUI as root which cannot be accomplished without? DenverD -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 20 Nov 2009 09:59:48 DenverD wrote:
Sound advice BUT by no means at all the rule of law you try to insist it is and just to disprove your theory i had a system running as root for several years with a 24/7 internet connection never a single problem
and you suggest that? no matter their experience or individual networking security expertise?
rule of law? no it is your machine, if you want to log into KDE, GNOME, whatever GUI as root 24/7 that is your business...but, if want to propose to the new folks jumping off the Redmond Ship every day that that is the secure way for them to operate their new install, then you have to excuse me for stating my opinion on the matter..
and, imho for them it should be law....at least until the have better idea of the pitfalls....well, at least *know* what a "root kit" is..
but, tell me what task is it that *requires* one to log into the GUI as root which cannot be accomplished without?
DenverD
No i dont suggest that but mereley stating a fact that some of you out there are hyper paranoid if i were in your shoes i would not even bother turning the PC on cus someone may be attempting to get into it Pete -- Powered by openSUSE 11.2 Milestone 2 (x86_64) Kernel: 2.6.30-rc6-git3-4- default KDE: 4.2.86 (KDE 4.2.86 (KDE 4.3 >= 20090514)) "release 1" 12:12 up 12 days 21:38, 4 users, load average: 0.13, 0.09, 0.06
DenverD wrote:
Sound advice BUT by no means at all the rule of law you try to insist it is and just to disprove your theory i had a system running as root for several years with a 24/7 internet connection never a single problem
and you suggest that? no matter their experience or individual networking security expertise?
rule of law? no it is your machine, if you want to log into KDE, GNOME, whatever GUI as root 24/7 that is your business...but, if want to propose to the new folks jumping off the Redmond Ship every day that that is the secure way for them to operate their new install, then you have to excuse me for stating my opinion on the matter..
and, imho for them it should be law....at least until the have better idea of the pitfalls....well, at least *know* what a "root kit" is..
but, tell me what task is it that *requires* one to log into the GUI as root which cannot be accomplished without?
DenverD
Case in point is my original post. In previous versions of openSuse, and Suse before that, I could open file manager (back then konk) enter root password as prompted, and perform tasks such as open, read, edit, save, etc. files as needed, without having to log in a session as root. Now without that capability, I am forced to log into a new session as root, which both takes more time and is something I'd rather not have to do if avoidable. If this is a bug I will file a report. I was hoping it wasn't, and there was a quick fix for this. If this is a "feature" well, I'll file a bug report anyway, or look for a better alternative. Thanks, Jim -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
DenverD wrote:
Sound advice BUT by no means at all the rule of law you try to insist it is and just to disprove your theory i had a system running as root for several years with a 24/7 internet connection never a single problem
and you suggest that? no matter their experience or individual networking security expertise?
rule of law? no it is your machine, if you want to log into KDE, GNOME, whatever GUI as root 24/7 that is your business...but, if want to propose to the new folks jumping off the Redmond Ship every day that that is the secure way for them to operate their new install, then you have to excuse me for stating my opinion on the matter..
and, imho for them it should be law....at least until the have better idea of the pitfalls....well, at least *know* what a "root kit" is..
but, tell me what task is it that *requires* one to log into the GUI as root which cannot be accomplished without?
DenverD
Case in point is my original post. In previous versions of openSuse, and Suse before that, I could open file manager (back then konk) enter root password as prompted, and perform tasks such as open, read, edit, save, etc. files as needed, without having to log in a session as root. Now without that capability, I am forced to log into a new session as root, which both takes more time and is something I'd rather not have to do if avoidable.
If this is a bug I will file a report. I was hoping it wasn't, and there was a quick fix for this. If this is a "feature" well, I'll file a bug report anyway, or look for a better alternative.
Thanks,
Jim Searching bugzilla finds this bug has been reported for 11.2 milestones #450203, almost a full year ago, on 2009-11-29, a week from now will be a year. Severity is listed as Major. I don't see any notes from the developers. It started with Dolphin, which we already knew. The bugzilla
Jim Flanagan wrote: page shows this to be opened for 10.3, but when you look at the bug report is shows 11.2. There have been a few other duplicate reports filed, so filing another one will probably not help. Is Suse going to get to this or are they leaving it to the KDE guys? Jim -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 11/21/2009 6:39 AM, Jim Flanagan wrote:
Searching bugzilla finds this bug has been reported for 11.2 milestones #450203, almost a full year ago, on 2009-11-29, a week from now will be a year. Severity is listed as Major. I don't see any notes from the developers. It started with Dolphin, which we already knew. The bugzilla page shows this to be opened for 10.3, but when you look at the bug report is shows 11.2. There have been a few other duplicate reports filed, so filing another one will probably not help.
Is Suse going to get to this or are they leaving it to the KDE guys?
Jim
Its a KDE bug, so I don't see opensuse handeling it. It resides id dbus-launch, which seems incapable of a true user context swtich. If you want this functionality without waiting for KDE to fix this you can replicate the menu item for Super User mode (Copy, Paste) and change the command to ssh -X -f root@localhost dolphin Uncheck Run as Different user in Advanced tab. Optionally, as root, you can do something like cat /home/[user]/.ssh/id_rsa.pub >> /root/.ssh/authorized_keys if you wish to avoid passwords. Just skip this step if you want a] password prompt each time to remind you of the risk. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 20 November 2009 12:20:42 am DenverD wrote:
anyway, my opinion is this 'problem' is not a problem, Dolphin is working as designed..
I do not thinks so. When you use Dolphin as a users or as a superuser it should be similar and it is not. The fact that when you try to read a file with kwrite for example shows an error, the fact that when you try to lunch a terminal (which is the dolphins menu)nothing happens does indicates that something is not working as it should. Do we need those facilities, well the answer is not, because linux has many ways to do the same thing however, I believe an important function of this forum is to find out problems and if real opening a bug report. Regards, -=terry=- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Teruel de Campo MD wrote:
I believe an important function of this forum is to find out problems and if real opening a bug report.
sounds real to me, but since i don't even have a Dolphin i'll leave the bug reporting to someone who does, like you...begin here: http://en.opensuse.org/Submitting_Bug_Reports DenverD -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 20 November 2009 06:11:57 am DenverD wrote:
i'll leave the bug reporting to someone who does, like you...begin here:
I know the site very well because I have done many. -=terry=- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 11/20/2009 5:11 AM, DenverD wrote:
Teruel de Campo MD wrote:
I believe an important function of this forum is to find out problems and if real opening a bug report.
sounds real to me, but since i don't even have a Dolphin i'll leave the bug reporting to someone who does, like you...begin here:
http://en.opensuse.org/Submitting_Bug_Reports
DenverD
Interesting. You don't even have dolphin and therefore have never seen the behavior, yet you weigh in and say it is working as designed, lecture us like school children about logging in as root (when super user mode was intended PRECISELY to avoid the need to do that), and then only BELATEDLY do you fess up to not having dolphin at all!!!? Unbelievable! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (5)
-
DenverD -
Jim Flanagan -
John Andersen -
Peter Nikolic -
Teruel de Campo MD