Downloads:

10,021

Downloads of v 1.0.2:

3,736

Last Update:

25 Mar 2019

Package Maintainer(s):

Software Author(s):

  • Andrew Nosenko

Tags:

sudo runas run shell command line powershell cmd admin administrator

wsudo

This is not the latest version of wsudo available.

  • 1
  • 2
  • 3

1.0.2 | Updated: 25 Mar 2019

Downloads:

10,021

Downloads of v 1.0.2:

3,736

Maintainer(s):

Software Author(s):

  • Andrew Nosenko

  • 1
  • 2
  • 3
wsudo 1.0.2

This is not the latest version of wsudo available.

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed


Validation Testing Passed


Verification Testing Failed

Details

Scan Testing Successful:

No detections found in any package files

Details
Learn More

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:

📝 NOTE: 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

  • 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

3. Copy Your Script

choco upgrade wsudo -y --source="'INTERNAL REPO URL'" --version="'1.0.2'" [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'" --version="'1.0.2'" 
$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.2'
    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.2'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


cChocoPackageInstaller wsudo
{
    Name     = "wsudo"
    Version  = "1.0.2"
    Source   = "INTERNAL REPO URL"
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'wsudo':
  ensure   => '1.0.2',
  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 Pauby on 29 Mar 2019.

Description

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

For more details, visit the GitHub repro.


bin\wasudo.cmd
@echo off
setlocal
set wsudo_commandLine=%*
set wsudo_curDir=%CD%
powershell.exe -ExecutionPolicy Bypass -NoProfile -NoLogo -File "%~dp0.\wsudoexec.ps1" -detach -stayOpen -title %~n0 -action prepare
exit /b %ERRORLEVEL%
bin\wasudox.cmd
@echo off
setlocal
set wsudo_commandLine=%*
set wsudo_curDir=%CD%
start /b powershell.exe -ExecutionPolicy Bypass -NoProfile -NoLogo -File "%~dp0.\wsudoexec.ps1" -detach -title %~n0 -action prepare
exit /b %ERRORLEVEL%
bin\wsudo.cmd
@echo off
setlocal
set wsudo_commandLine=%*
set wsudo_curDir=%CD%
powershell.exe -ExecutionPolicy Bypass -NoProfile -NoLogo -File "%~dp0.\wsudoexec.ps1" -stayOpen -title %~n0 -action prepare
exit /b %ERRORLEVEL%
bin\wsudoexec.ps1
#Requires -Version 5.1

param(
  [Parameter(Mandatory = $true)] [ValidateSet('prepare','run')] [string] $action,
  [string] $title,
  [string] $command,
  [switch] $stayOpen,
  [switch] $detach)

Set-StrictMode -Version Latest
$ErrorActionPreference = 'Stop'

class CommandInfo {
  [string]$curDir
  [string]$comSpec
  [string]$commandLine
  [string]$title
  [bool]$stayOpen
}

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 = $env:wsudo_commandLine
    $commandInfo.curDir = $env:wsudo_curDir
    $commandInfo.title = $title
    $commandInfo.stayOpen = $stayOpen
    $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")
      Verb = 'runAs'
    }
    $pi = Start-Process @startProcessArgs
    if ($detach) {
      # don't wait for the child proces to finish
      if ($pi.HasExited) {
        exit $pi.ExitCode
      }
      else {
        exit 0
      }
    }
    else {
      $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)

    if ($commandInfo.title) { 
      $host.ui.RawUI.WindowTitle = $commandInfo.title
    }

    Set-Location $commandInfo.curDir
    $comSpecOpts = $(if ($commandInfo.stayOpen) { '/K' } else { '/C' })
    $startProcessArgs = @{
      PassThru = $true
      NoNewWindow = $true
      FilePath = $commandInfo.comSpec
      ArgumentList = @($comSpecOpts + $commandInfo.commandLine)
    }
    $pi = Start-Process @startProcessArgs
    $pi.WaitForExit()
    exit $pi.ExitCode
    break
  }
  default {
    throw 'Invalid action.'
  }
}
bin\wsudox.cmd
@echo off
setlocal
set wsudo_commandLine=%*
set wsudo_curDir=%CD%
powershell.exe -ExecutionPolicy Bypass -NoProfile -NoLogo -File "%~dp0.\wsudoexec.ps1" -title %~n0 -action prepare
exit /b %ERRORLEVEL%
tools\chocolateyInstall.ps1
Install-BinFile -Name 'wsudo' -Path '..\lib\wsudo\bin\wsudo.cmd'
Install-BinFile -Name 'wsudox' -Path '..\lib\wsudo\bin\wsudox.cmd'
Install-BinFile -Name 'wasudo' -Path '..\lib\wsudo\bin\wasudo.cmd' -UseStart
Install-BinFile -Name 'wasudox' -Path '..\lib\wsudo\bin\wasudox.cmd' -UseStart

tools\chocolateyUninstall.ps1
Uninstall-BinFile 'wsudo' '..\lib\wsudo\bin\wsudo.cmd'
Uninstall-BinFile 'wsudox' '..\lib\wsudo\bin\wsudox.cmd'
Uninstall-BinFile 'wasudo' '..\lib\wsudo\bin\wasudo.cmd'
Uninstall-BinFile 'wasudox' '..\lib\wsudo\bin\wasudox.cmd'

Log in or click on link to see number of positives.

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.2 3736 Monday, March 25, 2019 Approved
wsudo 1.0.1 286 Thursday, February 28, 2019 Approved
wsudo 1.0.0 251 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


Discussion for the wsudo Package

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.
comments powered by Disqus