Downloads:

46,869

Downloads of v 1.1.1:

12,230

Last Update:

04 Feb 2019

Package Maintainer(s):

Software Author(s):

  • Jan Hebnes

Tags:

sudo console cmd command elevate administrator

Sudo

This is not the latest version of Sudo available.

1.1.1 | Updated: 04 Feb 2019

Downloads:

46,869

Downloads of v 1.1.1:

12,230

Maintainer(s):

Software Author(s):

  • Jan Hebnes

Tags:

sudo console cmd command elevate administrator

Sudo 1.1.1

This is not the latest version of Sudo available.

All Checks are Passing

2 Passing Test

Validation Testing Passed

Verification Testing Passed

Details

To install Sudo, run the following command from the command line or from PowerShell:

>

To upgrade Sudo, run the following command from the command line or from PowerShell:

>

To uninstall Sudo, run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • 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://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. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade sudo -y --source="'STEP 3 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 sudo -y --source="'STEP 3 URL'"
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode


- name: Ensure sudo installed
  win_chocolatey:
    name: sudo
    state: present
    version: 1.1.1
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'sudo' do
  action    :install
  version  '1.1.1'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: sudo,
    Version: 1.1.1,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller sudo
{
   Name     = 'sudo'
   Ensure   = 'Present'
   Version  = '1.1.1'
   Source   = 'STEP 3 URL'
}

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


