Re: [DNG] Xorg, choosing setuid vs. libpam-elogind and rant about security (was: Re: Jessie -> Ascii upgrade breaks X)

2018-06-13 Thread Andreas Messer
On Tue, Jun 12, 2018 at 10:49:35AM -1000, Joel Roth wrote: > Hi Andreas, > > And thanks for the explanations! > > Andreas Messer wrote: > > Hi Joel, > > dd> > On Sat, Jun 09, 2018 at 01:52:06PM -1000, Joel Roth wrote: > > > [...] > > > I have and use dbus apps on my system, However, as far as

Re: [DNG] Xorg, choosing setuid vs. libpam-elogind and rant about security (was: Re: Jessie -> Ascii upgrade breaks X)

2018-06-12 Thread Joel Roth
Hi Andreas, And thanks for the explanations! Andreas Messer wrote: > Hi Joel, > > On Sat, Jun 09, 2018 at 01:52:06PM -1000, Joel Roth wrote: > > [...] > > I have and use dbus apps on my system, However, as far as > > I'm aware, none of these programs has root privileges. > > > > As the

Re: [DNG] Xorg, choosing setuid vs. libpam-elogind and rant about security (was: Re: Jessie -> Ascii upgrade breaks X)

2018-06-12 Thread Peter Vachuska
Thank you for your reply. I should have started by RTFM (or in this case, reading the release notes). I walked away from the computer for two days and on the third day followed the documentation, behold, X ascended to F7 and played nice with screen & byobu & all of the virtual terminals. I

Re: [DNG] Xorg, choosing setuid vs. libpam-elogind and rant about security (was: Re: Jessie -> Ascii upgrade breaks X)

2018-06-11 Thread Andreas Messer
Hi Joel, On Sat, Jun 09, 2018 at 01:52:06PM -1000, Joel Roth wrote: > [...] > I have and use dbus apps on my system, However, as far as > I'm aware, none of these programs has root privileges. > > As the pam/dbus/elogind/polkit mechanism is capable of > handing out root authority, and as all

Re: [DNG] Xorg, choosing setuid vs. libpam-elogind and rant about security (was: Re: Jessie -> Ascii upgrade breaks X)

2018-06-10 Thread KatolaZ
On Sun, Jun 10, 2018 at 11:44:56PM +0200, k...@aspodata.se wrote: > KatolaZ: > > On Sun, Jun 10, 2018 at 11:15:18AM -0500, Peter Vachuska wrote: > ... > > > I know that my setup is atypical and console users won't > > > influence the direction of X. Still > > > Dear Peter, > > > > please

Re: [DNG] Xorg, choosing setuid vs. libpam-elogind and rant about security (was: Re: Jessie -> Ascii upgrade breaks X)

2018-06-10 Thread karl
KatolaZ: > On Sun, Jun 10, 2018 at 11:15:18AM -0500, Peter Vachuska wrote: ... > > I know that my setup is atypical and console users won't > > influence the direction of X. Still > Dear Peter, > > please have a look at the ASCII Release Notes: > >

Re: [DNG] Xorg, choosing setuid vs. libpam-elogind and rant about security (was: Re: Jessie -> Ascii upgrade breaks X)

2018-06-10 Thread Steve Litt
On Sat, 9 Jun 2018 13:52:06 -1000 Joel Roth wrote: > Colleagues! > > Earlier in this thread, we learned that installing xserver-xorg-legacy > allows you to run X the old way, as a setuid script. > > The default upgrade path from jessie -- in which X11 was > setuid-only -- migrates to a new

Re: [DNG] Xorg, choosing setuid vs. libpam-elogind and rant about security (was: Re: Jessie -> Ascii upgrade breaks X)

2018-06-10 Thread Joel Roth
KatolaZ wrote: > please have a look at the ASCII Release Notes: > > https://files.devuan.org/devuan_ascii/Release_notes.txt > > which provide an explanation of the whole X.org matter and of the > solutions available in Devuan ASCII. Thank you (and the author) for this reference. Somehow I'd

Re: [DNG] Xorg, choosing setuid vs. libpam-elogind and rant about security (was: Re: Jessie -> Ascii upgrade breaks X)

2018-06-10 Thread KatolaZ
On Sun, Jun 10, 2018 at 11:15:18AM -0500, Peter Vachuska wrote: > I really wish I had paid more attention to this thread and others warning > about the changes to X before attempting to upgrade to ascii. My preferred > way of working is out of a console running byobu and GNU screen and starting

Re: [DNG] Xorg, choosing setuid vs. libpam-elogind and rant about security (was: Re: Jessie -> Ascii upgrade breaks X)

2018-06-10 Thread fsmithred
On 06/10/2018 12:15 PM, Peter Vachuska wrote: > I really wish I had paid more attention to this thread and others warning > about the changes to X before attempting to upgrade to ascii. My preferred > way of working is out of a console running byobu and GNU screen and starting > X only when

Re: [DNG] Xorg, choosing setuid vs. libpam-elogind and rant about security (was: Re: Jessie -> Ascii upgrade breaks X)

2018-06-10 Thread Peter Vachuska
I really wish I had paid more attention to this thread and others warning about the changes to X before attempting to upgrade to ascii. My preferred way of working is out of a console running byobu and GNU screen and starting X only when needed. This no longer works as both screen and X use

[DNG] Xorg, choosing setuid vs. libpam-elogind and rant about security (was: Re: Jessie -> Ascii upgrade breaks X)

2018-06-09 Thread Joel Roth
Colleagues! Earlier in this thread, we learned that installing xserver-xorg-legacy allows you to run X the old way, as a setuid script. The default upgrade path from jessie -- in which X11 was setuid-only -- migrates to a new xserver-xorg in which the setuid mechanism is replaced. In order to