Quoting Didier Kryn (k...@in2p3.fr):
> However, in general, in situations where vision is the most use
> sense, colour is the prefered method to draw attention, not only on
> computers. It is very apropriate on the command line because it does
> not change the syntax of what is written, exactl
Le 24/09/2017 à 05:08, Rick Moen a écrit :
Quoting Didier Kryn (k...@in2p3.fr):
Well, I think we've got a comprehensive review of the strategies
used to remind the user s?he's acting as root, and they all rely on
colour.
The '#' character is a colour? ;->
No, of course, thanks for no
On Thu, Sep 21, 2017 at 11:12:19AM -0400, Renaud (Ron) OLGIATI wrote:
> Under Debian, I could su to root in a console, and launch gparted from the
> CLI.
>
> Now, I get:
>
> ron@ron:~/Desktop $ su
> Password:
> No protocol specified
> xmodmap: unable to open display ':0.0'
Try this:
xhost
Vernon, yours are also useful links, but I'm trying to find (and I have 2708
emails in my dng Mutt maildir folder) to what email you acually replied... So
first let me try to get your links in the right thread... By giving it an
"In-Reply-To:" header that will get it in place...
Pls. see below why
Quoting Didier Kryn (k...@in2p3.fr):
> Well, I think we've got a comprehensive review of the strategies
> used to remind the user s?he's acting as root, and they all rely on
> colour.
The '#' character is a colour? ;->
___
Dng mailing list
Dng@lis
On Sat, Sep 23, 2017 at 09:45:04PM +0200, Didier Kryn wrote:
> Means you must have one terminal profile for every location you ssh to.
> And you forbid yourself to use su or ssh from the command line, because this
> doesn't change the color scheme of the terminal.
~/.bashrc gets re-run on su,
> On Sep 23, 2017, at 4:52 AM, Renaud (Ron) OLGIATI
> wrote:
>
> On Fri, 22 Sep 2017 23:35:37 -0700
> Rick Moen wrote:
>
>> What a pity there isn't a visual indicator that you are weilding root
>> authority like, I don't know, maybe the bash shell prompt ending
>> character changing from "$"
Le 23/09/2017 à 22:26, Renaud (Ron) OLGIATI a écrit :
Changing PS1 in the relevant .bashrc changes colours both in XFCE-console and
in tty
Yes. But this isn't what Steve does. He changes the colour profile
of the xterm, depending of what command he wants to run.
__
Le 23/09/2017 à 21:56, Steve Litt a écrit :
On Sat, 23 Sep 2017 21:45:04 +0200
Didier Kryn wrote:
Le 23/09/2017 à 20:20, Steve Litt a écrit :
What a pity there isn't a visual indicator that you are weilding
root authority like, I don't know, maybe the bash shell prompt
ending character changi
On Sat, 23 Sep 2017 21:45:04 +0200
Didier Kryn wrote:
> And you forbid yourself to use su or ssh from the command line,
> because this doesn't change the color scheme of the terminal.
? ? ? ?
Changing PS1 in the relevant .bashrc changes colours both in XFCE-console and
in tty
Cheers,
Ron
On Sat, 23 Sep 2017 21:45:04 +0200
Didier Kryn wrote:
> Le 23/09/2017 à 20:20, Steve Litt a écrit :
> >> What a pity there isn't a visual indicator that you are weilding
> >> root authority like, I don't know, maybe the bash shell prompt
> >> ending character changing from "$" to "#".
> > That'
Le 23/09/2017 à 20:20, Steve Litt a écrit :
What a pity there isn't a visual indicator that you are weilding root
authority like, I don't know, maybe the bash shell prompt ending
character changing from "$" to "#".
That's not enough for me. When I open a terminal intended to be either
root or on
Le 23/09/2017 à 19:58, Miroslav Rovis a écrit :
(as further above) only if targetpw is also set...
Think I've got it now :-)
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
On Fri, 22 Sep 2017 23:35:37 -0700
Rick Moen wrote:
> Quoting Hendrik Boom (hend...@topoi.pooq.com):
>
> > The problem with su is that you may forget you are superuser and
> > start doing dangerous things,
> >
> > That's it.
>
> What a pity there isn't a visual indicator that you are weildin
On 170923-19:39+0200, Antoine wrote:
> On Sat, Sep 23, 2017 at 03:12:23PM +, Miroslav Rovis wrote:
> > (...)
> >
> > Anybody got a quick tips page somewhere to find the exact color codes? Else
> > I'm
> > out of the discussion for now. Too much effort... (and other work awaiting
> > me,
> >
Also a reply by Renaud, further in bottom (with the color codes! :-) )
On 170923-18:50+0200, Didier Kryn wrote:
> Le 23/09/2017 à 16:54, Miroslav Rovis a écrit :
The targetpw, three lines below is key to understanding my query that I posted
regarding the ability to forget the root password when i
On Sat, Sep 23, 2017 at 03:12:23PM +, Miroslav Rovis wrote:
> (...)
>
> Anybody got a quick tips page somewhere to find the exact color codes? Else
> I'm
> out of the discussion for now. Too much effort... (and other work awaiting me,
> I'm not lazy, but resources of mind energy not limitless
Le 23/09/2017 à 17:12, Miroslav Rovis a écrit :
But I'll need to take a deep breath to figure out the nice Bash lines
that you sent to the list. :-)
I didn't invent this totally; i picked it from some default Debian
.bashrc years ago. I bet you can still find at least part of it in the
de
Le 23/09/2017 à 16:54, Miroslav Rovis a écrit :
(Also replying to Didier Kryn, because it is related to my question put
following Edward email below, however, too much Edward's text missing in
Didier's reply.)
On 170923-09:15+0200, Edward Bartolo wrote:
Quote: "He's actually right: the least th
t; Find this wrong notion engraved, (lets put it mildly), in the comment at
> > line
> > 45 of:
> >
> > /etc/skel/.bashrc
> >
...
> > but it will be available in the www.mail-archives.com, right after the
> > message
> > to which I'm replying:
(Also replying to Didier Kryn, because it is related to my question put
following Edward email below, however, too much Edward's text missing in
Didier's reply.)
On 170923-09:15+0200, Edward Bartolo wrote:
> Quote: "He's actually right: the least the superuser's password is
> used, the better
> an
else
color_prompt=
fi
fi
And they read like the above in mine /etc/skel/.bashrc .
Attaching the /etc/skel/.bashrc as _bashrc.gz . It likely won't get to the
Lurker archives, attachments are not allowed in, other than text attachments,
but it will be available in the www.mai
On Sat, 23 Sep 2017 13:50:31 +
Miroslav Rovis wrote:
> Useful. But in which file do you stick it, you didn't say? ~/.bashrc ?
I stick the root ones in the relevant /root/.bashrc, and in ~/.bashrc for the
user.
Cheers,
Ron.
--
If God didn't want women to be looked at,
lor_prompt=yes
else
color_prompt=
fi
fi
And they read like the above in mine /etc/skel/.bashrc .
Attaching the /etc/skel/.bashrc as _bashrc.gz . It likely won't get to the
Lurker archives, attachments are not allowed in, other than text attachments,
but it will be available in t
On Sat, 23 Sep 2017 06:28:30 -0700
Rick Moen wrote:
> > If the '#' and "root@hostname" escape the attention of a person
> > entrusted with root privileges, then why not make the root prompt bright
> > red:
> >
> > root@ratatosk:/home/erik# export PS1="\[\033[1;31m\]\u@\h:\W\$
> > \[\033[0;0m\]
Quoting Erik Christiansen (dva...@internode.on.net):
> If the '#' and "root@hostname" escape the attention of a person
> entrusted with root privileges, then why not make the root prompt bright red:
>
> root@ratatosk:/home/erik# export PS1="\[\033[1;31m\]\u@\h:\W\$ \[\033[0;0m\]"
It's a very goo
Le 23/09/2017 à 08:49, Alessandro Selli a écrit :
He's actually right: the least the superuser's password is used, the better
and the safer.
Yep, you can invoke 'sudo su -l'; that's su without the root
password. It helps you forget the root password.
Didier
_
Le 23/09/2017 à 01:56, Hendrik Boom a écrit :
he problem with su is that you may forget you are superuser and start
doing dangerous things,
Edit the .bashrc of root to have the prompt written in red. That's
what I always do. Yet it is still dangerous.
You can make exactly the same da
Le 22/09/2017 à 18:51, Hector Gonzalez a écrit :
On 09/22/2017 05:10 AM, Didier Kryn wrote:
Le 22/09/2017 à 01:32, Arnt Karlsen a écrit :
You can probably justify 'xhost +' if this is one of those
I'm-the-only-user machines. Thank Ghu, remote network access to the X
server is no longer enabl
On 23.09.17 10:15, Arnt Karlsen wrote:
> ..I still miss and prefer the S.u.S.E.-5.2 way, root had a
> nice red background color in xterms, fairly hard to miss.
If the '#' and "root@hostname" escape the attention of a person
entrusted with root privileges, then why not make the root prompt bright
On Fri, 22 Sep 2017 23:35:37 -0700
Rick Moen wrote:
> What a pity there isn't a visual indicator that you are weilding root
> authority like, I don't know, maybe the bash shell prompt ending
> character changing from "$" to "#".
>
> It could work. Somebody should try it, some time.
I run xfce-
Le 22/09/2017 à 13:30, Arnt Karlsen a écrit :
On Fri, 22 Sep 2017 13:03:07 +0200, Arnt wrote in message
<20170922130307.25f57...@nb6.lan>:
On Thu, 21 Sep 2017 16:44:47 -0700, Rick wrote in message
<20170921234447.gp11...@linuxmafia.com>:
Quoting Arnt Karlsen (a...@iaksess.no):
..my prefecen
Le 22/09/2017 à 12:31, Renaud (Ron) OLGIATI a écrit :
On Fri, 22 Sep 2017 12:19:51 +0200
Didier Kryn wrote:
However, for at least a decade, the launcher of Synaptic, in
Debian, has been invoking gksu. Certainly some other sysadmin commands
were using it also, but synaptic is the one I mo
Arnt Karlsen wrote:
>> What a pity there isn't a visual indicator that you are weilding root
>> authority like, I don't know, maybe the bash shell prompt ending
>> character changing from "$" to "#".
>>
>> It could work. Somebody should try it, some time.
:D
> ..I still miss and prefer the S.
On Fri, 22 Sep 2017 23:35:37 -0700, Rick wrote in message
<20170923063536.gx11...@linuxmafia.com>:
> Quoting Hendrik Boom (hend...@topoi.pooq.com):
>
> > The problem with su is that you may forget you are superuser and
> > start doing dangerous things,
> >
> > That's it.
>
> What a pity there
On Thu, 21 Sep 2017 at 12:18:54 -0400
"Renaud (Ron) OLGIATI" wrote:
> On Thu, 21 Sep 2017 16:33:23 +0100
> KatolaZ wrote:
>
>> you probably just need to `xhost +` from the "regular" user account
>> before su-ing. By default the current display is not accessible by any
>> user except the one who
Quote: "He's actually right: the least the superuser's password is
used, the better
and the safer."
Granted, but sudo as configured in Ubuntu makes the use of a superuser
password pointless. Sudo is configured to be a wide wide open door
leading to any part of a computer's 'household'. In other wo
On Fri, 22 Sep 2017 at 19:56:27 -0400
Hendrik Boom wrote:
> On Fri, Sep 22, 2017 at 06:27:59AM +0100, KatolaZ wrote:
>> On Thu, Sep 21, 2017 at 09:41:08PM +0100, Dave Turner wrote:
>>
>> [cut]
>>
>>> The bottle of wine isn't quite finished yet, but I am not trying to
>>> force anyone to stop us
On Thu, 21 Sep 2017 at 20:12:40 +0100
Rowland Penny wrote:
> On Thu, 21 Sep 2017 19:43:54 +0100
> Dave Turner wrote:
>
>>
>> Also, 'su' is just wrong, don't use it, always use sudo, and if you
>> can find a decent .deb of OpenBSD 'doas' ported to linux use that, it
>> is even better!
>>
>
>
Quoting Hendrik Boom (hend...@topoi.pooq.com):
> The problem with su is that you may forget you are superuser and start
> doing dangerous things,
>
> That's it.
What a pity there isn't a visual indicator that you are weilding root
authority like, I don't know, maybe the bash shell prompt ending
On Thu, Sep 21, 2017 at 04:44:47PM -0700, Rick Moen wrote:
>
> This terminology actually confused me for years. I thought "Trusted"
> connections were safer. But actually it's an option you're supposed to
> use in situations where the connection IS trustworthy and you want to
> run stuff w
On Fri, Sep 22, 2017 at 06:27:59AM +0100, KatolaZ wrote:
> On Thu, Sep 21, 2017 at 09:41:08PM +0100, Dave Turner wrote:
>
> [cut]
>
> > The bottle of wine isn't quite finished yet, but I am not trying to force
> > anyone to stop using 'su'.
> >
> > It IS a really bad idea though, rummage the int
On Fri, 22 Sep 2017 11:51:53 -0500
Hector Gonzalez wrote:
> You can also do this, assuming your original user is "user":
> XAUTHORITY=~user/.Xauthority
> export XAUTHORITY
> DISPLAY=:0.0
> export DISPLAY
> and use x with that. You don't add permissions, and there is no need to
> use ssh to forw
Under Devuan ASCII I have no problem running gparted from a terminal
after becoming root with su. Obviously, the xorg must be running
before attempting to run gparted.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/l
On Fri, 22 Sep 2017 08:54:30 -0400, Renaud wrote in message
<20170922085430.0b228...@ron.cerrocora.org>:
> On Fri, 22 Sep 2017 14:31:44 +0200
> Arnt Karlsen wrote:
>
> > > I don't know how one can prevent you from running ssh -X
> > > root@localhost . Permission to do so is set/unset
> >
Quoting Hector Gonzalez (ca...@genac.org):
> You can also do this, assuming your original user is "user":
> XAUTHORITY=~user/.Xauthority
> export XAUTHORITY
> DISPLAY=:0.0
> export DISPLAY
> and use x with that.
Some of us like to do 'ssh -Y root@localhost' because we got tired of
messing around
On 09/22/2017 05:10 AM, Didier Kryn wrote:
Le 22/09/2017 à 01:32, Arnt Karlsen a écrit :
You can probably justify 'xhost +' if this is one of those
I'm-the-only-user machines. Thank Ghu, remote network access to the X
server is no longer enabled by default on Linux hosts. (The right way
to d
On Fri, 22 Sep 2017 14:31:44 +0200
Arnt Karlsen wrote:
> > I don't know how one can prevent you from running ssh -X
> > root@localhost . Permission to do so is set/unset
> > in /etc/ssh/sshd_config .
>
> ..ok, how?
"X11Forwarding yes" ?
Cheers,
Ron.
--
There's no
On Fri, 22 Sep 2017 12:10:37 +0200, Didier wrote in message
<9a258483-ff65-96a3-1ded-5bb121586...@in2p3.fr>:
> Le 22/09/2017 à 01:32, Arnt Karlsen a écrit :
> >> The '-Y' option enables X11 forwarding. (This of course requires
> >> sshd.)
> >>
> >> You can probably justify 'xhost +' if this is o
On Fri, 22 Sep 2017 13:03:07 +0200, Arnt wrote in message
<20170922130307.25f57...@nb6.lan>:
> On Thu, 21 Sep 2017 16:44:47 -0700, Rick wrote in message
> <20170921234447.gp11...@linuxmafia.com>:
>
> > Quoting Arnt Karlsen (a...@iaksess.no):
> >
> > > ..my prefecence was the -X option: ssh -X
On Thu, 21 Sep 2017 16:44:47 -0700, Rick wrote in message
<20170921234447.gp11...@linuxmafia.com>:
> Quoting Arnt Karlsen (a...@iaksess.no):
>
> > ..my prefecence was the -X option: ssh -X root@localhost
> > until Debian killed it with some new policy.
>
> Was it Debian that did that? I was ne
On Fri, 22 Sep 2017 12:19:51 +0200
Didier Kryn wrote:
> However, for at least a decade, the launcher of Synaptic, in
> Debian, has been invoking gksu. Certainly some other sysadmin commands
> were using it also, but synaptic is the one I mostly use.
When you launch it from the GUI, maybe,
Le 22/09/2017 à 11:41, Klaus Ethgen a écrit :
Not true.
That is the job of pam_xauth.so. Just use it as session plugin in pam.
Interesting. Learning everyday, thanks :-)
However, for at least a decade, the launcher of Synaptic, in
Debian, has been invoking gksu. Certainly some other
On Fri, Sep 22, 2017 at 11:37:14AM +0200, Didier Kryn wrote:
> Le 21/09/2017 à 17:12, Renaud (Ron) OLGIATI a écrit :
> >Under Debian, I could su to root in a console, and launch gparted from the
> >CLI.
>
> This could never work. su does not transmit the X connection (don't know
> the details
Le 22/09/2017 à 01:32, Arnt Karlsen a écrit :
The '-Y' option enables X11 forwarding. (This of course requires
sshd.)
You can probably justify 'xhost +' if this is one of those
I'm-the-only-user machines. Thank Ghu, remote network access to the X
server is no longer enabled by default on Linux
On Fri, 22 Sep 2017 11:37:14 +0200
Didier Kryn wrote:
> > Under Debian, I could su to root in a console, and launch gparted from the
> > CLI.
> This could never work. su does not transmit the X connection
I have no idea whether it _could_ work.
But I know it _did_ work. For many years
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
Am Fr den 22. Sep 2017 um 10:37 schrieb Didier Kryn:
> Le 21/09/2017 à 17:12, Renaud (Ron) OLGIATI a écrit :
> > Under Debian, I could su to root in a console, and launch gparted from the
> > CLI.
>
> This could never work. su does not tra
Le 21/09/2017 à 17:12, Renaud (Ron) OLGIATI a écrit :
Under Debian, I could su to root in a console, and launch gparted from the CLI.
This could never work. su does not transmit the X connection (don't
know the details). You got to use gksu or gksudo, or some equivalent
command. With just
On Thu, Sep 21, 2017 at 09:41:08PM +0100, Dave Turner wrote:
[cut]
> The bottle of wine isn't quite finished yet, but I am not trying to force
> anyone to stop using 'su'.
>
> It IS a really bad idea though, rummage the interweb, somewhere in there is
> a really good write up on why su is bad an
Quoting Arnt Karlsen (a...@iaksess.no):
> ..my prefecence was the -X option: ssh -X root@localhost
> until Debian killed it with some new policy.
Was it Debian that did that? I was never sure. I just remember that
'ssh -X' suddenly no longer did X11 forwarding as it used to, but I
looked up the
On Thu, 21 Sep 2017 12:06:40 -0700, Rick wrote in message
<20170921190640.gm11...@linuxmafia.com>:
> Quoting Renaud (Ron) OLGIATI (ren...@olgiati-in-paraguay.org):
>
> > Anything against having `xhost +` in ~/.bashrc ?
>
> Local security, disabling of.
>
> One different method:
>
> $ ssh -Y r
On 21/09/17 21:41, Dave Turner wrote:
On 21/09/17 21:33, Rowland Penny wrote:
On Thu, 21 Sep 2017 21:18:41 +0100
Arnt Gulbrandsen wrote:
Rowland Penny writes:
This is all down to the sysadmins decision and I thought one of the
main ideas behind Devuan is that nothing is forced on the sysadmi
On Thu, 21 Sep 2017 21:41:49 +0100
Arnt Gulbrandsen wrote:
> Rowland Penny writes:
> > Please stop being obtuse, You know very well what I meant.
>
> I do indeed, and I think you're wrong. Devuan has taken a no-systemd
> decision, that's all. That isn't a promise from anyone to provide
> alter
Rowland Penny writes:
Please stop being obtuse, You know very well what I meant.
I do indeed, and I think you're wrong. Devuan has taken a no-systemd
decision, that's all. That isn't a promise from anyone to provide
alternatives in any other question, or to make alternative packages. Not
eve
On 21/09/17 21:33, Rowland Penny wrote:
On Thu, 21 Sep 2017 21:18:41 +0100
Arnt Gulbrandsen wrote:
Rowland Penny writes:
This is all down to the sysadmins decision and I thought one of the
main ideas behind Devuan is that nothing is forced on the sysadmin.
Systemd isn't forced on you. LOTS o
On Thu, 21 Sep 2017 21:18:41 +0100
Arnt Gulbrandsen wrote:
> Rowland Penny writes:
> > This is all down to the sysadmins decision and I thought one of the
> > main ideas behind Devuan is that nothing is forced on the sysadmin.
>
> Systemd isn't forced on you. LOTS of other things are, starting w
Rowland Penny writes:
This is all down to the sysadmins decision and I thought one of the
main ideas behind Devuan is that nothing is forced on the sysadmin.
Systemd isn't forced on you. LOTS of other things are, starting with the
choice of .deb as package format.
Arnt
__
On Thu, 21 Sep 2017 19:43:54 +0100
Dave Turner wrote:
>
> Also, 'su' is just wrong, don't use it, always use sudo, and if you
> can find a decent .deb of OpenBSD 'doas' ported to linux use that, it
> is even better!
>
Just because you think using 'su' is wrong, doesn't make it wrong, it
is jus
Quoting Renaud (Ron) OLGIATI (ren...@olgiati-in-paraguay.org):
> Anything against having `xhost +` in ~/.bashrc ?
Local security, disabling of.
One different method:
$ ssh -Y root@localhost
# gparted &
#
The '-Y' option enables X11 forwarding. (This of course requires sshd.)
You can probably
On Thu, 21 Sep 2017 19:43:54 +0100
Dave Turner wrote:
> Also, 'su' is just wrong, don't use it, always use sudo,
If I wanted to always use sudo I would be running *ubuntu...
Cheers,
Ron.
--
No one can make you feel inferior without your consent.
On 21/09/17 16:41, fsmithred wrote:
On 09/21/2017 11:33 AM, KatolaZ wrote:
On Thu, Sep 21, 2017 at 11:12:19AM -0400, Renaud (Ron) OLGIATI wrote:
Under Debian, I could su to root in a console, and launch gparted from the CLI.
Now, I get:
ron@ron:~/Desktop $ su
Password:
No protocol specified
x
On Thu, 21 Sep 2017 16:33:23 +0100
KatolaZ wrote:
> you probably just need to `xhost +` from the "regular" user account
> before su-ing. By default the current display is not accessible by any
> user except the one who launched it. root is not an exception.
Anything against having `xhost +` in ~
On Thu, 21 Sep 2017 10:39:13 -0500
goli...@dyne.org wrote:
> There was an issue opened up about this 9 months ago:
> https://git.devuan.org/devuan-editors/devuan-art/issues/14
> Devuan alternatives were created specifically for xdm but never
> transferred to the project and repackaged.
OK ta, I'
On 09/21/2017 11:33 AM, KatolaZ wrote:
> On Thu, Sep 21, 2017 at 11:12:19AM -0400, Renaud (Ron) OLGIATI wrote:
>> Under Debian, I could su to root in a console, and launch gparted from the
>> CLI.
>>
>> Now, I get:
>>
>> ron@ron:~/Desktop $ su
>> Password:
>> No protocol specified
>> xmodmap: un
On 2017-09-21 10:12, Renaud (Ron) OLGIATI wrote:
And by the way, logging in under xdm (?) I had a shock when the Debian
name and logo appeared on the login screen...
Cheers,
Ron.
Hi Ron,
There was an issue opened up about this 9 months ago:
https://git.devuan.org/devuan-editors/devuan-art/
On Thu, Sep 21, 2017 at 11:12:19AM -0400, Renaud (Ron) OLGIATI wrote:
> Under Debian, I could su to root in a console, and launch gparted from the
> CLI.
>
> Now, I get:
>
> ron@ron:~/Desktop $ su
> Password:
> No protocol specified
> xmodmap: unable to open display ':0.0'
> No protocol specif
Under Debian, I could su to root in a console, and launch gparted from the CLI.
Now, I get:
ron@ron:~/Desktop $ su
Password:
No protocol specified
xmodmap: unable to open display ':0.0'
No protocol specified
xmodmap: unable to open display ':0.0'
No protocol specified
xmodmap: unable to open
77 matches
Mail list logo