On Vi, 19 iun 20, 09:58:40, to...@tuxteam.de wrote:
> On Fri, Jun 19, 2020 at 05:54:38AM +0300, Andrei POPESCU wrote:
> > On Mi, 17 iun 20, 10:55:55, to...@tuxteam.de wrote:
> > >
> > > Making things user friendly (something we *gotta* do) means sometimes
> > > taking decisions for the user.
On Fri, Jun 19, 2020 at 05:54:38AM +0300, Andrei POPESCU wrote:
> On Mi, 17 iun 20, 10:55:55, to...@tuxteam.de wrote:
> >
> > Making things user friendly (something we *gotta* do) means sometimes
> > taking decisions for the user. Where's the limit? Where's too much
> > (authoritarian software)?
On Mi, 17 iun 20, 10:55:55, to...@tuxteam.de wrote:
>
> Making things user friendly (something we *gotta* do) means sometimes
> taking decisions for the user. Where's the limit? Where's too much
> (authoritarian software)? Where's too litle (RTFM software)? You'll
> be wrong most of the time for
On Tue, Jun 16, 2020 at 04:51:39PM -0700, Gary L. Roach wrote:
[...]
> Miacopa
All is well, and sorry if my tone was... rough.
> I think I was venting. I am so frustrated with this whole Dolphin
> mess that I may have gone overboard [...]
I feel your pain. Not from KDE land, but I think it's
Le mercredi 17 juin 2020 01:40:05 UTC+2, Gary L. Roach a écrit :
[...]
> I now have to start communications with the Elmerfem people who have
> religated their GUI Qt4 problems from a bug to an inhancement. I have
> gotten warnings from several different sources that Debian is dropping
> Qt4
(Apologies if this link have been given before)
You will find a thread there on a KDE forum detailing why running Dolphin as
root is discouraged and how to bypass this measure:
https://forum.kde.org/viewtopic.php?t=141836
On 6/16/20 12:26 AM, to...@tuxteam.de wrote:
On Tue, Jun 16, 2020 at 09:21:24AM +0200, Marco Möller wrote:
On 15.06.20 21:47, Gary L. Roach wrote:
Someone in the Debian hierarchy decided that root Dolphin was too
much of a security risk. So the problem has propagated to at least
a half dozen
On 6/15/20 1:05 PM, Andrei POPESCU wrote:
On Lu, 15 iun 20, 12:47:59, Gary L. Roach wrote:
I assume that with respect to the original message that it should be obvious
that the root user problem stems from the underlying Debian OS. Someone in
the Debian hierarchy decided that root Dolphin
On Tue, Jun 16, 2020 at 09:21:24AM +0200, Marco Möller wrote:
> On 15.06.20 21:47, Gary L. Roach wrote:
> >Someone in the Debian hierarchy decided that root Dolphin was too
> >much of a security risk. So the problem has propagated to at least
> >a half dozen other distros
On Tue, Jun 16, 2020 at 08:33:29AM +1000, Keith bainbridge wrote:
[...]
> Here, hear i say. It is my computer.
You own it, you do the work. Complaining ain't working ;-D
> Now, i just tested both caja and nemo and both run as sudo and su
> -c. caja could not connect to ibus. (Default file
On 15.06.20 21:47, Gary L. Roach wrote:
Someone in the Debian hierarchy decided that root Dolphin was too much
of a security risk. So the problem has propagated to at least a half
dozen other distros (Ubuntu,Kubuntu, Mint) to name a couple.
To my knowledge, this is not true!
It is the Dolphin
OS. Someone in
the Debian hierarchy decided that root Dolphin was too much of a security
risk. So the problem has propagated to at least a half dozen other distros
(Ubuntu,Kubuntu, Mint) to name a couple.
Do you have any source for this claim?
Debian tends to do little if any customization
one in
> > the Debian hierarchy decided that root Dolphin was too much of a security
> > risk. So the problem has propagated to at least a half dozen other distros
> > (Ubuntu,Kubuntu, Mint) to name a couple.
>
> Do you have any source for this claim?
>
> Debian tends to
On Lu, 15 iun 20, 12:47:59, Gary L. Roach wrote:
>
> I assume that with respect to the original message that it should be obvious
> that the root user problem stems from the underlying Debian OS. Someone in
> the Debian hierarchy decided that root Dolphin was too much of a securit
t a better world. So, we just do the best we can.
Hi all,
I'M late getting into this but after reading through all of the
missives, I have a few comments.
I assume that with respect to the original message that it should be
obvious that the root user problem stems from the underlying Debian OS.
On Wed, Jun 10, 2020 at 4:12 AM Marco Möller
wrote:
>
> On 09.06.20 23:55, Default User wrote:
> > (...)
> > Now, a final note.
> >
> > When I did my main install, it was a day or two before the release of
> > Buster 10.0. I immediately upgraded to Unstable. But it is still
> > originally based
On 09.06.20 23:55, Default User wrote:
(...)
Now, a final note.
When I did my main install, it was a day or two before the release of
Buster 10.0. I immediately upgraded to Unstable. But it is still
originally based upon Stretch. It was set up with both root and user
passwords. And I use
On Ma, 09 iun 20, 17:55:07, Default User wrote:
>
> Well, when I did an alternate Buster Stable install on a spare drive,
> I was surprised (not happily) that when running from that setup,
> various programs demand the root password, and will not accept the
> user password. So, now I have to
On Sunday, Jun 7, 2020, at 12:11, Kushal Kumaran wrote:
>
>Running
>
> sudo sh -c 'unset SUDO_USER; KDE_FULL_SESSION=true
> dolphin'
>
> from a shell gets a dolphin window.
Thanks, Kushal. That does work. For Dolphin, anyway.
> There is some advice at
>
On Mon, Jun 08, 2020 at 09:07:58AM +0300, Andrei POPESCU wrote:
> In Debian's default configuration members of group 'sudo' have sudo
> access, so all you need is:
>
> adduser my_user_name sudo
(and then log out and back in)
> As far as I know the installer does the equivalent of that.
If
On Du, 07 iun 20, 21:21:07, Marco Möller wrote:
>
> Yes, design options exist. However, I never tried out if the user root could
> be blocked by the graphical session manager only, in the case of KDE usually
> sddm is in use. But I know that the login of user root can be blocked in
> general:
On 07.06.20 02:42, Keith bainbridge wrote:
On 7/6/20 8:30 am, Marco Möller wrote:
I would easily agree with you concerning not to log into a graphical
session as the user root. But Dolphin is also not running with sudo
prepended.
And here I was thinking that the dolphin issue ran here
On 7/6/20 12:56 pm, Default User wrote:
So I guess I just got spoiled, using the nemo file manager in Cinnamon.
Just right click the Cinnamon desktop, select "Open as root", then use
nemo with temporarily elevated privileges. Then close nemo, and I am
back to the desktop as a regular user
s are
> > deliberately working to prevent users from using some programs, including
> > Dolphin as root, as a "security measure".
> I have no idea what the unfixable security vulnerabilities are.
Perhaps the attack claimed here will answer that:
https://blog.martin-gra
ed to see many references to this problem,
>> > saying that this is not a bug, but a feature - that kde developers are
>> > deliberately working to prevent users from using some programs, including
>> > Dolphin as root, as a "security measure".
>> >
>> > So, ca
hat kde developers are
> > deliberately working to prevent users from using some programs, including
> > Dolphin as root, as a "security measure".
> >
> > So, can the current version of Dolphin in Debian Stable be run as root
> > (without re-compiling, et
seem to run
> Dolphin or Konqueror as root.
>
> Searching online, I was astounded to see many references to this problem,
> saying that this is not a bug, but a feature - that kde developers are
> deliberately working to prevent users from using some programs, including
> Dolphin as roo
On 7/6/20 8:30 am, Marco Möller wrote:
I would easily agree with you concerning not to log into a graphical
session as the user root. But Dolphin is also not running with sudo
prepended.
And here I was thinking that the dolphin issue ran here for several
days, just a few weeks ago
stounded to see many references to this
problem, saying that this is not a bug, but a feature - that kde
developers are deliberately working to prevent users from using
some programs, including Dolphin as root, as a "security measure".
So, can the current ver
evelopers are deliberately working to prevent users from using some
programs, including Dolphin as root, as a "security measure".
So, can the current version of Dolphin in Debian Stable be run as
root (without re-compiling, etc)?
And, if not, how (and why) would anyone use
but a feature - that kde developers are
>> deliberately working to prevent users from using some programs, including
>> Dolphin as root, as a "security measure".
>>
>> So, can the current version of Dolphin in Debian Stable be run as root
>> (without re-co
ng obvious, but I can not seem to run
> Dolphin or Konqueror as root.
>
> Searching online, I was astounded to see many references to this problem,
> saying that this is not a bug, but a feature - that kde developers are
> deliberately working to prevent users from using some p
, I was astounded to see many references to this problem,
saying that this is not a bug, but a feature - that kde developers are
deliberately working to prevent users from using some programs, including
Dolphin as root, as a "security measure".
So, can the current version of Dolphin in Deb
To date I have not found a way to
> log in my Dolphin package as root. I am using KDE 5.14.5 desktop with
> Debian Buster and an AMD-64 processor.
>
> There are a lot of forum entries telling how to correct the problem on
> Ubuntu but none of them work on Debian (missing software
On 4/3/20 10:08 am, Gary L. Roach wrote:
Thanks for the information. Caja can be started as root. This solves my
problem but it would still be nice if someone could fix the Dolphin
problem.
Perhaps you need to take that to KDE team?
--
Keith Bainbridge
ke1th3...@zoho.com
+61 (0)447 667 468
Thanks for the information. Caja can be started as root. This solves my
problem but it would still be nice if someone could fix the Dolphin problem.
Gary R
On 3/2/20 6:30 AM, Peter Ehlert wrote:
On 3/1/20 11:41 PM, Keith Bainbridge wrote:
On 2/3/20 10:44 am, Peter Ehlert wrote:
If it was
On 3/1/20 11:41 PM, Keith Bainbridge wrote:
On 2/3/20 10:44 am, Peter Ehlert wrote:
If it was me I would just install Pluma and be done with it.
oops, I intended to say caja
I used be a KDE devotee, changed a few years ago.
I use caja as my gui file manager of choice. It has the option
On 2/3/20 10:44 am, Peter Ehlert wrote:
If it was me I would just install Pluma and be done with it.
I used be a KDE devotee, changed a few years ago.
I use caja as my gui file manager of choice. It has the option of dual
pane - allowing you to open source & destination directories.
Or mc
reasons Dolphin was my goto package especially
when copying or moving root files. I understand that the fury over the
above change was so great that the developers backed off. To date I
have not found a way to log in my Dolphin package as root. I am using
KDE 5.14.5 desktop with Debian Buster
Dolphin package as root. I am using KDE 5.14.5 desktop with
Debian Buster and an AMD-64 processor.
There are a lot of forum entries telling how to correct the problem on
Ubuntu but none of them work on Debian (missing software packages).
Can anyone tell me how to setup Dolphin for root use
J'ai eu le problème en ouvrant un Dolphin en root (dans la configuration
du menus KDE dans Avancé, Exécuter en tant qu’utilisateur différent,
avec root).
Lors du démarrage, je saisie le mot de passe root (je ne veux pas
activer le sudo) et la fenêtre "kdesu" du mot de passe gel. Ça
fo
41 matches
Mail list logo
