DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:references:date:in-reply-to
	:message-id:mime-version:content-type; q=dns; s=default; b=tqwDo
	SiA03yGmmh5s1CpT7zdR3w+RXVA8eBlM0VEfpWIeQ/BY+hh8yC7PJV5GUl4EfT+Y
	b6sBhtGJdEiP3L7jPP76Bqc9V0tSYCbxYBvEQErNS+0aA+MVJqJLDhSNQevQHVam
	FmhL+jj+7EsgwAfkzBbyITFZY2TsRJ8u8ujvFI=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: [PATCH] default ps -W process start time to system boot time when inaccessible, 0, -1
References: <20190323034522.9688-1-Brian.Inglis@SystematicSW.ab.ca>	<87d0mh5x3u.fsf@Rainer.invalid>	<20190323183653.GB3471@calimero.vinschen.de>	<874l7tbfh6.fsf@Rainer.invalid>	<4dfdfce1-245d-98fe-0c49-890ba8ec8dd4@SystematicSw.ab.ca>	<874l7s65yv.fsf@Rainer.invalid>	<bacddf44-e71b-08a2-9e93-0da8d98cc540@SystematicSw.ab.ca>	<871s2wm956.fsf@Rainer.invalid>	<a5da8d2d-328e-f60b-3d4a-cfeffc8d7556@SystematicSw.ab.ca>
Date: Sun, 24 Mar 2019 20:48:14 +0100
In-Reply-To: <a5da8d2d-328e-f60b-3d4a-cfeffc8d7556@SystematicSw.ab.ca> (Brian	Inglis's message of "Sun, 24 Mar 2019 13:16:26 -0600")
Message-ID: <87wokokq9t.fsf@Rainer.invalid>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain

Brian Inglis writes:
> System processes with more recent process start times seem to make process times
> available to unelevated processes.
> Do startup system processes not have this info available to unelevated processes
> because of some security policy, timing, or possible race conditions with system
> process and performance monitor startup?

I don't understand why you keep talking exclusively about system startup
processes, these are just a subset (if a particularly stubborn one).

The process start time info is generally unavailable for an unprivileged
user (since it requires to "open" the process") except for processes
started under the same user account in the same user session.  There is
a security token (I forgot the name, but it's been posted on this list a
few days ago) you can add to user accounts so they get to see more (but
still not all) such information.  Certain types of information are only
accessible conditional on which groups you're a member of.  It also
varies a bit by Windows version and type of install, I think.  On top of
that come group policies.  So this is a lot more involved than just
system startup processes.

> System startup process start times appear to not be available to unelevated
> processes, so the process default value is zero.
> ISTM boot time is a better, more accurate, and useful default for those processes.

I still disagree, but then those are not the only processes that have
this issue.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Wavetables for the Terratec KOMPLEXER:
http://Synth.Stromeko.net/Downloads.html#KomplexerWaves

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple