Set requested execution level back to asInvoker while determining more advanced elevated scenarios #1324
Comments
ferventcoder
changed the title
This was referenced Jun 7, 2017
ferventcoder
added a commit
that referenced
this issue
Jun 8, 2017
After much deliberation on the topic, it was decided to move requested execution level back to `asInvoker` while determining more advanced scenarios to run privileged tasks from.
ferventcoder
added a commit
that referenced
this issue
Jun 8, 2017
* stable: (version) 0.10.7 (doc) update CHANGELOG/nuspec (GH-1328) Serialize/deserialize package files warnings (maint) clean up install/uninstall template (GH-1330) Use $packageArgs in default uninstall script (GH-1323) File/File64 as params not aliases (GH-1324) requestedExecutionLevel = asInvoker (GH-1327) AutoUninstaller - split multiple file paths (maint) add parameter props to UseOriginalLocation (maint) formatting (GH-1323) rename file to downloadFilePath (GH-1325) List/Search - no fail on local directory (docs) add to PowerShell CONTRIBUTING (GH-1326) Always show heading (GH-976) Use Write-FunctionCallLogMessage (maint) formatting (GH-1322) Fix: search - exact ignores page/page-size
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In 0.10.4, we moved to asking for elevated context from administrators every time (#1054), leaving non-admins in default context. However this has caused a lot of consternation as it can't be locally applied to each command (#1307). Set it back to
asInvokerfor now, but leave the manifest separated to allow for someone to change it on their own.The text was updated successfully, but these errors were encountered: