SAPIEN Forums

Powershell Studio 5.7.172
Windows 10 Pro 1909

Work has started the process of moving us to using a VDI as a jumpbox to reach our database servers. As part of that process we are being asked to test the software we normally use before they start locking things down.

I have installed Powershell Studio on this jumpbox and I am having issues when signing a script. When I have powershell->automatically sign .ps1 scripts checked every time I try to save a script powershell studio pauses/hangs (using no CPU) for about 60 seconds then it returns saying that it Successfully Signed the file but it did not.

From outside powershell studio the signing works with no issues.
No errors in the event viewer.

Hoping someone might have seen this or have an idea what is happening during signing that might be causing the application to pause/hang like that and then say it was successful. Or where I might look. I suspect its more in the way they have restricted this jumpbox than it is a problem with Studio but I don't even know where else I might look for any errors/messages.

Scott

I apologize I put this in the wrong forum some how. I meant to put it in the powershell studio form.. can it be moved or should I repost?

In a regular desktop environment, I'm not able to reproduce this behavior of not being able to sign, but I will keep investigating.
Also, please ensure that no components of PowerShell Studio are being blocked by a firewall, specifically a dll called SignScript.

Your post was redirected here as there are no licenses associated with your account.

ok thanks. Looks like the key/license was registered by someone else in the company. I will try and figure that out.

specifically a dll called SignScript.

That sounds promising these jumpboxes are definitely locked down. Would that be reaching out to the internet or are you referring to windows firewall blocking it just locally on the jumpbox itself.

Yes, timestamping while signing requires internet access to the timestamp URL specified in the options.
If you do NOT timestamp, the signature becomes invalid when the signing certificate expires.