Project

General

Profile

Actions

Bug #9193

closed

The PowerShell list-compatible-inputs version should be executed with Bypass ExecutionPolicy

Added by Matthieu CERDA about 8 years ago. Updated about 8 years ago.

Status:
Released
Priority:
1 (highest)
Category:
-
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

We currently do execute the inventory signature PS script like this:

"sign_script" string => "C:\Windows\System32\WindowsPowershell\v1.0\powershell.exe -ExecutionPolicy Bypass -File \"C:\Program Files\Rudder\sbin\signature.ps1\" -file";

but list-compatible-inputs is executed like this, since #8553:

"list_compatible_inputs" string => "\& '${ncf_path}\common\10_ncf_internals\list-compatible-inputs.ps1\'";

This second command will not work, as the default Restricted ExecutionPolicy will raise an error due to the file being foreign.

We need to do just like we do with the signature script.

Actions #1

Updated by Matthieu CERDA about 8 years ago

  • Status changed from New to In progress
  • Assignee set to Matthieu CERDA
Actions #2

Updated by Matthieu CERDA about 8 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Matthieu CERDA to Nicolas CHARLES
  • Pull Request set to https://github.com/Normation/rudder-techniques/pull/1048
Actions #3

Updated by Matthieu CERDA about 8 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions #4

Updated by Vincent MEMBRÉ about 8 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.1.15 and 3.2.8 which were released today.

Actions

Also available in: Atom PDF