package { 'sudo':
  provider => 'chocolatey',
  ensure   => '1.1.1',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install sudo version="1.1.1" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved as a trusted package on 05 Nov 2019.

Description

Used from a command line as e.g. "sudo cmd" or "sudo notepad" to elevate directly from the shell, can preserve current directory using e.g "sudo . cmd"

bin\sudo.cmd 
@echo off

:: Pass execution context information through environment variables.
set SUDO_CMDLINE=%*
set SUDO_ARG1=%1
set SUDO_ARG2=%2
set SUDO_CD=%CD%
set SUDO_DRIVE=%CD:~0,2%

:: %~dpn0 is refering to this files name and %* sends along the full commandline  
cscript //nologo "%~dpn0.vbs" %*
bin\sudo.vbs 
' //***************************************************************************
' // ***** Script Header *****
' //
' // File:      Sudo.vbs
' // Additional files required:  Sudo.cmd
' //
' // Purpose:   To provide a command line method of launching applications that
' //            prompt for elevation (Run as Administrator).
' //
' // Usage:     (Not used directly.  Launched from Sudo.cmd)
' //
' // Version:   1.1.0
' // Date :     20/04/2018
' //
' // History:
' // 1.0.0   01-Feb-2007  Created initial version used internally.
' // 1.0.1   01-Mar-2007  Added detailed usage output.
' // 1.0.0	 23-Oct-2013  Released on chocolatey
' // 1.0.1   08-Sep-2014  chocolatey framework changes required new version
' // 1.0.2   12-Jun-2015  chocolatey framework changes required new version
' // 1.1.0   20-Apr-2018  Added the option of keeping current directory 
' //                      context by using the inserted . or _ as first command argument 
' //                      when used a context cmd shell window is opened for setting 
' //                      current directory context using _ hides this window 
' // 1.1.1   04-Feb-2019  Added the -V or -version option to query the version of sudo
' //
' // ***** End Header *****
' //***************************************************************************

Set objShell = CreateObject("Shell.Application")
Set objWshShell = WScript.CreateObject("WScript.Shell")
Set objWshProcessEnv = objWshShell.Environment("PROCESS")

' Get execution context information from sudo.cmd passed in through environment variables.
strCommandLine = objWshProcessEnv("SUDO_CMDLINE")
strApplicationArgument1 = objWshProcessEnv("SUDO_ARG1")
strApplicationArgument2 = objWshProcessEnv("SUDO_ARG2")
strCurrentDirectory = objWshProcessEnv("SUDO_CD")
strCurrentDrive = objWshProcessEnv("SUDO_DRIVE")

If (WScript.Arguments.Count >= 1) Then
    strFlag = WScript.Arguments(0)
    If (strFlag = "") OR (strFlag="help") OR (strFlag="/h") OR (strFlag="\h") OR (strFlag="-h") _
        OR (strFlag = "\?") OR (strFlag = "/?") OR (strFlag = "-?") OR (strFlag="h") _
        OR (strFlag = "?") Then
        DisplayUsage
		WScript.Quit
    ElseIf (strFlag="-V") OR (strFlag="--version") Then
        DisplayVersion
		WScript.Quit
    Else

        boolKeepCurrentDirectoryContext = ((strApplicationArgument1 = ".") OR (strApplicationArgument1 = "_"))
        boolHideCurrentDirectoryContextCommandWindow = (strApplicationArgument1 = "_")

        If (boolKeepCurrentDirectoryContext = True) Then
            
            If (Len(strApplicationArgument2) > 0) Then  
                strApplication = strApplicationArgument2
                strArguments = Right(strCommandLine, (Len(strCommandLine) - (Len(strApplicationArgument1) + Len(strApplicationArgument2) + 1)))
            Else
                strApplication = "cmd"
                strArguments = ""
            End If

            'Shell.ShellExecute method https://msdn.microsoft.com/en-us/library/windows/desktop/gg537745(v=vs.85).aspx

            If (boolHideCurrentDirectoryContextCommandWindow) Then            
                vShow = 0 'Open the application with a hidden window
                'vShow = 2 'Open the application with a minimized window
                'vShow = 7 'Open the application with a minimized window. The active window remains active.
            Else
                'vShow = 1  'Open the application with a normal window. If the window is minimized or maximized, the system restores it to its original size and position.
                vShow = 10 'Open the application with its window in the default state specified by the application.
            End If

            'WScript.Echo "objShell.ShellExecute ""cmd"",""/C """ & strCurrentDrive & " && cd " & strCurrentDirectory & " && " & strApplication & " " & strArguments & """, """ & strCurrentDirectory & """, ""runas"", " & vShow
            objShell.ShellExecute "cmd","/C """ & strCurrentDrive & " && cd " & strCurrentDirectory & " && " & strApplication & " " & strArguments & """", strCurrentDirectory, "runas", vShow

        Else
            strApplication = strApplicationArgument1
            strArguments = Right(strCommandLine, (Len(strCommandLine) - Len(strApplication)))
        
            'WScript.Echo "objShell.ShellExecute """ & strApplication & """, """ & strArguments & """, """ & strCurrentDirectory & """, ""runas"" "
            objShell.ShellExecute strApplication, strArguments, strCurrentDirectory, "runas"

            'Note that strCurrentDirectory is not respected when runas is used, why the piped commands on a command shell is in use above 

        End if
         
    End If
Else
    DisplayUsage
    WScript.Quit
End If

Sub DisplayVersion

    WScript.Echo "Sudo version 1.1.1" & vbCrLf & _
        "https://chocolatey.org/packages/Sudo" & vbCrLf & _
        "https://github.com/janhebnes/chocolatey-packages/tree/master/Sudo" & vbCrLf

End Sub

Sub DisplayUsage

    WScript.Echo "Start application that prompt for elevation (Run as Administrator)." & vbCrLf & _
                 "" & vbCrLf & _
                "SUDO command" & vbCrLf & _
				"" & vbCrLf & _
				"    elevate command" & vbCrLf & _
				"" & vbCrLf & _
				"SUDO . command" & vbCrLf & _
				"" & vbCrLf & _
				"    elevate and preserve current directory" & vbCrLf & _
				"" & vbCrLf & _
				"SUDO _ command" & vbCrLf & _
				"" & vbCrLf & _
				"    elevate and preserve current directory but hide context window used to set context" & vbCrLf & _
				"" & vbCrLf & _
				"SUDO notepad %cd%\hosts" & vbCrLf & _
				"" & vbCrLf & _
				"    Note also the option of getting the current directory using %CD%\ where you would have used .\" & vbCrLf & _
				 "" & vbCrLf & _
                 "SUDO -V " & vbCrLf & _
                 "SUDO --version" & vbCrLf & _
                 "" & vbCrLf & _
				"    Prints the sudo version as well as the chocolatey package source" & vbCrLf & _
                 "" & vbCrLf & _
                 "Examples:" & vbCrLf & _
                 "" & vbCrLf & _
                 "    sudo cmd /k cd ""C:\Program Files""" & vbCrLf & _
                 "    or       sudo . cmd" & vbCrLf & _
                 "    or       sudo . " & vbCrLf & _
                 "" & vbCrLf & _
                 "    sudo powershell -NoExit -Command Set-Location 'C:\Windows'" & vbCrLf & _
                 "    or       sudo . powershell" & vbCrLf & _
                 "" & vbCrLf & _
                 "    sudo notepad ""c:\Windows\System32\drivers\etc\hosts""" & vbCrLf & _
                 "    or       sudo _ notepad hosts" & vbCrLf & _
                 "    or       sudo notepad %cd%\hosts" & vbCrLf & _
                 "" & vbCrLf & _
                 "" & vbCrLf & _
                 "Note that keeping current directory requires an elevated cmd shell " & vbCrLf & _
                 "that sets directory context before executing your command. " & vbCrLf & _ 
                 "" & vbCrLf & _
                 "You can also keep context by working with %CD%\ on file locations." & vbCrLf & _
                 "" & vbCrLf & _
                 "Usage with scripts: When using the sudo command with scripts such as" & vbCrLf & _
                 "Windows Script Host or Windows PowerShell scripts, you should specify" & vbCrLf & _
                 "the script host executable (i.e., wscript, cscript, powershell) as the " & vbCrLf & _
                 "application." & vbCrLf & _
                 "" & vbCrLf & _
                 "Sample usage with scripts:" & vbCrLf & _
                 "" & vbCrLf & _
                 "    sudo cscript ""C:\windows\system32\slmgr.vbs"" " & vbCrLf & _
                 "    sudo powershell -NoExit -Command & 'C:\Temp\Test.ps1'" & vbCrLf & _
                 "" & vbCrLf & _
                 "" & vbCrLf & _
                 "The sudo command consists of sudo.cmd and sudo.vbs" & vbCrLf

End Sub
tools\chocolateyInstall.ps1 
Remove-BinFile 'Sudo' '..\lib\Sudo.1.0\bin\sudo.cmd'
Remove-BinFile 'Sudo' '..\lib\Sudo.1.0\bin\sudo.vbs'
Remove-BinFile 'Sudo' '..\lib\Sudo.1.0.1\bin\sudo.cmd'
Remove-BinFile 'Sudo' '..\lib\Sudo.1.0.1\bin\sudo.vbs'
Remove-BinFile 'Sudo' '..\lib\Sudo.1.1.0\bin\sudo.cmd'
Remove-BinFile 'Sudo' '..\lib\Sudo.1.1.0\bin\sudo.vbs'
Generate-BinFile 'Sudo' '..\lib\Sudo\bin\sudo.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.

Version Downloads Last Updated Status
Sudo 1.1.2 9010 Friday, December 27, 2019 Approved
Sudo 1.1.1 12230 Monday, February 4, 2019 Approved
Sudo 1.1.0 7521 Friday, April 20, 2018 Approved
Sudo 1.0.2 12425 Friday, June 12, 2015 Approved
Sudo 1.0.1 4041 Monday, September 8, 2014 Approved
Sudo 1.0 1642 Wednesday, October 23, 2013 Approved

(Version 1.1) Introduces option for preserving current directory. e.g. "sudo . cmd" or just "sudo ." (Version 1.1.1) Added -V and --version parameters for checking version

This package has no dependencies.

Discussion for the Sudo Package

Ground Rules:

  • This discussion is only about Sudo and the Sudo 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 Sudo, 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