Re: Embarrassing security bug in systemd
On Saturday 09 December 2017 12:01:59 David Wright wrote:
> On Sat 09 Dec 2017 at 11:29:58 (-0500), Gene Heskett wrote:
> > On Saturday 09 December 2017 05:12:16 Joe wrote:
> > > On Fri, 8 Dec 2017 23:56:44 +0000
> > >
> > > Brian <ad44@cityscape.co.uk> wrote:
> > > > On Fri 08 Dec 2017 at 23:06:00 +0000, Joe wrote:
> > > > > On Fri, 8 Dec 2017 17:12:18 -0500
> > > > >
> > > > > Cindy-Sue Causey <butterflybytes@gmail.com> wrote:
> > > > > > I do remember having to give a password, but I don't
> > > > > > remember how long ago now. And I have too much open right
> > > > > > now to test drive whether mine does it or not these days..
> > > > > > :)
> > > > >
> > > > > As I did the other day. I've tried it now (up-to-date
> > > > > unstable) and it works for a non-root user.
> > > >
> > > > Without policykit-1 installed it doesn't; no rebooting or
> > > > powering off with /sbin/reboot or /sbin/poweroff for a user.
> > > > CTRL+ALT+DEL from a terminal reboots. That's the same behaviour
> > > > as sysvinit.
> > >
> > > Yes, I understand that, the point is that the first installation
> > > of policykit-1, which I did not explicitly request, did not ask me
> > > if I wanted non-root users to be able to reboot, or indeed about
> > > anything else it might control. Not that it matters on any of my
> > > machines, I'd just like to have been told that it was changing,
> > > and given the option to keep it as it was had I needed to.
> >
> > Thats another very sore point. Where are the man pages? Its
> > installed on 6, maybe 7 machines here, with zero docs. What the
> > hell? If debian or any other distro decides to shove this crap down
> > our throats, at least have the courtesy of making the docs
> > available. I just searched thru the repo's with synaptic and came up
> > null and empty on polkit-1.
> >
> > So where are the docs?
>
> $ dpkg -L policykit-1 | less
> will reveal what came with the package, and you'll find the
> manpages listed there, about 7 of them.
>
> Cheers,
> David.
I see that David, but when the name is not consistent, it comes across as
yet another attempt to keep it all a secret from those not in the know,
but are just harassed to tears by the effects of this stuff.
In case you hadn't noticed, polkit-1 /= policykit-1 when doing a search.
So lets at least have a consistent name, and a lot of the fire and name
calling will go away simply because we CAN find the docs. And if the
deocs are complete enough, maybe even fix our bitches.
As it exists now, the miss-matched names are seen as nothing but
obfuscation, purposely designed to prevent the users from over-riding
its ill-formed (to us who have been running an all linux house for the
last 19 years, and used Amiga's for a decade before that) rules choices.
Linux is supposedly all about freedom of choice, so give it back to us
instead of having to constantly feed the flame war just to get the info
we need, which is as you are well aware, difficult to do without making
some enemies.
Thank you David, for emitting that bit of information and helping the
rest of us.
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)
Genes Web page <http://geneslinuxbox.net:6309/gene>
Reply to: