I've tried using the code at http: //sourceforge.net/projects/sudowin/ but haven't had any luck getting it to work.
The Un*x sudo/sudoers setup is so clean in implementation, why is this so hard...
Last edited by emueyes; 22 Jun 2011 at 02:21. Reason: fix link
Probably because this is Windows and not Linux? Just use UAC and Runas.
Code:C:\Windows\system32>runas /? RUNAS USAGE: RUNAS [ [/noprofile | /profile] [/env] [/savecred | /netonly] ] /user:<UserName> program RUNAS [ [/noprofile | /profile] [/env] [/savecred] ] /smartcard [/user:<UserName>] program RUNAS /trustlevel:<TrustLevel> program /noprofile specifies that the user's profile should not be loaded. This causes the application to load more quickly, but can cause some applications to malfunction. /profile specifies that the user's profile should be loaded. This is the default. /env to use current environment instead of user's. /netonly use if the credentials specified are for remote access only. /savecred to use credentials previously saved by the user. This option is not available on Windows 7 Home or Windows 7 Starter Editions and will be ignored. /smartcard use if the credentials are to be supplied from a smartcard. /user <UserName> should be in form USER@DOMAIN or DOMAIN\USER /showtrustlevels displays the trust levels that can be used as arguments to /trustlevel. /trustlevel <Level> should be one of levels enumerated in /showtrustlevels. program command line for EXE. See below for examples Examples: > runas /noprofile /user:mymachine\administrator cmd > runas /profile /env /user:mydomain\admin "mmc %windir%\system32\dsa.msc" > runas /env /user:user@domain.microsoft.com "notepad \"my file.txt\"" NOTE: Enter user's password only when prompted. NOTE: /profile is not compatible with /netonly. NOTE: /savecred is not compatible with /smartcard.
Indeed, this is Windows, but I was using the Un*x solution as an example of an implemented solution, not as a espousal of its use.
The whole idea of the sudo command is that a prior list of users and programs is established by an Administrator; thereafter those users may execute the selected commands at a higher privilege. The list itself is not editable by normal users of course.
To the best of my knowledge, any variation of runas still requires a password to be entered. That's been stated here several times.
The code at the Sourceforge sudowin site seems ideal, according the the fairly ambitious description by its author, and I was just wondering if anyone else had any experience with it.
Rob
Quote