Open rui-hi opened 11 months ago
Thanks for reporting @rui-hi Do you mean that changing the locale after installing the module will cause it unable to be imported?
Hi @isra-fel Yes, but it happens regardless the locale at the time of installation. At the time of execution, or more specifically at the time of digital signature verification, system local setting should be important.
@Nickcandy please try to reproduce this issue. Thanks.
Thanks, in advance. I scanned all scripts in az resources, if it has larger character code than 127. Removing specific characters from the scripts below, re-signing seemed to work.
scripts | characters 6.11.2\MSGraph.Autorest\custom\New-AzADUser.ps1 | {'–'} 6.11.2\MSGraph.Autorest\custom\Update-AzADUser.ps1 | {'’', '–'} 6.11.2\MSGraph.Autorest\exports\ProxyCmdletDefinitions.ps1 | {'×', '’', '–'} 6.11.2\MSGraph.Autorest\internal\ProxyCmdletDefinitions.ps1 | {'×', '’', '–'}
Description
When we import Az.Resources on Windows10, 11 with ja-JP or zh-CN locale, code sign verification fails for some of the scripts. It succeed with en-EU locale so scripts itself should not be forged. Depending on the organization's compliance, the code signing verification policy may need to be "Allsigned". So could you please take a look towards this issue ?
Repro Step:
Seems like OS level verification and Get-AuthenticodeSignature fails.
ja-JP locale (zh-CN locale has the same problem too)
No problem with en-US locale
Issue script & Debug output
Environment data
Module versions
Error output
No response