17 Dec
2015
17 Dec
'15
2:06 p.m.
Greetings;
Out of curiosity, I tried to run ksysv from the tde menu. Can't.
If insists on a root pw that does not exist on this debian wheezy
install. A sudo -i in a konsole for me, and it runs just fine.
This really ought to be fixed. No biggie for me, but...
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Some mill pix are at:
Genes Web page <http://geneslinuxbox.net:6309/gene/GO704-pix>
19 Dec
19 Dec
6:52 a.m.
New subject: [trinity-users] KSysV missfire
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 12/17/2015 03:06 PM, Gene Heskett wrote:
Greetings;
Out of curiosity, I tried to run ksysv from the tde menu. Can't. If insists on a
root pw that does not exist on
this debian wheezy install. A sudo -i in a konsole for me, and it runs just fine.
This really ought to be fixed. No biggie for me, but...
Cheers, Gene Heskett
No issues here (Debian/Stretch) with ksysv. Just typed in the root password and
it worked flawlessly.
The fact that ksysv requires root password is not surprising since you are playing with
the system config.
Cheers
Michele
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCgAGBQJWdP6+AAoJECp1t8qK3tXPjYcP/3wYm63Lg2KxACnAUpZsUvB5
OYC+Rbuam643yuzbatJCfgztmi/ZpUUHjnIEJsoe+DwzWJMVhOvMEK+96U/tEWQ3
20HKwuAtyzspOYAvEv+S0VTHlyFEHaPEBwbnpByETF1Dq7ZREeayCWNKDAO87PGW
N9QcREBKva1CT/szl7bfPLE0GXeeUe/KLs+wNCx08ykBmJeot65MN/fWyNOMEW8w
TehstlqREb7nmjPKv/D9B5bXESeNKHVHfpYoqX7ejbBhh7ad+p5viX6abAmTJCI2
F0cl2MPQDSF1OXowLaHc6XfWvY6VF4aCKyig+pTloLrVFOdgKlasxWs1OsFHHNNA
BGG/DI1rf+tpLZ1Dzy8Rmzh3nb0R2MpoTyoiiJIPPMpJqqc8FPR0Kt9fc2Q7wyIK
RiwVYcbcESD9myMOaZaqHObqFYww1EXr6H0taL9DAJ/hQCNRKqoT3jqSugZiF5CJ
D5GPUNyG/W5eWIYL3ZJbkVuvqq3aU024nDmpjSlcZh7IGnKE0No6jPHUdEic/TSE
LZp9aZgZBzwDCKgISe4CjdcXHSpY4WLAwJYm4m5wXbGtK5zM5YlT+4DDGqTdEdKe
tjyXUroyXTVfJjjgIl/GQNkBWeTfTFE/bn/0sjcDIhexvRCiyi89KJzoa7T5LZk4
t3f7p8brOauSB20PKHj7
=7hYY
-----END PGP SIGNATURE-----
7:22 a.m.
New subject: [trinity-users] KSysV missfire
On Saturday 19 December 2015 01:52:46 Michele Calgaro wrote:
On 12/17/2015 03:06 PM, Gene Heskett wrote:
You missed the point, it demands a root pw, that on this wheezy system,
does not exist, so it cannot be launched from the menu entry by any pw
entered. The pw used for doing a sudo is not accepted. That was my
point.
Don't put it in the menu's at all if the user cannot use his sudo to get
the root rights it needs.
I am used to defeating petty attempts to mold linux networking to
someones idea of consistency, but which is an abject failure where one's
home network, all behind a good router, is all based on the common to
all machines /etc/hosts file, with a locally carved in granite hostname
per machine. Turning network-mangler loose in that environment is a no
networking disaster, so the first thing you have to do on the install
reboot, is sudo -i, make the entry's for that machine
in /etc/network/interfaces, chmod +i that file, then nuke the link and
make a real /etc/resolv.conf, and chmod +i that. If udev hasn't played
with things and moved eth0 to something else, thats it. Your networking
Just Works(TM) Then at your leasure you can uninstall network-mangler.
No use of its burning cpu cycles trying to tear down what you just made
immutible.
Network-mangler might be of use in the situation where the machine is
connected directly to the access modem. Thats for folks who do not
understand the need for an isolating, natting, 20 hungry pit-bull guard
dogs for a firewall, router. Without that, a windows box is owned 30
seconds after the cat5 is plugged in. The linux box is at risk but its
lower. I haven't worried about that since I discovered dd-wrt, which
can be reflashed into the better routers. To me, its a transparent
gateway to the net. To the net, if no port forwarding is being done,
its a cable with an address with nothing on the other end of it.
Greetings;
Out of curiosity, I tried to run ksysv from the tde menu. Can't. If
insists on a root pw that does not exist on this debian wheezy
install. A sudo -i in a konsole for me, and it runs just fine.
This really ought to be fixed. No biggie for me, but...
Cheers, Gene Heskett
No issues here (Debian/Stretch) with ksysv. Just typed in the root
password and it worked flawlessly. The fact that ksysv requires root
password is not surprising since you are playing with the system
config. Cheers
Michele
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-users-unsubscribe(a)lists.pearsoncomputing.net For additional
commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net Read
list messages on the web archive:
http://trinity-users.pearsoncomputing.net/ Please remember not to
top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Some mill pix are at:
Genes Web page <http://geneslinuxbox.net:6309/gene/GO704-pix>
7:42 a.m.
New subject: [trinity-users] KSysV missfire
Hi Gene!
Where's the problem of giving root a password?
nik
Am Samstag, 19. Dezember 2015 schrieb Gene Heskett:
On Saturday 19 December 2015 01:52:46 Michele Calgaro
wrote:
--
Please do not email me anything that you are not comfortable also sharing with the NSA.
Dr. Nikolaus Klepp
Einnehmerstraße 14
A-4810 Gmunden
Tel.: +43 650 82 11 724
email: office(a)klepp.biz
On 12/17/2015 03:06 PM, Gene Heskett wrote:
You missed the point, it demands a root pw, that on this wheezy system,
does not exist, so it cannot be launched from the menu entry by any pw
entered. The pw used for doing a sudo is not accepted. That was my
point.
Don't put it in the menu's at all if the user cannot use his sudo to get
the root rights it needs.
I am used to defeating petty attempts to mold linux networking to
someones idea of consistency, but which is an abject failure where one's
home network, all behind a good router, is all based on the common to
all machines /etc/hosts file, with a locally carved in granite hostname
per machine. Turning network-mangler loose in that environment is a no
networking disaster, so the first thing you have to do on the install
reboot, is sudo -i, make the entry's for that machine
in /etc/network/interfaces, chmod +i that file, then nuke the link and
make a real /etc/resolv.conf, and chmod +i that. If udev hasn't played
with things and moved eth0 to something else, thats it. Your networking
Just Works(TM) Then at your leasure you can uninstall network-mangler.
No use of its burning cpu cycles trying to tear down what you just made
immutible.
Network-mangler might be of use in the situation where the machine is
connected directly to the access modem. Thats for folks who do not
understand the need for an isolating, natting, 20 hungry pit-bull guard
dogs for a firewall, router. Without that, a windows box is owned 30
seconds after the cat5 is plugged in. The linux box is at risk but its
lower. I haven't worried about that since I discovered dd-wrt, which
can be reflashed into the better routers. To me, its a transparent
gateway to the net. To the net, if no port forwarding is being done,
its a cable with an address with nothing on the other end of it.
Greetings;
Out of curiosity, I tried to run ksysv from the tde menu. Can't. If
insists on a root pw that does not exist on this debian wheezy
install. A sudo -i in a konsole for me, and it runs just fine.
This really ought to be fixed. No biggie for me, but...
Cheers, Gene Heskett
No issues here (Debian/Stretch) with ksysv. Just typed in the root
password and it worked flawlessly. The fact that ksysv requires root
password is not surprising since you are playing with the system
config. Cheers
Michele
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-users-unsubscribe(a)lists.pearsoncomputing.net For additional
commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net Read
list messages on the web archive:
http://trinity-users.pearsoncomputing.net/ Please remember not to
top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Cheers, Gene Heskett
8:08 a.m.
New subject: [trinity-users] KSysV missfire
On Saturday 19 December 2015 02:42:50 Dr. Nikolaus Klepp wrote:
Hi Gene!
Where's the problem of giving root a password?
nik
The last time I did that, somewhere along about the time of fedora 2, it
destroyed sudo, and I then rebooted single and nuked it, expecting sudo
to come back, but it didn't so reinstall time. I was sick of being Red
Hat's lab rat always suffering from some redhat experiment you couldn't
get fixed, so I used my lappy to pull and burn the cd and bailed to
mandrake, then pclos for a while, but it wasn't at all compatible with
linuxcnc, so I finally went with wheezy for transparent compatibility.
In that regard it has been truly excellent since the latest LCNC is
wheezy based.
Thank deity I had already setup a decent backup (amanda), so the
transistions between distro's, while not painless, has not cost me a lot
of data in the long view.
However, since they want sudo to be used, leaving root passwordless, I
am not fussy as long as it works. But I am not going to set a root PW if
its going to screw up the rest of the stuff that expects sudo to work.
Am Samstag, 19. Dezember 2015 schrieb Gene Heskett:
> On Saturday 19 December 2015 01:52:46 Michele Calgaro wrote:
> > On 12/17/2015 03:06 PM, Gene Heskett wrote:
> > > Greetings;
> > >
> > > Out of curiosity, I tried to run ksysv from the tde menu.
> > > Can't. If insists on a root pw that does not exist on this
> > > debian wheezy install. A sudo -i in a konsole for me, and it
> > > runs just fine.
> > >
> > > This really ought to be fixed. No biggie for me, but...
> > >
> > > Cheers, Gene Heskett
> >
> > No issues here (Debian/Stretch) with ksysv. Just typed in the
> > root password and it worked flawlessly. The fact that ksysv
> > requires root password is not surprising since you are playing
> > with the system config. Cheers
> > Michele
>
> You missed the point, it demands a root pw, that on this wheezy
> system, does not exist, so it cannot be launched from the menu entry
> by any pw entered. The pw used for doing a sudo is not accepted.
> That was my point.
>
> Don't put it in the menu's at all if the user cannot use his sudo to
> get the root rights it needs.
>
> I am used to defeating petty attempts to mold linux networking to
> someones idea of consistency, but which is an abject failure where
> one's home network, all behind a good router, is all based on the
> common to all machines /etc/hosts file, with a locally carved in
> granite hostname per machine. Turning network-mangler loose in that
> environment is a no networking disaster, so the first thing you have
> to do on the install reboot, is sudo -i, make the entry's for that
> machine
> in /etc/network/interfaces, chmod +i that file, then nuke the link
> and make a real /etc/resolv.conf, and chmod +i that. If udev hasn't
> played with things and moved eth0 to something else, thats it. Your
> networking Just Works(TM) Then at your leasure you can uninstall
> network-mangler. No use of its burning cpu cycles trying to tear
> down what you just made immutible.
>
> Network-mangler might be of use in the situation where the machine
> is connected directly to the access modem. Thats for folks who do
> not understand the need for an isolating, natting, 20 hungry
> pit-bull guard dogs for a firewall, router. Without that, a windows
> box is owned 30 seconds after the cat5 is plugged in. The linux box
> is at risk but its lower. I haven't worried about that since I
> discovered dd-wrt, which can be reflashed into the better routers.
> To me, its a transparent gateway to the net. To the net, if no port
> forwarding is being done, its a cable with an address with nothing
> on the other end of it.
>
> > ------------------------------------------------------------------
> >--- To unsubscribe, e-mail:
> > trinity-users-unsubscribe(a)lists.pearsoncomputing.net For
> > additional commands, e-mail:
> > trinity-users-help(a)lists.pearsoncomputing.net Read list messages
> > on the web archive:
> > http://trinity-users.pearsoncomputing.net/ Please remember not to
> > top-post:
> > http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
>
> Cheers, Gene Heskett
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Some mill pix are at:
Genes Web page <http://geneslinuxbox.net:6309/gene/GO704-pix>
8:33 a.m.
New subject: [trinity-users] KSysV missfire
Am Samstag, 19. Dezember 2015 schrieb Gene Heskett:
--
Please do not email me anything that you are not comfortable also sharing with the NSA.
On Saturday 19 December 2015 02:42:50 Dr. Nikolaus
Klepp wrote:
Hi Gene!
There are no side effects in setting a root password. In fact, there is already a root
password, but it's useless for the user.
If you want to try:
$ sudo bash
# cp /etc/shadow /root/
# passwd
If you have sideffects using sudo, you can always do:
$ su
# cp /root/shadow /etc/
Nik
Hi Gene!
Where's the problem of giving root a password?
nik
The last time I did that, somewhere along about the time of fedora 2, it
destroyed sudo, and I then rebooted single and nuked it, expecting sudo
to come back, but it didn't so reinstall time. I was sick of being Red
Hat's lab rat always suffering from some redhat experiment you couldn't
get fixed, so I used my lappy to pull and burn the cd and bailed to
mandrake, then pclos for a while, but it wasn't at all compatible with
linuxcnc, so I finally went with wheezy for transparent compatibility.
In that regard it has been truly excellent since the latest LCNC is
wheezy based.
Thank deity I had already setup a decent backup (amanda), so the
transistions between distro's, while not painless, has not cost me a lot
of data in the long view.
However, since they want sudo to be used, leaving root passwordless, I
am not fussy as long as it works. But I am not going to set a root PW if
its going to screw up the rest of the stuff that expects sudo to work. Am Samstag, 19. Dezember 2015 schrieb Gene
Heskett:
> On Saturday 19 December 2015 01:52:46 Michele Calgaro wrote:
> > On 12/17/2015 03:06 PM, Gene Heskett wrote:
> > > Greetings;
> > >
> > > Out of curiosity, I tried to run ksysv from the tde menu.
> > > Can't. If insists on a root pw that does not exist on this
> > > debian wheezy install. A sudo -i in a konsole for me, and it
> > > runs just fine.
> > >
> > > This really ought to be fixed. No biggie for me, but...
> > >
> > > Cheers, Gene Heskett
> >
> > No issues here (Debian/Stretch) with ksysv. Just typed in the
> > root password and it worked flawlessly. The fact that ksysv
> > requires root password is not surprising since you are playing
> > with the system config. Cheers
> > Michele
>
> You missed the point, it demands a root pw, that on this wheezy
> system, does not exist, so it cannot be launched from the menu entry
> by any pw entered. The pw used for doing a sudo is not accepted.
> That was my point.
>
> Don't put it in the menu's at all if the user cannot use his sudo to
> get the root rights it needs.
>
> I am used to defeating petty attempts to mold linux networking to
> someones idea of consistency, but which is an abject failure where
> one's home network, all behind a good router, is all based on the
> common to all machines /etc/hosts file, with a locally carved in
> granite hostname per machine. Turning network-mangler loose in that
> environment is a no networking disaster, so the first thing you have
> to do on the install reboot, is sudo -i, make the entry's for that
> machine
> in /etc/network/interfaces, chmod +i that file, then nuke the link
> and make a real /etc/resolv.conf, and chmod +i that. If udev hasn't
> played with things and moved eth0 to something else, thats it. Your
> networking Just Works(TM) Then at your leasure you can uninstall
> network-mangler. No use of its burning cpu cycles trying to tear
> down what you just made immutible.
>
> Network-mangler might be of use in the situation where the machine
> is connected directly to the access modem. Thats for folks who do
> not understand the need for an isolating, natting, 20 hungry
> pit-bull guard dogs for a firewall, router. Without that, a windows
> box is owned 30 seconds after the cat5 is plugged in. The linux box
> is at risk but its lower. I haven't worried about that since I
> discovered dd-wrt, which can be reflashed into the better routers.
> To me, its a transparent gateway to the net. To the net, if no port
> forwarding is being done, its a cable with an address with nothing
> on the other end of it.
>
> > ------------------------------------------------------------------
> >--- To unsubscribe, e-mail:
> > trinity-users-unsubscribe(a)lists.pearsoncomputing.net For
> > additional commands, e-mail:
> > trinity-users-help(a)lists.pearsoncomputing.net Read list messages
> > on the web archive:
> > http://trinity-users.pearsoncomputing.net/ Please remember not to
> > top-post:
> > http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
>
> Cheers, Gene Heskett
Cheers, Gene Heskett
1:39 p.m.
New subject: [trinity-users] KSysV missfire
On Saturday 19 December 2015 03:33:17 Dr. Nikolaus Klepp wrote:
Am Samstag, 19. Dezember 2015 schrieb Gene Heskett:
Which from a very dim recall at this late date, is not how I did it
before. And this time it appears to be working well, no surprises.
Now I just have to remember to try the root pw if mine doesn't work. Both
are long enough that typu's can be a problem. But roots is like 16
characters longer. As it should be.
Thanks Nik.
On Saturday 19 December 2015 02:42:50 Dr.
Nikolaus Klepp wrote:
Hi Gene!
There are no side effects in setting a root password. In fact, there
is already a root password, but it's useless for the user.
If you want to try:
$ sudo bash
# cp /etc/shadow /root/
# passwd Hi Gene!
Where's the problem of giving root a password?
nik
The last time I did that, somewhere along about the time of fedora
2, it destroyed sudo, and I then rebooted single and nuked it,
expecting sudo to come back, but it didn't so reinstall time. I was
sick of being Red Hat's lab rat always suffering from some redhat
experiment you couldn't get fixed, so I used my lappy to pull and
burn the cd and bailed to mandrake, then pclos for a while, but it
wasn't at all compatible with linuxcnc, so I finally went with
wheezy for transparent compatibility. In that regard it has been
truly excellent since the latest LCNC is wheezy based.
Thank deity I had already setup a decent backup (amanda), so the
transistions between distro's, while not painless, has not cost me a
lot of data in the long view.
However, since they want sudo to be used, leaving root
passwordless, I am not fussy as long as it works. But I am not going
to set a root PW if its going to screw up the rest of the stuff that
expects sudo to work. If you have sideffects using sudo, you can always do:
$ su
# cp /root/shadow /etc/
Nik
> > Am Samstag, 19. Dezember 2015 schrieb Gene Heskett:
> > > On Saturday 19 December 2015 01:52:46 Michele Calgaro wrote:
> > > > On 12/17/2015 03:06 PM, Gene Heskett wrote:
> > > > > Greetings;
> > > > >
> > > > > Out of curiosity, I tried to run ksysv from the tde menu.
> > > > > Can't. If insists on a root pw that does not exist on this
> > > > > debian wheezy install. A sudo -i in a konsole for me, and it
> > > > > runs just fine.
> > > > >
> > > > > This really ought to be fixed. No biggie for me, but...
> > > > >
> > > > > Cheers, Gene Heskett
> > > >
> > > > No issues here (Debian/Stretch) with ksysv. Just typed in the
> > > > root password and it worked flawlessly. The fact that ksysv
> > > > requires root password is not surprising since you are playing
> > > > with the system config. Cheers
> > > > Michele
> > >
> > > You missed the point, it demands a root pw, that on this wheezy
> > > system, does not exist, so it cannot be launched from the menu
> > > entry by any pw entered. The pw used for doing a sudo is not
> > > accepted. That was my point.
> > >
> > > Don't put it in the menu's at all if the user cannot use his
> > > sudo to get the root rights it needs.
> > >
> > > I am used to defeating petty attempts to mold linux networking
> > > to someones idea of consistency, but which is an abject failure
> > > where one's home network, all behind a good router, is all based
> > > on the common to all machines /etc/hosts file, with a locally
> > > carved in granite hostname per machine. Turning network-mangler
> > > loose in that environment is a no networking disaster, so the
> > > first thing you have to do on the install reboot, is sudo -i,
> > > make the entry's for that machine
> > > in /etc/network/interfaces, chmod +i that file, then nuke the
> > > link and make a real /etc/resolv.conf, and chmod +i that. If
> > > udev hasn't played with things and moved eth0 to something else,
> > > thats it. Your networking Just Works(TM) Then at your leasure
> > > you can uninstall network-mangler. No use of its burning cpu
> > > cycles trying to tear down what you just made immutible.
> > >
> > > Network-mangler might be of use in the situation where the
> > > machine is connected directly to the access modem. Thats for
> > > folks who do not understand the need for an isolating, natting,
> > > 20 hungry pit-bull guard dogs for a firewall, router. Without
> > > that, a windows box is owned 30 seconds after the cat5 is
> > > plugged in. The linux box is at risk but its lower. I haven't
> > > worried about that since I discovered dd-wrt, which can be
> > > reflashed into the better routers. To me, its a transparent
> > > gateway to the net. To the net, if no port forwarding is being
> > > done, its a cable with an address with nothing on the other end
> > > of it.
> > >
> > > > --------------------------------------------------------------
> > > >---- --- To unsubscribe, e-mail:
> > > > trinity-users-unsubscribe(a)lists.pearsoncomputing.net For
> > > > additional commands, e-mail:
> > > > trinity-users-help(a)lists.pearsoncomputing.net Read list
> > > > messages on the web archive:
> > > > http://trinity-users.pearsoncomputing.net/ Please remember not
> > > > to top-post:
> > > > http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
> > >
> > > Cheers, Gene Heskett
>
> Cheers, Gene Heskett
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Some mill pix are at:
Genes Web page <http://geneslinuxbox.net:6309/gene/GO704-pix>
10:21 a.m.
New subject: [trinity-users] KSysV missfire
Hi Gene
You missed the point, it demands a root pw, that on
this wheezy system,
does not exist, so it cannot be launched from the menu entry by any pw
entered. The pw used for doing a sudo is not accepted. That was my
point.
Don't put it in the menu's at all if the user cannot use his sudo to get
the root rights it needs.
what happens, if you do - if you are allowed to start su from sudo:
xhost + # to allow other users to access the xserver
sudo su # to become root without a password
export DISPLAY=:0 # set the DISPLAY variable to access the xserver
ksysv # start the wanted program
If this works, you can use the program without a password.
HTH
Rolf
1:12 p.m.
New subject: [trinity-users] KSysV missfire
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 2015/12/19 11:21 AM, Rolf Schmidt wrote:
You missed the point, it demands a root pw, that on
this wheezy system,
> does not exist, so it cannot be launched from the menu entry by any pw entered. The
pw used for doing a sudo is
> not accepted. That was my point.
Again, I see nothing wrong on a general
basis.
If you are root (yes, not recommended I know) there is no problem to run ksysv at all.
If you are a standard user, you type in the root password and everything works.
If your setup does not use a root password or you do not have access to such password,
you have the choice to edit the menu and remove the ksysv entry.
IMHO, the menu entry is fine as it is now since it will work as expected for the majority
of the users.
Unconventional setups will need special handling for this type of problem.
Just my 2 cents
Cheers
Michele
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCgAGBQJWdVepAAoJECp1t8qK3tXPMaUQAKLyK/VJolV5bJBZby/QovAh
XAKuo7L41Q6XF9k1TV7cGDzOTiiTP+xH8dPXdYaK93OCUxCI5S/JxgOzcFBBZveX
Qf08D0oejRnF4kTTYlwS65PXlKwwa8IoIWm3yWEPWn+z6P1Eb8WANupqFd5dAMRT
tx6Yrl+arolMsLV7PYhKV9xH/G4SzmMCQEioia9Xx+OklY9WFiX2zzSDBpNnN88z
NkSdK8P9Fr/LnRtpI6X+Ty+H2dCaH6hAV6jBKE1FpiS5TPaRk+1Myp5gguka5CCC
f4wAaVqbkguSUSYu7XjHxi59MjQfoDpqRt5f0hpY0LsGRUkhyRZdbRqyCRNZZkUl
Ddl5BdI+ipo1X5TWch9G0lI825IbL8VhKNxfkROrWynKBOv6X25MogTsLgH6kESU
1E39oZJ3DjxpuEowJkzAbVRLjZaVND0EwlzXcd6sIWBDRliZM79lwzQR4PvVmrrk
vrw4cYBEkApKcX2Y9DaLIPWyIw9rhVHLWdR/ZAnmvh6fdIcszG3WyYhukH9yuTQs
7XUw2wa5eb1NsAiUuyCh8Tr5FeQDKkNGsAhuJHTllYqHyN3Kiu9SAHitPtxPv1t5
lo8pYfgJfF74gYmyJBlHx2bR3/VgGbl3K46jWgSdhhHIKAG0Bv3bI9sKNYPy/Q+q
IfxithHgrw8tuu9XfKsG
=+CB4
-----END PGP SIGNATURE-----
1:55 p.m.
New subject: [trinity-users] KSysV missfire
On Saturday 19 December 2015 08:12:09 Michele Calgaro wrote:
On 2015/12/19 11:21 AM, Rolf Schmidt wrote:
debian wheezy has never had a root passwd known to the user. Unless they
follow Nik's proceedure to reset it. It does exist, but is not known to
the first user, so there rather effectively is not one as far as that
first user who has sudo rights is concerned.
You missed the point, it demands a root pw, that
on this wheezy
system,
> does not exist, so it cannot be launched from the menu entry by any
> pw entered. The pw used for doing a sudo is not accepted. That
> was my point.
Again, I see nothing wrong on a general basis.
If you are root (yes, not recommended I know) there is no problem to
run ksysv at all. If you are a standard user, you type in the root
password and everything works.
If your setup does not use a root password or you do not have access
to such password, you have the choice to edit the menu and remove the
ksysv entry. IMHO, the menu entry is fine as it is now since it
will work as
expected for the majority of the users.
Your idea of the word majority is miss-applied in the modern linux world.
Root password usage is pretty well deprecated by most distro's today,
using sudo instead, even in wheezy which is considered elderly these
days.
Unconventional setups will
need special handling for this type of problem. Just my 2 cents
Cheers
Michele
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-users-unsubscribe(a)lists.pearsoncomputing.net For additional
commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net Read
list messages on the web archive:
http://trinity-users.pearsoncomputing.net/ Please remember not to
top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Some mill pix are at:
Genes Web page <http://geneslinuxbox.net:6309/gene/GO704-pix>
3:16 p.m.
New subject: [trinity-users] KSysV missfire
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 12/19/2015 02:55 PM, Gene Heskett wrote:
Your idea of the word majority is miss-applied in the
modern linux world. Root password usage is pretty well
deprecated by most distro's today, using sudo instead, even in wheezy which is
considered elderly these days.
You are probably right on this, I agree. Now I see
the point you were trying to make.
I will discuss with Slavek, see what he thinks too.
Cheers
Michele
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCgAGBQJWdXTiAAoJECp1t8qK3tXPAvUP/RB7q/sjQfAhcps0BxUahnN2
VSLRVhtQMnjXR5W63R3tuBafjZa1RZYl/E7TiJ1/hJjzW2lCLIBd+tC+kHBG//KQ
uayWgtZaSgMTSD3cxTumLKin9Squos74dRWKQ5eOgMGW6mhXxOKtr/V9vTsqCPtr
MMX9xWE6WAuxkJswN0TTJzKBss06FGyKFgNPGs5QkWLzUKIrvHsCVpmz4XeJUzt5
KRA2YjOUbipBRtLaXKxrZXNZUwwtZcAR3GVvlp4hKfGzMOYDDHZHUKPKYxCg0jI4
plp+hoqASJoPvjwBwOaLk/mgAobCMqsqNzPjqKRzIwyDj7yNqxIp+7EiTKeqn/lk
oxEQo1qTpe8I6QdyuRWfMNyNoOH7PNXfT4+zq5Sj5Ydiv6Xvfn0do1XL0UtA8y4W
se3VW5ka8ry+dGz3RF2xIJxFug/4AS43gZyzXU4HicKnZAkzlAFlANU55wBLsaBl
8Z4veYiE1FMMLTBTAMPbkJCmd+VVFNvv+6lW4iMctisXuRS6tgSkMPTMJcGjTkZG
P2/g3eCZziWMIVXONhbdJ3+PtKS77Ewm2cC0trf1NI4TM6sTUydtNkuNaXoSUCPC
DldXWjWfJhIPaT6JZPe+zBaesiPpyquoQwFafrcCVOgGZWqkfPxT/w/Dytv2JLNa
cSK8bbXQL+mN9+6VioAv
=z/c+
-----END PGP SIGNATURE-----
4:17 p.m.
New subject: [trinity-users] KSysV missfire
On Saturday 19 December 2015 10:16:51 Michele Calgaro wrote:
On 12/19/2015 02:55 PM, Gene Heskett wrote:
Thank you, Michele
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Some mill pix are at:
Genes Web page <http://geneslinuxbox.net:6309/gene/GO704-pix>
Your idea of the word majority is miss-applied in
the modern linux
world. Root password usage is pretty well deprecated by most
distro's today, using sudo instead, even in wheezy which is
considered elderly these days.
You are probably right on this, I agree. Now I see the point you were
trying to make. I will discuss with Slavek, see what he thinks too.
Cheers
Michele
4:50 p.m.
New subject: [trinity-users] KSysV missfire
On Saturday 19 December 2015 10:16:51 Michele Calgaro wrote:
On 12/19/2015 02:55 PM, Gene Heskett wrote:
I should also add that synaptic is in this same boat, and that until I
discovered synaptic-pkexec from a cli, which uses sudo to get its
rights, I was locked out of using the best package manager ever.
update-manager is nice, and it runs well with a sudo, but it cannot add
a new package one might need. adept, with its fugly ncurses gui that is
so easily destroyed, could probably be used by someone familiar with the
ncurses idiosynchrocies I suppose, but ncurses has had 20 years to grow
a screen refresh and hasn't done it yet. mc, if ncurses grew a screen
refresh would be hands down the best file manager ever. krusader looks
nice, but is impotent. As it is, the only way to refresh mc is to quit
it and restart it.
That leaves synaptic as a universal package manager, which because of its
x integration cannot be run as root (can't access the display as root)
but sudo the pkexec wrapper and its beautifull. And I just edited the
menu item so it can be run from the menu. Except it doesn't run at all
now, and logs no errors. But it still works from the cli. Take out the
single quotes the editor so helpfully added, and it runs, but takes the
newly added root pw. Can we get any more confused? Doubtful.
There are no doubt several other "system set it once and forget it"
things, but those are a few of the things that bug me weekly if not more
often.
Thanks Michele
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Some mill pix are at:
Genes Web page <http://geneslinuxbox.net:6309/gene/GO704-pix>
Your idea of the word majority is miss-applied in
the modern linux
world. Root password usage is pretty well deprecated by most
distro's today, using sudo instead, even in wheezy which is
considered elderly these days.
You are probably right on this, I agree. Now I see the point you were
trying to make. I will discuss with Slavek, see what he thinks too.
Cheers
Michele
5:19 p.m.
New subject: [trinity-users] KSysV missfire
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
I should also add that synaptic is in this same boat,
and that until I discovered synaptic-pkexec from a cli, which
uses sudo to get its rights, I was locked out of using the best package manager ever.
Gene,
although which one is the best package manager is quite subjective (for example aptitude
is my favorite),
I have discussed with Slavek about the sudo-TDE MEnu issue.
Can you file a bug report in bugszilla about this problem? Make sure to add bug 2540 to
the "Blocks" field so that the
new bug is added to the r14.0.3 bug list.
Thanks
Michele
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCgAGBQJWdZGdAAoJECp1t8qK3tXPbaYQANDG7HNI8J9YilhcuxZdcDbG
aFz/1pbyuyN3eolU0OTDI9OjHq04IXC0H02xRFflqWj5wMIY7GeLjWd1+MendIs5
3k6Gl0+WP5OonaDs4yXNzmrhIQFg61IPc5TRje6cpHDiQOj6ZzcbnCd4z+SjuHQ9
hlrxaoVkq76eZSMC8PgtrHIRqzoyQYY8KZl9Q9e8/+hxNDFj2Ga1bYFbZzYMQV+/
y389WzeIZ5UkEkSTTGUJvZfXZu/wre/58tARuNIQzCQ96ZhoG2+54V2meUd00nKl
m1zebpOgk0XMCgiEu/fOqs9fogUQt3QEZWZ6i8NfrJCbDxuvQjkOMlR49pNf3u9h
t/TX0Vo2jXr/JkSGL7D918HMQd8yR+aCHm5tZTe+qYrMaYDfbqach/1jhDRH9HwO
nHk02PiFr/8oC0bibvy03YLQG/PeVjb0f6G5sUP0hq2XWum1wio6kf5a/i5cm8DD
20KYHYDtJ74zM2p6qwXAqVx4DQ6rKn7w1XfviYHxShJaXeUJHvzUKto99RCBSVBW
oc05NWUqL4cT1R6KtxdxpPWSYB+6zN+Fa4NOq/OPbYnoDhrwu9rbZrlzdti4HNHI
1hmqM+llkeXcuaHxsbfABMNPWBcsj7TC2s9oBngtxvYUUA7pq+z2MNnrNtAqjQjX
rYmda5qmkRbGW/kfYTjI
=Eqkm
-----END PGP SIGNATURE-----
10:29 p.m.
New subject: [trinity-users] KSysV missfire
On Saturday 19 December 2015 12:19:25 Michele Calgaro wrote:
ISTR I did register there at some point a month+ back up the log. But I
don't recall the username or pw. I asked it to send me a pw reset, but
it went to the pw reset screen, where its still sitting, and I have not
received the reset message in something like 10 minutes, eg 3 fetchmail
cycles.
Next?
Thanks Michele
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Some mill pix are at:
Genes Web page <http://geneslinuxbox.net:6309/gene/GO704-pix>
I should also
add that synaptic is in this same boat, and that until
I discovered synaptic-pkexec from a cli, which uses sudo to get its
rights, I was locked out of using the best package manager ever.
Gene,
although which one is the best package manager is quite subjective
(for example aptitude is my favorite), I have discussed with Slavek
about the sudo-TDE MEnu issue.
Can you file a bug report in bugszilla about this problem? Make sure
to add bug 2540 to the "Blocks" field so that the new bug is added to
the r14.0.3 bug list.
Thanks
Michele
20 Dec
20 Dec
12:10 p.m.
New subject: [trinity-users] KSysV missfire
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 12/19/2015 11:29 PM, Gene Heskett wrote:
ISTR I did register there at some point a month+ back
up the log. But I don't recall the username or pw. I asked
it to send me a pw reset, but it went to the pw reset screen, where its still sitting,
and I have not received the
reset message in something like 10 minutes, eg 3 fetchmail cycles.
Next?
Thanks Michele
Cheers, Gene Heskett
For the records, I filed bug 2563 for this problem. The
comment is the same you put in bug 2540 ;-)
Cheers
Michele
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCgAGBQJWdpqcAAoJECp1t8qK3tXPHPIP/2KD1I27fbuNwmq0LFynQYyr
SwMfGAMM3Ns0qDz4GuBZH6r4NxGyD5xViEVKDpnTM1Mbvoowy9ADXCylumK4tvau
VE6835WNFhyrRd6pAvCR3SziIwOw0PQ1soUc8Rk0Vq/LI9GakG3BkysV9LzgBFo+
DIgr0ZHFZk0a779uL7SmaEeqaBmtS53BhAT8vV3ypChzSBSTpcIoY0wbB2/12AKa
i/fp8hmViRZ2tUNTu0Pp0UyLSn69zkVcVBTyJcPqevep3GX57mnIfP/pvlaLtPBk
z8WDDjiMJuz5CCJI2YAtv1QmOkN3yr60Ywp+VAz/Uj9zImEzifKurvfoaRU9Vnld
PvJPCRul49BanNj0i77d/H14dPNZbLYUj5zJVl54Rp5MOi8dynZuSux20yRXyfW2
pbTLfJsobMdpU/1ywVP19fFUco1OK5g2qg6k3wxZZd1h7B5YG6hVZoyibZO/vKOW
I+ll3StIbjqNtB3boN/+iqdSread6e373/KYTvGZJCFXdPHe2fh6y+bQ6BauBUi3
r+jvmePRRK12W4lM9Q4H5TbPm4+pR/YbKJnFNZinZnQNQWJUEe4DCs2t4LshkohI
WycVoapyJ6BZ7c+sE4QVa7I7WQN+oc+Q1rWjGzE9CFuWsAOjMo70fCm+65FLu0Ly
d1mQ9elAYs9X57Wu0QGw
=pTtq
-----END PGP SIGNATURE-----
19 Dec
19 Dec
7:44 p.m.
New subject: [trinity-users] KSysV missfire
On Saturday 19 December 2015 13:55:41 Gene Heskett wrote:
You are using Debian. It is not deprecated. IMHO this no root password
business is part of the creeping Ubuntuisation.
On Saturday 19 December 2015 08:12:09 Michele Calgaro
wrote:
Rubbish! Rubbish! Rubbish! Debian has always had a root password. If you
haven't got one it is because you aren't using a Wheezy but a CNC or soethnig
one. Debian _has_ started giving the option at install tine of not having one
if you don't want one instead of imposing one on you, but basically Wheezy
has a root password.
On 2015/12/19 11:21 AM, Rolf Schmidt wrote:
debian wheezy has never had a root passwd known to the user. You missed the point, it demands a root pw, that
on this wheezy
system,
> does not exist, so it cannot be launched from the menu entry by any
> pw entered. The pw used for doing a sudo is not accepted. That
> was my point.
Again, I see nothing wrong on a general basis.
If you are root (yes, not recommended I know) there is no problem to
run ksysv at all. If you are a standard user, you type in the root
password and everything works.
If your setup does not use a root password or you do not have access
to such password, you have the choice to edit the menu and remove the
ksysv entry. Unless they
follow Nik's proceedure to reset it. It does exist, but is not known to
the first user, so there rather effectively is not one as far as that
first user who has sudo rights is concerned.
Rubbish again.
IMHO, the menu
entry is fine as it is now since it will work as
expected for the majority of the users.
Your idea of the word majority is miss-applied in the modern linux world.
Root password usage is pretty well deprecated by most distro's today, using sudo instead, even in wheezy
Sorry, Gene, but rubbish!
which is considered elderly these
days.
> Unconventional setups will
> need special handling for this type of problem. Just my 2 cents
Quite Michele. The Debian/TDE combination norm for a setup is to have a root
password. It is not as though those who insist on being different cannot
sort it out easily, as you have Gene. But you could always have used Ubuntu,
which does have sudo for the first user by default. <shudder>
Lisi.
20 Dec
20 Dec
7:54 a.m.
New subject: [trinity-users] KSysV missfire
Am Samstag, 19. Dezember 2015 schrieb Lisi Reisz:
On Saturday 19 December 2015 13:55:41 Gene Heskett
wrote:
You are using Debian. It is not deprecated. IMHO this no root password
business is part of the creeping Ubuntuisation.
Hi Lisi!
Genes problem is indeed a problem of the linuxcnc live cd, which was formerly based on
ubuntu but is now on wheezy. Somebody on the assembly line liked sudo better than su,
which is quite funny. Now when Gene uses the linuxcnc livesystem (or that installed on a
disk) he ends up with wheezy+ubuntu "make it esy"-stuff aka xfcs/sudo/systemd
etc, which makes things qute interesting when you leave the red flaged paths. On the other
hand, you can install linuxcnc on top of wheezy without that clutter, but you'll need
to know where to go :-)
Nik
--
Please do not email me anything that you are not comfortable also sharing with the NSA.
On Saturday 19 December 2015 08:12:09 Michele
Calgaro wrote:
Rubbish! Rubbish! Rubbish! Debian has always had a root password. If you
haven't got one it is because you aren't using a Wheezy but a CNC or soethnig
one. Debian _has_ started giving the option at install tine of not having one
if you don't want one instead of imposing one on you, but basically Wheezy
has a root password.
On 2015/12/19 11:21 AM, Rolf Schmidt wrote:
debian wheezy has never had a root passwd known to the user. You missed the point, it demands a root pw, that
on this wheezy
system,
> does not exist, so it cannot be launched from the menu entry by any
> pw entered. The pw used for doing a sudo is not accepted. That
> was my point.
Again, I see nothing wrong on a general basis.
If you are root (yes, not recommended I know) there is no problem to
run ksysv at all. If you are a standard user, you type in the root
password and everything works.
If your setup does not use a root password or you do not have access
to such password, you have the choice to edit the menu and remove the
ksysv entry. Unless they
follow Nik's proceedure to reset it. It does exist, but is not known to
the first user, so there rather effectively is not one as far as that
first user who has sudo rights is concerned.
Rubbish again.
IMHO, the
menu entry is fine as it is now since it will work as
expected for the majority of the users.
Your idea of the word majority is miss-applied in the modern linux world.
Root password usage is pretty well deprecated by most distro's today, using sudo instead, even in wheezy
Sorry, Gene, but rubbish!
which is considered elderly these
days.
> Unconventional setups will
> need special handling for this type of problem. Just my 2 cents
Quite Michele. The Debian/TDE combination norm for a setup is to have a root
password. It is not as though those who insist on being different cannot
sort it out easily, as you have Gene. But you could always have used Ubuntu,
which does have sudo for the first user by default. <shudder>
Lisi.
10:56 a.m.
New subject: [trinity-users] KSysV missfire
On Sunday 20 December 2015 07:54:59 Dr. Nikolaus Klepp wrote:
Am Samstag, 19. Dezember 2015 schrieb Lisi Reisz:
Thanks, Nik!
Lisi
On Saturday 19 December 2015 13:55:41 Gene
Heskett wrote:
You are using Debian. It is not deprecated. IMHO this no root password
business is part of the creeping Ubuntuisation.
Hi Lisi!
Genes problem is indeed a problem of the linuxcnc live cd, which was
formerly based on ubuntu but is now on wheezy. Somebody on the assembly
line liked sudo better than su, which is quite funny. Now when Gene uses
the linuxcnc livesystem (or that installed on a disk) he ends up with
wheezy+ubuntu "make it esy"-stuff aka xfcs/sudo/systemd etc, which makes
things qute interesting when you leave the red flaged paths. On the other
hand, you can install linuxcnc on top of wheezy without that clutter, but
you'll need to know where to go :-)
Nik On Saturday 19 December 2015 08:12:09 Michele
Calgaro wrote:
Rubbish! Rubbish! Rubbish! Debian has always had a root password. If
you haven't got one it is because you aren't using a Wheezy but a CNC or
soethnig one. Debian _has_ started giving the option at install tine of
not having one if you don't want one instead of imposing one on you, but
basically Wheezy has a root password.
On 2015/12/19 11:21 AM, Rolf Schmidt wrote:
> You missed the point, it demands a root pw, that on this wheezy
> system,
>
>> does not exist, so it cannot be launched from the menu entry by
>> any pw entered. The pw used for doing a sudo is not accepted.
>> That was my point.
Again, I see nothing wrong on a general basis.
If you are root (yes, not recommended I know) there is no problem to
run ksysv at all. If you are a standard user, you type in the root
password and everything works.
If your setup does not use a root password or you do not have access
to such password, you have the choice to edit the menu and remove the
ksysv entry.
debian wheezy has never had a root passwd known to the user. Unless they
follow Nik's proceedure to reset it. It does exist, but is not known to
the first user, so there rather effectively is not one as far as that
first user who has sudo rights is concerned.
Rubbish again.
IMHO, the
menu entry is fine as it is now since it will work as
expected for the majority of the users.
Your idea of the word majority is miss-applied in the modern linux
world. Root password usage is pretty well deprecated by most distro's
today, using sudo instead, even in wheezy
Sorry, Gene, but rubbish!
which is considered elderly these
days.
> Unconventional setups will
> need special handling for this type of problem. Just my 2 cents
Quite Michele. The Debian/TDE combination norm for a setup is to have a
root password. It is not as though those who insist on being different
cannot sort it out easily, as you have Gene. But you could always have
used Ubuntu, which does have sudo for the first user by default.
<shudder>
Lisi. 
10:57 a.m.
New subject: [trinity-users] KSysV missfire
Il 20/12/2015 08:54, Dr. Nikolaus Klepp ha scritto:
Genes problem is indeed a problem of the linuxcnc live
cd
We can all agree that Gene is got a problem, and that it would be nice
to find a solution for his problem.
But as his problem arises from a quite unsafe setting with sudo stuff of
his ubuntuish CNC, I wouldn't like is that, in order to solve Gene's
problem, something is done which might impair safety for everybody else,
as Michele's answer might imply.
Giuliano
11:07 a.m.
New subject: [trinity-users] KSysV missfire
On Sunday 20 December 2015 10:57:42 Giuliano Colla wrote:
Il 20/12/2015 08:54, Dr. Nikolaus Klepp ha scritto:
I was thinking exactly the same, Guiliano, and was going to write saying so.
Making access as easy as that is an accident waiting to happen. I want
things that are system related locked up behind root, and would be very sad
to see this changed in Debian/TDE. This very issue is one of my reasons for
not liking Ubuntu.
And Gene has got, and has applied, a solution to his problem. He just
objected to having to find it.
Lisi
Genes problem is indeed a problem of the linuxcnc
live cd
We can all agree that Gene is got a problem, and that it would be nice
to find a solution for his problem.
But as his problem arises from a quite unsafe setting with sudo stuff of
his ubuntuish CNC, I wouldn't like is that, in order to solve Gene's
problem, something is done which might impair safety for everybody else,
as Michele's answer might imply.
12:16 p.m.
New subject: [trinity-users] KSysV missfire
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 12/20/2015 11:57 AM, Giuliano Colla wrote:
We can all agree that Gene is got a problem, and that
it would be nice to find a solution for his problem.
But as his problem arises from a quite unsafe setting with sudo stuff of his ubuntuish
CNC, I wouldn't like is
that, in order to solve Gene's problem, something is done which might impair safety
for everybody else, as
Michele's answer might imply.
Correct. The idea is to explore a way to give the user a choice between typing the root
password or run a program with
something similar to sudo (tdesudo??).
The solution should be such that by default the root password is required, but for those
users who prefer (or have to)
use sudo, an additional package should be available to overcome the "type the root
password" problem.
Cheers
Michele
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCgAGBQJWdpw5AAoJECp1t8qK3tXPOd4P/0v8Iw7REjUb4/YULxNciHgN
XOfrngEV04KWsIwMqB1+XmfZqB++h5RqxM00eFBJc7P/z61mjMa1+nhzzQQ7CFjF
vtoxYD6GBoVF9jKAJeto2BunNA3VQttasSpsVrmp86szftuA0eW9SqJ2OE0bKvdw
GmzRY9WbQJT4zrvRWXT+15i1gG/flumYFTQz+4r1VnSt2sWhjnJq4YYt7vvjoky7
IipLoH5wTpCKzmML5fmwCn0FIb+xPI5y+tLtr+TO6kdg8l20SEk+4YPhFGapSR2c
XntElZuF/to22596gHT10ul7Ew3JHWwMAFF0ZONVg6zgWJ666y1e5oMt4GDuMjL7
OflrmzfNbQVFS8LFa8bWeCmSDpR4PrMh5vwCAu7rwGRaPldZIZAgErDRhhOdVtoW
DsIx0xNwzK/2aRR4zEgWjRuy8jd8vkB8f7HDzoB/C1AcpHpLHA4Pgpy/eNpqoVZr
K/rTFTOjjTb6lQX3l5y8HMHTvf4MMot/3pdDYVqwn2HuqTIi6G6QQvEnWbz/5qk8
0ga5J0DPbK52Tb3JdDIpB+VN3p3LTrB6ERw0aKB0IrkIK0tLVMxzjLDWXjiqVyqS
58d+LbdK04BkN5gx5ddY6y448cYSuXBar3QsZWNkT7dlYsepX+rblUEiTUHoIY2I
TarrEZ1OOYuXa2tO4ZGd
=LMWX
-----END PGP SIGNATURE-----
3:12 p.m.
New subject: [trinity-users] KSysV missfire
On Sunday 20 December 2015 07:16:57 Michele Calgaro wrote:
On 12/20/2015 11:57 AM, Giuliano Colla wrote:
IMO a separate package should not be needed. To that end, if the package
asks for a pw, and gets the 1st users pw as a response, it should be
happy and run. There is little or no difference between root and 1st
user as 1st user is generally the one who originally setup the system
and should know it well.
I was not aware, until this discussion, that debian did setup a root
passwd, I had assumed that the buntu's inherited the sudo requirement
from debian. I've one other machine that is running a 14.04 lubuntu
LTS, my lappy, and you have my curiosity piqued now, so its booting.
That takes a while as it seems to be convinced it must do an fsck
everytime it boots, on a 100 gig drive. And that transition to sudo for
everything is complete, there is not a passwd hash in the /etc/shadow
file for root.
It probably needs an update session so we'll see what synaptic wants to
install. 4 new packages, 52 to be upgraded. It was last done a couple
weeks ago, so the packagers have been busy. Updates I see include bind9
and grub plus a grocery list of other stuff. A new kernel too IIRC.
So I am learning a bit, and now don't feel so crippled at having to use a
root pw for some stuff. It was actually expected if it was pure debian.
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Some mill pix are at:
Genes Web page <http://geneslinuxbox.net:6309/gene/GO704-pix>
We can all agree that Gene is got a problem, and
that it would be
nice to find a solution for his problem.
But as his problem arises from a quite unsafe setting with sudo
stuff of his ubuntuish CNC, I wouldn't like is that, in order to
solve Gene's problem, something is done which might impair safety
for everybody else, as Michele's answer might imply.
Correct. The idea is to explore a way to give the user a choice
between typing the root password or run a program with something
similar to sudo (tdesudo??).
The solution should be such that by default the root password is
required, but for those users who prefer (or have to) use sudo, an
additional package should be available to overcome the "type the root
password" problem.
Cheers
Michele
3:49 p.m.
New subject: [trinity-users] KSysV missfire
On Sunday 20 December 2015 15:12:17 Gene Heskett wrote:
IMO a separate package should not be needed. To that
end, if the package
asks for a pw, and gets the 1st users pw as a response, it should be
happy and run. There is little or no difference between root and 1st
user as 1st user is generally the one who originally setup the system
and should know it well.
That is what Ubuntu users think, Gene. But Ubuntu is available, as is TDE for
Ubuntu..
I was not aware, until this discussion, that debian
did setup a root
passwd, I had assumed that the buntu's inherited the sudo requirement
from debian.
No, it created it and the infection is spreading into Debian, on the whole
from Ubuntu users who switch. (Like you.)
I've one other machine that is running a 14.04
lubuntu
LTS, my lappy, and you have my curiosity piqued now, so its booting.
That takes a while as it seems to be convinced it must do an fsck
everytime it boots, on a 100 gig drive. And that transition to sudo for
everything is complete, there is not a passwd hash in the /etc/shadow
file for root.
It probably needs an update session so we'll see what synaptic wants to
install. 4 new packages, 52 to be upgraded. It was last done a couple
weeks ago, so the packagers have been busy. Updates I see include bind9
and grub plus a grocery list of other stuff. A new kernel too IIRC.
So I am learning a bit, and now don't feel so crippled at having to use a
root pw for some stuff. It was actually expected if it was pure debian.
Quite!! And some of us really want it. ;-)
Lisi
4:13 p.m.
New subject: [trinity-users] KSysV missfire
On Sunday 20 December 2015 10:49:56 Lisi Reisz wrote:
On Sunday 20 December 2015 15:12:17 Gene Heskett
wrote:
TBT Lisi, it has been handy here, even if I too failed to grok the reason
for it years ago when the *buntu's first started it. Like most, if I set
a root pw, it is going to be a considerably longer, mixed case and
alphanumeric string I can remember. Let them spend a few hundred years
using a dictionary attack at 10x/second being the operative theory...
That MIGHT get them thru the router, but then they have to get to the
machines.
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Some mill pix are at:
Genes Web page <http://geneslinuxbox.net:6309/gene/GO704-pix>
IMO a separate package should not be needed. To
that end, if the
package asks for a pw, and gets the 1st users pw as a response, it
should be happy and run. There is little or no difference between
root and 1st user as 1st user is generally the one who originally
setup the system and should know it well.
That is what Ubuntu users think, Gene. But Ubuntu is available, as is
TDE for Ubuntu..
I was not aware, until this discussion, that
debian did setup a root
passwd, I had assumed that the buntu's inherited the sudo
requirement from debian.
No, it created it and the infection is spreading into Debian, on the
whole from Ubuntu users who switch. (Like you.)
I've one other machine that is running a
14.04 lubuntu
LTS, my lappy, and you have my curiosity piqued now, so its booting.
That takes a while as it seems to be convinced it must do an fsck
everytime it boots, on a 100 gig drive. And that transition to sudo
for everything is complete, there is not a passwd hash in the
/etc/shadow file for root.
It probably needs an update session so we'll see what synaptic wants
to install. 4 new packages, 52 to be upgraded. It was last done a
couple weeks ago, so the packagers have been busy. Updates I see
include bind9 and grub plus a grocery list of other stuff. A new
kernel too IIRC.
So I am learning a bit, and now don't feel so crippled at having to
use a root pw for some stuff. It was actually expected if it was
pure debian.
Quite!! And some of us really want it. ;-)
Lisi
5:27 p.m.
New subject: [trinity-users] KSysV missfire
On Sunday 20 December 2015 16:13:57 Gene Heskett wrote:
Like most, if I set
a root pw, it is going to be a considerably longer, mixed case and
alphanumeric string I can remember.
I don't get this. Yes, I have a strong root password. But my user has no
access. Your user can use his password. Do:
$ sudo -s
enter user's password
and have full root privileges. Why does root's password need to be stronger,
since the user has full root privileges???
Lisi
7:28 p.m.
New subject: [trinity-users] KSysV missfire
On Sunday 20 December 2015 12:27:48 Lisi Reisz wrote:
On Sunday 20 December 2015 16:13:57 Gene Heskett
wrote:
Good question Lisi, one I've yet to hear a good explanation for from the
bunto folks, and I did ask a couple times in the past. Should I make the
pw I use just as obtuse & long?
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Some mill pix are at:
Genes Web page <http://geneslinuxbox.net:6309/gene/GO704-pix>
Like most, if I set
a root pw, it is going to be a considerably longer, mixed case and
alphanumeric string I can remember.
I don't get this. Yes, I have a strong root password. But my user
has no access. Your user can use his password. Do:
$ sudo -s
enter user's password
and have full root privileges. Why does root's password need to be
stronger, since the user has full root privileges???
Lisi
9:19 p.m.
New subject: [trinity-users] KSysV missfire
On Sunday 20 December 2015 19:28:42 Gene Heskett wrote:
On Sunday 20 December 2015 12:27:48 Lisi Reisz wrote:
Yes!!!
Lisi
On Sunday 20 December 2015 16:13:57 Gene Heskett
wrote:
Good question Lisi, one I've yet to hear a good explanation for from the
bunto folks, and I did ask a couple times in the past. Should I make the
pw I use just as obtuse & long? Like most, if I set
a root pw, it is going to be a considerably longer, mixed case and
alphanumeric string I can remember.
I don't get this. Yes, I have a strong root password. But my user
has no access. Your user can use his password. Do:
$ sudo -s
enter user's password
and have full root privileges. Why does root's password need to be
stronger, since the user has full root privileges???
Lisi 
9:32 p.m.
New subject: [trinity-users] KSysV missfire
On Sunday 20 December 2015 22.19:06 Lisi Reisz wrote:
Yes!!!
Lisi
While this has nothing to do with TDE, that is my main reason for sticking to
the "old" user/root system. Windows users mostly don't use a superuser
(although they could) because it's "complicated". Mac users "have no
root",
but that means that if they use an easy password (I should not say, but I
can't move my wife from 654321 ...), anyone having access to their computer
can turn root on and lock them out.
Same with Linux: if I can easily guess someone's user password and he has sudo
rights, then sudo passwd root and sudo passwd <user>: I'm the boos and he's
out.
So, as long as sudo users don't use strong password (and most I know
_don't_ ), a separate root password is more secure.
Thierry
Why does root's password need to be
stronger, since the user has full root privileges???
Lisi
Good question Lisi, one I've yet to hear a good explanation for from the
bunto folks, and I did ask a couple times in the past. Should I make the
pw I use just as obtuse & long?
11:25 p.m.
New subject: [trinity-users] KSysV missfire
On Sunday 20 December 2015 21:32:41 Thierry de Coulon wrote:
So, as long as sudo users don't use strong
password (and most I know
_don't_ ), a separate root password is more secure.
I'm equally worried about the things that sudo users can and do do to
themselves because it is so easy!
Lisi
21 Dec
21 Dec
8:26 a.m.
New subject: [trinity-users] KSysV missfire
Am Montag, 21. Dezember 2015 schrieb Lisi Reisz:
On Sunday 20 December 2015 21:32:41 Thierry de Coulon
wrote:
If user can do "sudo bash" - which he can in most cases - then the whole
"security improvement by sudo" is pure illusion.
Nik
--
Please do not email me anything that you are not comfortable also sharing with the NSA.
So, as long as sudo users don't use strong
password (and most I know
_don't_ ), a separate root password is more secure.
I'm equally worried about the things that sudo users can and do do to
themselves because it is so easy!
Lisi
12:41 a.m.
New subject: [trinity-users] KSysV missfire
On Sunday 20 December 2015 21:32:41 Thierry de Coulon wrote:
if I can easily guess someone's user password and
he has sudo
rights, then sudo passwd root and sudo passwd <user>: I'm the boos and
he's out.
(Sorry, misquoted last time.)
I'm equally worried about the things that sudo users can and do do to
themselves because it is so easy!
Lisi
So, as long as sudo users don't use strong password (and most I know
_don't_ ), a separate root password is more secure.
1:58 a.m.
New subject: [trinity-users] KSysV missfire
On Sun, Dec 20, 2015 at 02:28:42PM -0500, Gene Heskett wrote:
Good question Lisi, one I've yet to hear a good
explanation for from the
bunto folks, and I did ask a couple times in the past. Should I make the
pw I use just as obtuse & long?
That depends on what sort of threats you may face.
If you have unrestricted sudo rights, then access to your account is
just as good as access to root. Possibly even more so, since your
account might have access to resources on other machines that root
doesn't.
Or an attacker might use an unpatched exploit to steal root access, even
without sudo rights. But even without root access, access to your
account alone may be valuable to the attacker.
If the attacker thinks of you as just another machine on the Internet,
then they can still use your machine to (say) store files, launch
attacks on others, maliciously delete or encrypt files (ransomware),
send spam, go through your address books and emails looking for other
accounts to attack, steal unencrypted passwords from your web browser
and get access to your on-line banking, social media and "cloud"-based
systems. From which they can steal your money, send spam, or launch
attacks on others -- emailed malware is *much* more effective when it
comes from a person you trust.
If they are specifically targetting *you*, or somebody you know, they
can invade your privacy, stalk you or your friends/family, perform
industrial espionage, or frame you for possession of illegal material
such as child pornography or terrorist-related material. Root access not
required.
Consider that attacks are not necessarily over the internet. Are you
living alone, or sharing a flat with four total strangers? Do you take
your computer into the shop to get repairs done? How well do you trust
them?
--
Steve
20 Dec
20 Dec
5:32 p.m.
New subject: [trinity-users] KSysV missfire
On Sun, 20 Dec 2015 10:12:17 -0500
Gene Heskett <gheskett(a)shentel.net> wrote:
To that end, if the package
asks for a pw, and gets the 1st users pw as a response, it should be
happy and run. There is little or no difference between root and 1st
user as 1st user is generally the one who originally setup the system
and should know it well.
Don't assume that all systems are single-user desktops. Your
suggested setup isn't sufficient, for instance, to handle a multi-user
system that's just gotten a new administrator, as might happen in
a corporate environment. Once the old admin's account is scrubbed,
the original "first user" isn't there anymore, so where should the rights
end up? The next user added probably wasn't the new admin, and
the new admin shouldn't have to use someone else's login name.
TDE shouldn't allow behaviour that sudo doesn't (assuming that
sudo is even present on the system--it's quite possible to use su
only and never install sudo!), which seems to be what you're
advocating here. It does have to be able to be able to authenticate
via sudo with user passwords if the system accepts that behaviour
in other contexts.
Regardless, I expect Michele et al. will do The Right Thing.
E. Liddell
6:37 p.m.
New subject: [trinity-users] KSysV missfire
On Sunday 20 December 2015 17:32:41 E. Liddell wrote:
And don't assume, as you clearly do, that the "first user" is the one who
set
up the system. This can get very confusing where one is administering
someone else's machine. At least, I tend to end up very confused.
Just as you are used to Ubuntu-think, I am used to Debian think. First user
is just the user you set up first - after root. ;-)
To that end,
if the package
asks for a pw, and gets the 1st users pw as a response, it should be
happy and run. There is little or no difference between root and 1st
user as 1st user is generally the one who originally setup the system
and should know it well.
Don't assume that all systems are single-user desktops. TDE shouldn't allow behaviour that sudo
doesn't (assuming that
sudo is even present on the system--it's quite possible to use su
only and never install sudo!), which seems to be what you're
advocating here. It does have to be able to be able to authenticate
via sudo with user passwords if the system accepts that behaviour
in other contexts.
The problem is that Gene's system is a mish-mash, with sudo a left-over from
Ubuntu; and most of those of us who are using pure Debian don't want this
behaviour. Michele's suggested compromise, of being able to add an extra
package if you want it, appears to be a good one.
Lisi
7:41 p.m.
New subject: [trinity-users] KSysV missfire
On Sunday 20 December 2015 12:32:41 E. Liddell wrote:
On Sun, 20 Dec 2015 10:12:17 -0500
Gene Heskett <gheskett(a)shentel.net> wrote:
Here, that is precisely the case. Any other "users" are there only to
separate rights, like nut and amanda.
To that end, if the package
asks for a pw, and gets the 1st users pw as a response, it should be
happy and run. There is little or no difference between root and 1st
user as 1st user is generally the one who originally setup the
system and should know it well.
Don't assume that all systems are single-user desktops. Your
suggested setup isn't sufficient, for instance, to handle a multi-user
system that's just gotten a new administrator, as might happen in
a corporate environment. Once the old admin's account is scrubbed,
the original "first user" isn't there anymore, so where should the
rights end up? The next user added probably wasn't the new admin, and
the new admin shouldn't have to use someone else's login name.
Violent agreement there.
OTOH, other than rebooting single and having the new admin set both his
pw, and roots, and change the username in the /etc/sudoers file if it
exists, should not be locked out. The machine may have valuable data on
it that would be lost if a re-install was forced. OTOH, if the new
admin doesn't know how to do the above, he is not qualified to admin any
*nix machine. If they need the data bad enough, they WILL find an admin
that is capable of installing himself.
TDE shouldn't allow behaviour that sudo doesn't (assuming that
sudo is even present on the system--it's quite possible to use su
only and never install sudo!), which seems to be what you're
advocating here. It does have to be able to be able to authenticate
via sudo with user passwords if the system accepts that behaviour
in other contexts.
Regardless, I expect Michele et al. will do The Right Thing.
E. Liddell
No arguements there as the Right Thing must include the multiuser
scenario, which doesn't exist in terms of live users here. Thats my
problem, not yours. All I want is consistency in applying the must use
root rules. Since this is obviously a mixed system, its something I'll
have to put up with in the grand scheme of things.
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-users-unsubscribe(a)lists.pearsoncomputing.net For additional
commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net Read
list messages on the web archive:
http://trinity-users.pearsoncomputing.net/ Please remember not to
top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Some mill pix are at:
Genes Web page <http://geneslinuxbox.net:6309/gene/GO704-pix>
19 Dec
19 Dec
7:45 p.m.
New subject: [trinity-users] KSysV missfire
Il 19/12/2015 14:55, Gene Heskett ha scritto:
Your idea of the word majority is miss-applied in the
modern linux world.
Root password usage is pretty well deprecated by most distro's today,
using sudo instead, even in wheezy which is considered elderly these
days.
The method suggested by Rolf Schmidt to overcome your problem
demonstrates that it's something as unsafe as can be imagined. Anybody
can get root privileges without a password.
Letting any user do anything just by typing sudo before a command is a
rather peculiar way of implementing security, be it the old Wheezy, or
the newer Ubuntu (and its siblings).
Just my 2 c.
Giuliano
10:22 p.m.
New subject: [trinity-users] KSysV missfire
On Saturday 19 December 2015 19:45:14 Giuliano Colla wrote:
Letting any user do anything just by typing sudo
before a command is a
rather peculiar way of implementing security, be it the old Wheezy, or
the newer Ubuntu (and its siblings).
Hear, hear. I know someone who upgraded to the next version of Ubuntu from
an LTS version,*by* *mistake*. Thereby kyboshing her most necessary piece of
professional software.
There are indeed some convincing arguments for having sudo, with limited
privileges, available in a multi user environment, but in a single user
environment, where that single user has full root privileges available as
sudo, it is a disaster waiting to happen.."Most people", when asked to input
their password do so automatically without thinking. If asked for root's
password, they do at least have to think.
Lisi
1:47 p.m.
New subject: [trinity-users] KSysV missfire
On Saturday 19 December 2015 05:21:42 Rolf Schmidt wrote:
Hi Gene
Would that not be considered a security hole you could drive a 65 foot
refer with 88,000 lbs of swinging beef thru, on a cooked spaghetti
WV/USA road? (its the only kind of roads we have here in West Virginia)
It sure would to me. But folks call me paranoid too.
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Some mill pix are at:
Genes Web page <http://geneslinuxbox.net:6309/gene/GO704-pix>
You missed the point, it demands a root pw, that
on this wheezy
system, does not exist, so it cannot be launched from the menu entry
by any pw entered. The pw used for doing a sudo is not accepted.
That was my point.
Don't put it in the menu's at all if the user cannot use his sudo to
get the root rights it needs.
what happens, if you do - if you are allowed to start su from sudo:
xhost + # to allow other users to access the xserver
sudo su # to become root without a password
export DISPLAY=:0 # set the DISPLAY variable to access the xserver
ksysv # start the wanted program
If this works, you can use the program without a password.
HTH
Rolf
3289
days inactive
3293
days old
38 comments
9 participants
participants (9)
-
Dr. Nikolaus Klepp -
E. Liddell -
Gene Heskett -
Giuliano Colla -
Lisi Reisz -
Michele Calgaro -
Rolf Schmidt -
Steven D'Aprano -
Thierry de Coulon