You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
in my environment we use WithSecure with a bunch of anti ransomware rules. One of these rules is to prevent rare files with unknown reputation to be run from the default temp path.
In my case I tried to install "Microsoft SQL Management Studio" or Git, which were blocked during the installation.
I can define exceptions based on the sha256 hash of the installers, but it would be easier to be able to define an alternate temp path to be used.
Proposed technical implementation details
I'd like to be able to call winget like this:
winget --temp-path c:\temp install Git.Git
The text was updated successfully, but these errors were encountered:
I'd like to be able to call winget like this: winget --temp-path c:\temp install Git.Git
this would download the installer file to C:\temp and execute from there. To prevent overwriting existing files this command could of course create a temporary directory like C:\temp\winget. and put the downloaded file there and remove the folder after the operation.
So you want to work around flaws in your security system by changing unrelated tools? Why is %temp% any less secure than any other place a non-admin user can write?
Description of the new feature / enhancement
Hi,
in my environment we use WithSecure with a bunch of anti ransomware rules. One of these rules is to prevent rare files with unknown reputation to be run from the default temp path.
In my case I tried to install "Microsoft SQL Management Studio" or Git, which were blocked during the installation.
I can define exceptions based on the sha256 hash of the installers, but it would be easier to be able to define an alternate temp path to be used.
Proposed technical implementation details
I'd like to be able to call winget like this:
winget --temp-path c:\temp install Git.Git
The text was updated successfully, but these errors were encountered: