PowerShell / PowerShell/PowerShell
Get-AppLocker information | Expand property Publisher is not showing the Binary Name
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 55.5k
- Forks
- 8.5k
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 88
Description
Prerequisites
- Write a descriptive title.
- Make sure you are able to repro it on the latest released version
- Search the existing issues.
- Refer to the FAQ.
- Refer to Differences between Windows PowerShell 5.1 and PowerShell.
Steps to reproduce
I am experiencing an issue with the commandlet,
Get-AppLockerFileInformation APP.MSI | Select-Object -ExpandProperty Publisher
Powershell version 5.1 listed the binary information, binary name
Expected behavior
PublisherName : O=CISCO SYSTEMS, INC., L=SAN JOSE, S=CALIFORNIA, C=US
ProductName : CISCO SECURE CLIENT - THOUSANDEYES ENDPOINT AGENT
BinaryName : {3EEA3EAE-BE3B-4746-B7AF-8DBE4EE1C37E}
BinaryVersion : 1.195.0.0
HasPublisherName : True
HasProductName : True
HasBinaryName : True
Actual behavior
Publisher
---------
O=CISCO SYSTEMS, INC., L=SAN JOSE, S=CALIFORNIA, C=US\CISCO SECURE CLIENT - THOUSANDEYES ENDPOINT AGENT\{3EEA3EAE-BE3B-4746-B7AF-8DBE4EE1C37E},1.195.0.0
Error details
No response
Environment data
Name Value
---- -----
PSVersion 7.4.2
PSEdition Core
GitCommitId 7.4.2
OS Microsoft Windows 10.0.19045
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
Visuals
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue on Windows with the shown Get-AppLockerFileInformation command and compare its Publisher expansion with the documented PowerShell 5.1 output. Trace the Get-AppLockerFileInformation entry point and identify where Publisher properties are assembled; done means BinaryName and the other expected fields are exposed in the expanded result without regressing the existing publisher value.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- cli, operating-systems, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100