Re: Embarrassing security bug in systemd

2017-12-09 Thread Jonathan Dowland
On Fri, Dec 08, 2017 at 03:31:54PM -0500, Gene Heskett wrote: On Friday 08 December 2017 14:26:41 Jonathan Dowland wrote: No objection there, and I agree that the release notes should probably have covered the policy changes. That ship has now sailed unfortunately. So now, no effort will ever

Re: Embarrassing security bug in systemd

2017-12-09 Thread Jonathan Dowland
On Fri, Dec 08, 2017 at 07:57:03PM +, Brian wrote: That's a good point. Not really. systemd doesn't stop providing a single place to define a consistent policy because a set of users do not use it. That's not the point I thought was good: the point is, in Debian, systemd is optional. As a

Re: Embarrassing security bug in systemd

2017-12-09 Thread Jonathan Dowland
On Sat, Dec 09, 2017 at 01:30:17AM +, Glenn English wrote: Even if there's an error in the release note? Less than optimal way to run a train. Errors and omissions are different things. I'm not responsible for release notes but I suspect if there was something that was glaringly false, it *

Re: Embarrassing security bug in systemd

2017-12-09 Thread tomas
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, Dec 08, 2017 at 05:04:51PM -0600, John Hasler wrote: > tomas writes: > > Not a fan of systemd here (have outed myself this way clearly enough, > > I think), but systemd is pretty well documented, for sure. > > Is the Debian default configurati

Re: Embarrassing security bug in systemd

2017-12-09 Thread Joe
On Sat, 09 Dec 2017 01:46:59 + Mark Fletcher wrote: > The OP has never been seen again since the original post. Just > sayin’... > > Because he accidentally discovered a new feature, thought it was a bug, and was immediately corrected. End of story. We've been discussing the 'accidentally'

Re: Embarrassing security bug in systemd

2017-12-09 Thread Brian
On Sat 09 Dec 2017 at 07:52:56 +, Jonathan Dowland wrote: > On Fri, Dec 08, 2017 at 07:57:03PM +, Brian wrote: > > > That's a good point. > > > > Not really. systemd doesn't stop providing a single place to define a > > consistent policy because a set of users do not use it. > > That's n

Re: Embarrassing security bug in systemd

2017-12-09 Thread Joe
On Fri, 8 Dec 2017 23:56:44 + Brian wrote: > On Fri 08 Dec 2017 at 23:06:00 +, Joe wrote: > > > On Fri, 8 Dec 2017 17:12:18 -0500 > > Cindy-Sue Causey wrote: > > > > > > > > I do remember having to give a password, but I don't remember how > > > long ago now. And I have too much ope

Re: Filter logcheck reboot messages?

2017-12-09 Thread Jeremy Nicoll
On Sat, 9 Dec 2017, at 01:19, Richard Hector wrote: > Nobody else uses logcheck? Everyone is fine with how it works? Can't say... but having never heard of it I googled it, found my way to the project page and its mail-lists, and noticed that there's been hardly any traffic there for years. On

Re: Embarrassing security bug in systemd

2017-12-09 Thread Brian
On Sat 09 Dec 2017 at 10:12:16 +, Joe wrote: > On Fri, 8 Dec 2017 23:56:44 + > Brian wrote: > > > On Fri 08 Dec 2017 at 23:06:00 +, Joe wrote: > > > > > On Fri, 8 Dec 2017 17:12:18 -0500 > > > Cindy-Sue Causey wrote: > > > > > > > > > > > I do remember having to give a password

Re: on-screen artifacts (red pixels) at high resolution with Intel HD 630 (Kaby Lake)

2017-12-09 Thread Alexandre Rossi
> Screenshot [1] looks normal to me, but on screenphoto [2] I clearly see > red-ish stripes and pink spots in the middle. > > Now it looks like your LCD could be faulty not PC hardware\software. Can you > test it with another LCD monitor, or connect it to TV via HDMI cable if it's > possible? The

Re: Filter logcheck reboot messages?

2017-12-09 Thread Sven Hartge
Richard Hector wrote: > Nobody else uses logcheck? Everyone is fine with how it works? I use logcheck on all systems and I see no need to change it. In fact, I *want* the reboot messages and filtering them out would be a regression for me. Grüße, Sven. -- Sigmentation fault. Core dumped.

