Skip to content

unsigned modules should not load with AllSigned policy #5485

@TravisEz13

Description

@TravisEz13

Steps to reproduce

Set-ExecutionPolicy -Policy AllSigned -scope process
import-module pester -force  #Import a module which lives in $PSHome

But if you copy Pester out of $PSHome it will not load

Expected behavior

image

Actual behavior

module loads without error

Notes

PS 5.1 has the same behavior

Environment data

> $PSVersionTable
Name                           Value
----                           -----
PSVersion                      6.0.0-rc
PSEdition                      Core
GitCommitId                    v6.0.0-rc
OS                             Microsoft Windows 6.1.7601 S
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Metadata

Metadata

Assignees

Labels

Resolution-FixedThe issue is fixed.WG-Enginecore PowerShell engine, interpreter, and runtimeWG-Securitysecurity related areas such as JEA

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions