DiagReport.ps1 Signature is invalid
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.6k
- Forks
- 592
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
The signature for DiagReport.ps1 is invalid due to script changes without re-signing the file.
To Reproduce
Steps to reproduce the behavior:
- Go to the installer directory.
Get-AuthenticodeSignature .\DiagReport.ps1 | Format-List
Expected behavior
Signature verification of PowerShell script succeeds.
Screenshots
Additional context
Execution of the .bat-file should usually work unless the execution policy is set by GPO, so should still ideally be re-signed.
Contributor guide
No contributing guide indexed for this repository
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
Start with installer/DiagReport.ps1 and run Get-AuthenticodeSignature .\DiagReport.ps1 | Format-List to confirm the reported state. Review the script changes and the project's signing process, then re-sign the updated file so signature verification succeeds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- security
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100