Re: Filter logcheck reboot messages?

2017-12-09 Thread Ulf Volmer
On 09.12.2017 15:37, Sven Hartge wrote: > Richard Hector wrote: > >> Nobody else uses logcheck? Everyone is fine with how it works? > > I use logcheck on all systems and I see no need to change it. In fact, I > *want* the reboot messages and filtering them out would be a regression > for me. Ag

Re: on-screen artifacts (red pixels) at high resolution with Intel HD 630 (Kaby Lake)

2017-12-09 Thread David Wright
On Sat 09 Dec 2017 at 15:35:18 (+0100), Alexandre Rossi wrote: > > Screenshot [1] looks normal to me, but on screenphoto [2] I clearly see > > red-ish stripes and pink spots in the middle. > > > > Now it looks like your LCD could be faulty not PC hardware\software. Can you > > test it with another

Re: Embarrassing security bug in systemd

2017-12-09 Thread Ric Moore
On 12/08/2017 05:12 PM, Cindy-Sue Causey wrote: Something I did *not* understand when I saw it in operation was why a password was needed at the terminal but not from within the GUI's "Applications > Log Out" menu path. Thank you Cindy, now I don't have to point out the obvious! :) Ric -- My

Re: Filter logcheck reboot messages?

2017-12-09 Thread Sven Hartge
Ulf Volmer wrote: > On 09.12.2017 15:37, Sven Hartge wrote: >> Richard Hector wrote: >>> Nobody else uses logcheck? Everyone is fine with how it works? >> >> I use logcheck on all systems and I see no need to change it. In >> fact, I *want* the reboot messages and filtering them out would be a

Re: on-screen artifacts (red pixels) at high resolution with Intel HD 630 (Kaby Lake)

2017-12-09 Thread Benny Simonsen
The image with errors looks as it was manipulated in a photoeditor, eg. Gamma/levels curves ... Does the driver have some image adjustment enabled?

Re: Embarrassing security bug in systemd

2017-12-09 Thread Tom Furie
On Sat, Dec 09, 2017 at 10:17:45AM -0500, Ric Moore wrote: > On 12/08/2017 05:12 PM, Cindy-Sue Causey wrote: > > Something I did *not* understand when I saw it in operation was why > > a password was needed at the terminal but not from within the GUI's > > "Applications > Log Out" menu path. > > T

Re: Embarrassing security bug in systemd

2017-12-09 Thread David Wright
On Fri 08 Dec 2017 at 18:30:08 (-0800), Jimmy Johnson wrote: > On 12/07/2017 02:31 AM, Jonathan Dowland wrote: > >On Thu, Dec 07, 2017 at 10:02:56AM +, Tixy wrote: > >>I'm running Jessie (with systemd running but booting with sysvinit) and > >>trying to execute halt/poweroff/reboot/shutdown fro

Re: Embarrassing security bug in systemd

2017-12-09 Thread Gene Heskett
On Saturday 09 December 2017 05:12:16 Joe wrote: > On Fri, 8 Dec 2017 23:56:44 + > > Brian wrote: > > On Fri 08 Dec 2017 at 23:06:00 +, Joe wrote: > > > On Fri, 8 Dec 2017 17:12:18 -0500 > > > > > > Cindy-Sue Causey wrote: > > > > I do remember having to give a password, but I don't reme

Re: Embarrassing security bug in systemd

2017-12-09 Thread David Wright
On Sat 09 Dec 2017 at 10:17:45 (-0500), Ric Moore wrote: > On 12/08/2017 05:12 PM, Cindy-Sue Causey wrote: > Something I did *not* understand when I saw it in > >operation was why a password was needed at the terminal but not from > >within the GUI's "Applications > Log Out" menu path. > > Thank

Re: Embarrassing security bug in systemd

2017-12-09 Thread David Wright
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 + > > > > Brian wrote: > > > On Fri 08 Dec 2017 at 23:06:00 +, Joe wrote: > > > > On Fri, 8 Dec 2017 17:12:18 -0500 > > > > > > > > Cindy-Sue Ca

Re: Embarrassing security bug in systemd

