imadlatch Posted December 7, 2015 Share Posted December 7, 2015 NSudo 3.1 Debug English + "NSudoC Commandline"NSudo 3.1 Debug x64 translated from Chinese to English completely BY ME using Microsoft Visual studio 2015 C++NSudo 3.1 Debug x64 base upgraded to 3.2 using original source https://github.com/MouriNaruto/NSudoNSudo now supporting command-line using (NSudoC.exe -U:T -P:E Path ApplicationName) and fixed some bugs If you face Process creation failed "don't run as administrator"Sorry I was not able to translate x86 version because some corruption in databaseSorry for bad English is this post "Google translate" DOWNLOADSudo - a powerful system management toolsThis tool is raymai97 super command prompt that article said King Friends of making single-file version of the next releaseThe following are brief references to the original raymai97 TrustedInstallerTrustedInstaller when Windows Update and other system components need to modify the file, use the "proxy."TI's authority is very high - even higher than the SYSTEM ~ called the Windows version of ROOT privileges ~CMD TI mode allows you to not modify / destroy the NTFS permissions setting, directly on the operating system files, such as replace, rename, delete ......verify that you can successfully modify the file includes explorer.exe, shell32.exe, iexplore .exe.Using TI mode CMD, the program will start automatically have permission to TI. So you can use it to start your favorite third-party file manager, such as 7zFM. It should be noted, explorer TI mode is not supported, it will not run properly.You might ask, modify NTFS permissions are not set up like? There are many online "One key to change the owner" "a key to get permission," it ~You know, NTFS permissions are used to prevent your system files are blind reform. After most people tend to modify permissions and file, no recovery permission settings, so after other programs can modify these files directly!If the default NTFS permissions are set, even if the program is run as an administrator, but also requires quite a bit of codeTo make their own privileges, modify the relevant documents.Win8 the WindowsApps folder is a typical example. If you modify the permissions, do not change it back, there will not open Apps (flash back) risk, severe cases can not all Apps are open!Well, you say you want to manually change the permissions, and then modify the file, and then change the permissions back ...... Just think, just to modify a system file, so in trouble. If you have multiple system documents?So I think, directly CMD has TI permissions, and then with other third-party file manager (eg 7zFM), will be more convenient than to modify NTFS permissions, fast and safe -Future version (3.1) to improve the place1. Adjust System Console and TrustedInstaller permissions buffer size2. You can not use path repair problems with spacesImproved logNSudo 3.1 Debug1. Fix the ComboBox UI can not enter long text issues2. fix the problem in some cases can not be used (due to the development of machine Windows10 Bug caused by mistaken that way possible)3. Increase the real token down the right (except Administrator cmd mistakenly displayed outside; others will see it as a normal user)4. Increase the command-line version5. Add a list of frequently used custom featuresSudo 3.0 R21. Bug fixes can not be opened by the system to other associated files2.SDK header file improvements: increased #pragma comment (lib, "NSudoAPI.lib")Sudo 3.01. Support for external application calls (sorry for some people wait too long)2. To increase the common list of calls (temporarily does not support custom; 3.1 will join the future)3. Add up down the right function (of course, is perfect right down to the front UAC is not to mention the right of course not with the principles of obtaining explorer token and create a scheduled task)4. Support for custom permissions tokens5. The interface is completely reconstructed (relative to 2.x is)6. code optimization (with respect NSudo 3.0 M1 is)7. Add NSudo SDK8. native 64-bit version9. The implementation of the method call an external program to ignore WOW64 redirection (NSudoCreateProcess)10.WinPE support (although did not play much of a role)InstructionsDouble-click on [NSudo schema file folder you need (such as Win32 is 32 NSudo)] \ NSudo.exe according to promptsCommand Line Options (NSudoC.exe)Format: Sudo [-U] [-P] [-M] command line or in the name of common tasks-U: [T | S | C | P | D] UsersT TrustedInstallerS SystemC current userP current processD current process (down right)-P: [E | D] privilegeE Enable all privilegesD Disable all privilegesPS: If you want to default privileged way, please do not include the -P parameter-M: [s | H | M | L] IntegrityS systemH HighM inL LowPS: If you want to default, then the integrity of the way, please do not include -M parameters-? Displays the contentExamples: In TrustedInstaller permissions, enable all the privileges, integrity default run Command PromptNSudoC -U:T -P:E cmdSince the definition of common list, you can use tools such as Notepad to edit ShortCutList.ini; the following format[title]CommandLine = Command LineFor example; Suppose I want to build a title as "claustrophobic death ki Princess ? is ? se pu Te ? Suites" command line "e: \ downloads \ claustrophobic death ki Princess ? is ? se pu Te ? Suites .mp3" common project, you can doPrecautionsUse this tool needs to have some basic computerDue to get permission too high, VB4112 (From MSHK) on this comment: "This tool is very dangerous, especially PC users do not know"License AgreementDOWNLOAD Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.