Same certificate issue on the MSI package as the last few releases, which triggers a SmartScreen warning.
adam
June 27, 2024, 6:00pm
3
I see the SmartScreen issue as well but the file is signed properly. I’ll see if we can figure out what’s happening here.
PS C:\src\universal\tools> signtool verify /v /pa 'C:\users\adamr\downloads\PowerShellUniversal.4.3.1 (1).msi'
Verifying: C:\users\adamr\downloads\PowerShellUniversal.4.3.1 (1).msi
Signature Index: 0 (Primary Signature)
Hash of file (sha256): 40C7042F07E462FB7697AE6F5D66D28AAB95EDD27C7C8FAD03074AE721646CF4
Signing Certificate Chain:
Issued to: GlobalSign
Issued by: GlobalSign
Expires: Sun Mar 18 05:00:00 2029
SHA1 hash: D69B561148F01C77C54578C10926DF5B856976AD
Issued to: GlobalSign Code Signing Root R45
Issued by: GlobalSign
Expires: Sat Mar 17 19:00:00 2029
SHA1 hash: 4C5D80D2CD06B1A493C49B2E9BED4A57C2F873E5
Issued to: GlobalSign GCC R45 CodeSigning CA 2020
Issued by: GlobalSign Code Signing Root R45
Expires: Sat Jul 27 19:00:00 2030
SHA1 hash: 7A2146EDB29E2EAD64AFBE7CEAD0B6085D437A32
Issued to: Ironman Software LLC
Issued by: GlobalSign GCC R45 CodeSigning CA 2020
Expires: Sat Jun 21 12:08:08 2025
SHA1 hash: C4CB3A19A4CDCF521FECBB027FB3B0CE6BBDB905
The signature is timestamped: Wed Jun 26 14:32:39 2024
Timestamp Verified by:
Issued to: GlobalSign
Issued by: GlobalSign
Expires: Sat Dec 09 19:00:00 2034
SHA1 hash: 8094640EB5A7A1CA119C1FDDD59F810263A7FBD1
Issued to: GlobalSign Timestamping CA - SHA384 - G4
Issued by: GlobalSign
Expires: Sat Dec 09 19:00:00 2034
SHA1 hash: F585500925786F88E721D235240A2452AE3D23F9
Issued to: Globalsign TSA for Advanced - G4 - 202311
Issued by: GlobalSign Timestamping CA - SHA384 - G4
Expires: Mon Dec 04 05:30:02 2034
SHA1 hash: E201FF2BD75AFDF8BC0C2C1B51BD58F8631D38B6
Successfully verified: C:\users\adamr\downloads\PowerShellUniversal.4.3.1 (1).msi
Number of files successfully Verified: 1
Number of warnings: 0
Number of errors: 0
1 Like
Did something change with App urls containing variables?
New-UDDashboard -Title 'PowerShell Universal' -Pages @(
New-UDPage -Name 'Test' -Url '/param/:TestParam' -Content {
New-UDElement -Tag 'pre' -Content { Get-Variable | Select-Object Name,Value | ConvertTo-Json -Depth 5 }
}
)
Prior to 4.3.1 $TestParam would be populated, however it seems to have stopped working even though the URL routing is still serving the page.
Edit: Seems like it last worked in 4.2.21 maybe?
Where can I get a full guide please, so I can get help from AI thanks, the website in not sufficient since the AI I use can’t dig or parse the web version. it would be really helpful, thanks so much. Ebook, PDF, word, notepad, anything in full text would be appreciated.
adam
July 2, 2024, 3:33pm
7
We have 4.3.2 in the pipeline to resolve this. It was introduced in 4.3.1.
adam
July 2, 2024, 3:34pm
8
All our docs are on GitHub. You could clone the repo and process the text files. GitHub - ironmansoftware/universal-docs: Documentation for PowerShell Universal