Ansible
PS DSC
Downloads:
14,800
Downloads of v 1.0.3:
10,304
Last Update:
17 Aug 2020
Package Maintainer(s):
Software Author(s):
- Andrew Nosenko
Tags:
sudo runas run shell command line powershell cmd admin administrator- Software Specific:
- Software Site
- Software License
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
wsudo
- 1
- 2
- 3
1.0.3 | Updated: 17 Aug 2020
- Software Specific:
- Software Site
- Software License
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
14,800
Downloads of v 1.0.3:
10,304
Maintainer(s):
Software Author(s):
- Andrew Nosenko
wsudo 1.0.3
Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by Andrew Nosenko. The inclusion of Andrew Nosenko trademark(s), if any, upon this webpage is solely to identify Andrew Nosenko goods or services and not for commercial purposes.
- 1
- 2
- 3
All Checks are Passing
3 Passing Tests
Deployment Method: Individual Install, Upgrade, & Uninstall
To install wsudo, run the following command from the command line or from PowerShell:
To upgrade wsudo, run the following command from the command line or from PowerShell:
To uninstall wsudo, run the following command from the command line or from PowerShell:
Deployment Method:
This applies to both open source and commercial editions of Chocolatey.
1. Enter Your Internal Repository Url
(this should look similar to https://community.chocolatey.org/api/v2/)
2. Setup Your Environment
1. Ensure you are set for organizational deployment
Please see the organizational deployment guide
2. Get the package into your environment
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)-
Open Source or Commercial:
- Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
- You can also just download the package and push it to a repository Download
-
Open Source
-
Download the package:
Download - Follow manual internalization instructions
-
-
Package Internalizer (C4B)
-
Run: (additional options)
choco download wsudo --internalize --source=https://community.chocolatey.org/api/v2/ -
For package and dependencies run:
choco push --source="'INTERNAL REPO URL'" - Automate package internalization
-
Run: (additional options)
3. Copy Your Script
choco upgrade wsudo -y --source="'INTERNAL REPO URL'" [other options]See options you can pass to upgrade.
See best practices for scripting.
Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.
If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:
choco upgrade wsudo -y --source="'INTERNAL REPO URL'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Install wsudo
win_chocolatey:
name: wsudo
version: '1.0.3'
source: INTERNAL REPO URL
state: present
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'wsudo' do
action :install
source 'INTERNAL REPO URL'
version '1.0.3'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
cChocoPackageInstaller wsudo
{
Name = "wsudo"
Version = "1.0.3"
Source = "INTERNAL REPO URL"
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'wsudo':
ensure => '1.0.3',
provider => 'chocolatey',
source => 'INTERNAL REPO URL',
}
Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.
4. If applicable - Chocolatey configuration/installation
See infrastructure management matrix for Chocolatey configuration elements and examples.
This package was approved by moderator gep13 on 17 Oct 2024.
Purpose
wsudo is a Linux sudo-like tool for Windows to invoke a program with elevated rights (as Administrator) from a non-admin shell command prompt.
This implementation doesn't depend on the legacy Windows Script Host (CScript). Instead, it uses a helper PowerShell 5.1 script that invokes "Start-Process -Wait -Verb runAs ..." cmdlet. Your system most likely already has PowerShell 5.x installed, otherwise you'll be offered to install it as a dependency.
Usage
wsudo runs a program or an inline command with elevated rights in the current directory. Examples:
wsudo .\myAdminScript.bat
wsudox "del C:\Windows\Temp*.* && pause"
wasudo cup all -y
wasudox start notepad C:\Windows\System32\drivers\etc\hosts
wasudog wt.exe -d %cd%
For more details, visit the GitHub repro.
@echo off
setlocal
set wsudo_commandLine=%*
set wsudo_curDir=%CD%
start /min powershell.exe -NonInteractive -ExecutionPolicy Bypass -NoProfile -NoLogo -File "%~dp0.\wsudoexec.ps1" -detach -permanent -title %~n0 -action prepare
exit /b %ERRORLEVEL%
@echo off
setlocal
set wsudo_commandLine=%*
set wsudo_curDir=%CD%
start /min powershell.exe -ExecutionPolicy Bypass -NoProfile -NoLogo -File "%~dp0.\wsudoexec.ps1" -detach -useStart -title %~n0 -action prepare
exit /b %ERRORLEVEL%
@echo off
setlocal
set wsudo_commandLine=%*
set wsudo_curDir=%CD%
start /min powershell.exe -ExecutionPolicy Bypass -NoProfile -NoLogo -File "%~dp0.\wsudoexec.ps1" -detach -title %~n0 -action prepare
exit /b %ERRORLEVEL%
@echo off
setlocal
set wsudo_commandLine=%*
set wsudo_curDir=%CD%
powershell.exe -NonInteractive -NonInteractive -ExecutionPolicy Bypass -NoProfile -NoLogo -File "%~dp0.\wsudoexec.ps1" -permanent -title %~n0 -action prepare
exit /b %ERRORLEVEL%
#Requires -Version 5.1
param(
[Parameter(Mandatory = $true)] [ValidateSet('prepare','run')] [string] $action,
[string] $title,
[string] $command,
[switch] $permanent,
[switch] $useStart,
[switch] $detach)
Set-StrictMode -Version Latest
$ErrorActionPreference = 'Stop'
class Helpers {
static [bool]IsElevated()
{
$currentPrincipal = New-Object Security.Principal.WindowsPrincipal( `
[Security.Principal.WindowsIdentity]::GetCurrent())
return $currentPrincipal.IsInRole([Security.Principal.WindowsBuiltInRole]::Administrator)
}
}
class CommandInfo {
[string]$curDir
[string]$comSpec
[string]$commandLine
[string]$title
[bool]$permanent
[bool]$detached
[bool]$useStart
[bool]$wasElevated
}
switch($action) {
'prepare' {
# pack curDir, commandLine etc using JSON/base64 and re-launch itself as admin
$commandInfo = [CommandInfo]::new()
$commandInfo.comSpec = $env:ComSpec
$commandInfo.commandLine = ([string]$env:wsudo_commandLine).Trim()
$commandInfo.curDir = $env:wsudo_curDir
$commandInfo.title = $title
$commandInfo.permanent = $permanent
$commandInfo.detached = $detach
$commandInfo.useStart = $useStart
$commandInfo.wasElevated = [Helpers]::IsElevated()
$empty = [String]::IsNullOrWhiteSpace($commandInfo.commandLine)
$commandInfoJson = ConvertTo-Json -Compress $commandInfo
$commandInfoEncoded = [Convert]::ToBase64String([System.Text.Encoding]::UTF8.GetBytes($commandInfoJson))
# get the powershell EXE name
$powershell = [System.Diagnostics.Process]::GetCurrentProcess().MainModule.FileName
$startProcessArgs = @{
PassThru = $true
FilePath = $powershell
ArgumentList = @("-ExecutionPolicy Bypass -NoProfile -NoLogo -File $PSCommandPath", '-action run', "-command $commandInfoEncoded")
}
if (!$commandInfo.wasElevated) {
$startProcessArgs.Verb = 'runAs'
if ($useStart -and !$empty) {
$startProcessArgs.WindowStyle = "Minimized"
}
}
else {
$startProcessArgs.NoNewWindow = !$detach;
}
try {
$pi = Start-Process @startProcessArgs
}
catch {
exit 1
}
if ($detach) {
# don't wait for the child proces to finish
if ($pi.HasExited) {
exit $pi.ExitCode
}
else {
exit 0
}
}
else {
if (!$commandInfo.wasElevated) {
Write-Output "Elevated and waiting..."
}
$pi.WaitForExit()
exit $pi.ExitCode
}
break
}
'run' {
# unpack curDir, commandLine etc and run the command under CMD
if (!$command) {
throw 'Must provide commandInfo.'
}
$commandInfoJson = [System.Text.Encoding]::UTF8.GetString([System.Convert]::FromBase64String($command));
$commandInfo = [CommandInfo](ConvertFrom-Json $commandInfoJson)
Set-Location $commandInfo.curDir
$empty = [String]::IsNullOrWhiteSpace($commandInfo.commandLine)
if ($commandInfo.wasElevated)
{
if (!$commandInfo.detached) {
if ($empty) {
Write-Output "Already elevated and nothing to execute, exiting."
exit 1
}
else {
$commandInfo.permanent = $false
}
}
}
if ($commandInfo.title -and ($commandInfo.detached -or !$commandInfo.wasElevated)) {
$host.ui.RawUI.WindowTitle = $commandInfo.title
}
$comSpecOpts = '/C start '
if (!$commandInfo.useStart) {
$comSpecOpts = $(if ($commandInfo.permanent) { '/K ' } else { '/C ' })
}
$startProcessArgs = @{
PassThru = $true
NoNewWindow = $true
WorkingDirectory = $commandInfo.curDir
FilePath = $commandInfo.comSpec
ArgumentList = @($comSpecOpts + $commandInfo.commandLine)
}
$pi = Start-Process @startProcessArgs
$pi.WaitForExit()
exit $pi.ExitCode
}
default {
throw 'Invalid action.'
}
}
@echo off
setlocal
set wsudo_commandLine=%*
set wsudo_curDir=%CD%
powershell.exe -NonInteractive -ExecutionPolicy Bypass -NoProfile -NoLogo -File "%~dp0.\wsudoexec.ps1" -useStart -title %~n0 -action prepare
exit /b %ERRORLEVEL%
@echo off
setlocal
set wsudo_commandLine=%*
set wsudo_curDir=%CD%
powershell.exe -NonInteractive -ExecutionPolicy Bypass -NoProfile -NoLogo -File "%~dp0.\wsudoexec.ps1" -title %~n0 -action prepare
exit /b %ERRORLEVEL%
Uninstall-BinFile 'wsudo' '..\lib\wsudo\bin\wsudo.cmd'
Uninstall-BinFile 'wsudox' '..\lib\wsudo\bin\wsudox.cmd'
Uninstall-BinFile 'wsudog' '..\lib\wsudo\bin\wsudog.cmd'
Uninstall-BinFile 'wasudo' '..\lib\wsudo\bin\wasudo.cmd'
Uninstall-BinFile 'wasudox' '..\lib\wsudo\bin\wasudox.cmd'
Uninstall-BinFile 'wasudog' '..\lib\wsudo\bin\wasudog.cmd'
Log in or click on link to see number of positives.
- wsudo.1.0.3.nupkg (228ac8f6423e) - ## / 61
In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).
Chocolatey Pro provides runtime protection from possible malware.
| Add to Builder | Version | Downloads | Last Updated | Status |
|---|---|---|---|---|
| wsudo 1.0.3 | 10304 | Monday, August 17, 2020 | Approved | |
| wsudo 1.0.2 | 3828 | Monday, March 25, 2019 | Approved | |
| wsudo 1.0.1 | 350 | Thursday, February 28, 2019 | Approved | |
| wsudo 1.0.0 | 318 | Wednesday, February 13, 2019 | Approved |
1.0.0 (Feb 12, 2019) - Initial release
1.0.1 (Feb 26, 2019) - Added wasudo/wasudox
1.0.2 (Mar 25, 2019) - Added -ExecutionPolicy Bypass -NoProfile -NoLogo PS options
1.0.3 (Aug 14, 2020) - Check if already elevated, addded wsudog/wasudog
This package has no dependencies.
Ground Rules:
- This discussion is only about wsudo and the wsudo package. If you have feedback for Chocolatey, please contact the Google Group.
- This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
- The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
- Tell us what you love about the package or wsudo, or tell us what needs improvement.
- Share your experiences with the package, or extra configuration or gotchas that you've found.
- If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.