public inbox for
help / color / mirror / Atom feed
Subject: setup ChangeLog LogFile.h r ...
Date: Thu, 07 Nov 2013 13:14:00 -0000	[thread overview]
Message-ID: <> (raw)

CVSROOT:	/cvs/cygwin-apps
Module name:	setup
Changes by:	2013-11-07 13:14:19

Modified files:
	.              : ChangeLog LogFile.h res.rc 
	                 resource.h setup.exe.manifest 
	                 setup64.exe.manifest win32.h 

Log message:
	* (LogFile::exit): Don't print ending message after
	successful elevation.
	* res.rc (IDS_ELEVATED): New string.
	* resource.h (IDS_ELEVATED): New string resource number.
	* (LogFile::flushAll): New function to flush log all logging
	to files without exiting (as LogFile::exit does).
	* LogFile.h: Declare new method closeAll.
	* (NoAdminOption): Add new CLI options -B/--no-admin. This
	option allows the user to suppress privilege elevation (in tandem with
	"asInvoker" requestedExecutionLevel changes to exe manifests).
	(WinMain): check if setup run with Administrator privilege and if the
	NoAdminOption has not been specified, attempt to elevate privilege to an
	Administrator via WINAPI ShellExecuteEx().
	* setup.exe.manifest: Add requestedExecutionLevel of asInvoker to allow
	suppression of privilege elevation.
	* setup64.exe.manifest: Modify requestedExecutionLevel from
	requireAdministrator to asInvoker to allow suppression of privilege
	elevation. Continuity of privilege elevation attempt on startup is
	implemented by changes to WinMain().
	* (NTSecurity::isRunAsAdmin): New function to allow to
	check if setup.exe has been run with privilege elevated to Administrator
	* win32.h: Declare new method isRunAsAdmin.


                 reply	other threads:[~2013-11-07 13:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).