Releases: gerardog/gsudo
Releases Β· gerardog/gsudo
gsudo v2.5.1
What's Changed
- Modified the new
PathPrecedence
config setting (docs) ensuring that the system recognize the changes without requiring a log-off or restart. You still need to restart your consoles.
Full Changelog: v2.5.0...v2.5.1
gsudo v2.5.0
What's Changed
With the release of Microsoft Sudo in Windows 11 24H2, both needs to coexist peacefully. When Microsoft Sudo is present, the sudo
command no longer redirects to gsudo
by default, so:
- Added a new config setting
PathPrecedence
: When set totrue
, it will ensuregsudo
appears first in thePATH
variable, ensuring thesudo
keyword startsgsudo
instead of Microsoft Sudo.- Call
gsudo config PathPrecedence true
to activate. Please restart all your consoles to ensure the change makes effect.- There is a bug, so this change works only after log-off or restart. Sorry! Will be fixed in v2.5.1
- Set it back to
false
to go back to normal.
- Call
If a user with ms-sudo muscle memory, accidentally runs gsudo
, let's ensure gets a good user experience with:
- Added support for ms-sudo styled arguments such as
--inline
,--disable-input
,--preserve-env
,--new-window
- Added the ability to start the elevation in a specified folder with
--chdir {directory}
(or uppercase-D {directory}
) in #355
Also:
- Added text descriptions to
gsudo config
command, so users can read each config use, in #354 - Added
SecurityEnforceUacIsolation
/DisableInput
handling also in Attached and TokenSwitch elevation Modes. - For some reason Windows doesn't focus the UAC popup if it is configured as
Do Not Dim
. The fix (#85) makes gsudo focus the popup.
Full Changelog: v2.4.4...v2.5.0
gsudo v2.4.4
What's Changed
Full Changelog: v2.4.3...v2.4.4
gsudo v2.4.3
What's Changed
- Fixed two security issues in TokenSwitchMode by:
- Restricting ACL of the elevated process to High Integrity.
- Restricting process and thread handles that are kept open during the elevation.
- Fixed (actually a workaround) for
vim
andnano
freezing when elevated directly (i.e.gsudo vim
). #248 #302 - Fixed an issue with multiple simultaneous gsudo versions installed throwing
Unauthorized. (Different gsudo.exe?)
. #300 - Fixed an issue when elevating to
MediumPlus
integrity level - Fixed an error when user configures
CacheDuration
> 24 days. #318
Acknowledgments
- Special thanks to @diversenok for making a security assessment of gsudo
Full Changelog: v2.4.2...v2.4.3
gsudo v2.4.2
What's Changed
- Fix
Error: Invalid option: -noninteractive
usinggsudo {command}
on Visual Studio code by @gerardog in #306 - Fix issue in system/trusted-installer credentials cache support by @gerardog in #323
Docs
- Docs: improve README.md manual installation technique, fixes #296 by @rfay in #299
- Docs: Include Nushell on homepage by @connorjs in #304
New Contributors
Full Changelog: v2.4.0...v2.4.2
gsudo v2.4.1-fixnoninteractive
What's Changed
- The code signing certificate expired, so I've applied the one donated by @parag_c_meta & signmycode.com. Please be patient until this certificate gets downloads and reputation on Antivirus vendors. Please report false positives!
- Fix for #305 "Error: Invalid option: -noninteractive" running
gsudo {command}
on VSCode.
Docs
- Docs: improve README.md manual installation technique, fixes #296 by @rfay in #299
- Docs: Include Nushell on homepage by @connorjs in #304
New Contributors
Full Changelog: v2.4.0...v2.4.1-fixnoninteractive
gsudo v2.4.0
What's Changed
- Improved scripting scenarios by @gerardog in #286
- Fixed issue on Cache ON not propagating
--LogLevel
or--Duration
if cache was already active - Fix
Error: Unable to connect to the elevated service
/NullReferenceException
by @gerardog in #292 - Preserve console title after gsudo exit (#266) by @gerardog in #294
Full Changelog: v2.3.0...v2.4.0
gsudo v2.3.1-beta
What's Changed
Full Changelog: v2.3.0...v2.3.1-beta
gsudo v2.3.0
What's Changed
- Add JSON format to
gsudo status --json
by @gerardog in #276 - Fetch a single status value using
gsudo status {key}
- E.g.
gsudo status CacheAvailable
- E.g.
- Fixed PowerShell Module install location to support Windows Powershell too by @gerardog in #278
Full Changelog: v2.2.0...v2.3.0
gsudo v2.2.0
What's Changed
- PowerShell Module Improvements by @gerardog in #275
- The module can now be imported simply with
Import-Module gsudoModule
, eliminating the requirement for a full absolute path. Existing scripts using absolute paths will continue to work as expected.- ...because both the
.MSI
andChocolatey
installers now deploy the module files also to%ProgramFiles%\PowerShell\Modules\gsudoModule\
.
- ...because both the
- The module version number is now properly updated with the build version.
- The module can now be imported simply with
Full Changelog: v2.1.0...v2.2.0