2017-12-09 Thread Jonathan Dowland
On Sat, 2017-12-09 at 10:00 +, Brian wrote: > Consistencey can be achieved by not installing policykit. The OP > appears to have chosen the wrong target.Consistencey can be achieved > by not > installing policykit. As Michael pointed out in [1], that's not the case; prior to polkit, there was

Re: Embarrassing security bug in systemd

2017-12-09 Thread Dejan Jocic
On 09-12-17, Jonathan Dowland wrote: > On Sat, 2017-12-09 at 10:00 +, Brian wrote: > > Consistencey can be achieved by not installing policykit. The OP > > appears to have chosen the wrong target.Consistencey can be achieved > by > > not installing policykit. > > As Michael pointed out in [1]

Public folder in plasma?

2017-12-09 Thread Hans
Dear list, maybe someone might remember, that in kde2 (or kde3?) was an option implemented, that one could add a public folder, to let people get access to it. This was a nifty little application, which was running in the taskbar. In this folder you could put any files, you want to share with t

Re: Embarrassing security bug in systemd

2017-12-09 Thread Brian
On Sat 09 Dec 2017 at 18:20:01 +, Jonathan Dowland wrote: > On Sat, 2017-12-09 at 10:00 +, Brian wrote: > > Consistencey can be achieved by not installing policykit. The OP > > appears to have chosen the wrong target.Consistencey can be achieved > by > > not installing policykit. > > As

Re: Embarrassing security bug in systemd

2017-12-09 Thread Roberto C . Sánchez
On Sat, Dec 09, 2017 at 06:20:01PM +, Jonathan Dowland wrote: > On Sat, 2017-12-09 at 10:00 +, Brian wrote: > > Consistencey can be achieved by not installing policykit. The OP > > appears to have chosen the wrong target.Consistencey can be achieved > by > > not installing policykit. > >

Re: Embarrassing security bug in systemd

2017-12-09 Thread Gene Heskett
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 + > > > > > > Brian wrote: > > > > On Fri 08 Dec 2017 at 23:06:00 +, Joe wrote: >

Re: Embarrassing security bug in systemd

2017-12-09 Thread Brian
On Sat 09 Dec 2017 at 20:07:17 +0100, Dejan Jocic wrote: > On 09-12-17, Jonathan Dowland wrote: > > On Sat, 2017-12-09 at 10:00 +, Brian wrote: > > > Consistencey can be achieved by not installing policykit. The OP > > > appears to have chosen the wrong target.Consistencey can be achieved > by

Re: Embarrassing security bug in systemd

2017-12-09 Thread Ben Caradoc-Davies
On 10/12/17 04:45, Tom Furie wrote: On Sat, Dec 09, 2017 at 10:17:45AM -0500, Ric Moore wrote: On 12/08/2017 05:12 PM, Cindy-Sue Causey wrote: Something I did *not* understand when I saw it in operation was why a password was needed at the terminal but not from within the GUI's "Applications >

Re: Embarrassing security bug in systemd

2017-12-09 Thread Dejan Jocic
On 09-12-17, Brian wrote: > On Sat 09 Dec 2017 at 20:07:17 +0100, Dejan Jocic wrote: > > > On 09-12-17, Jonathan Dowland wrote: > > > On Sat, 2017-12-09 at 10:00 +, Brian wrote: > > > > Consistencey can be achieved by not installing policykit. The OP > > > > appears to have chosen the wrong ta

Re: Embarrassing security bug in systemd

2017-12-09 Thread The Wanderer
On 2017-12-09 at 09:10, Brian wrote: > The Terms and Conditions of installing a Debian package include (as > I'm sure you are aware) accepting the Depends: and Recomends: lines. > What is in these lines can be accepted or rejected and, in the case > of Recommends:, adjusted to suit your needs.

Re: Filter logcheck reboot messages?

2017-12-09 Thread Richard Hector
On 10/12/17 04:01, Ulf Volmer wrote: > On 09.12.2017 15:37, Sven Hartge wrote: >> Richard Hector wrote: >> >>> Nobody else uses logcheck? Everyone is fine with how it works? >> >> I use logcheck on all systems and I see no need to change it. In fact, I >> *want* the reboot messages and filtering t