Product, version and build:
(*** Please do not write "latest" as a version, specify a version number ***)
32 or 64 bit version of product: Powershell Studio 2016 x64
Operating system: Win 10
32 or 64 bit OS: x64
DO NOT POST SUBSCRIPTIONS, KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM
Hello,
I browsed the forum to find an answer but didn´t get the info needed.
When I´m compiling a form, created with Powershell Studio 2016, how safe would be the exe file, assuming I have credentials inside (I´m using "System.Management.Automation.PSCredential")?
I read something about Primal Script but nothing about Powershell Studio.
Somebody has a clue?
Powershell Studio 2016 executable encryption
Forum rules
DO NOT POST SUBSCRIPTION NUMBERS, LICENSE KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
DO NOT POST SUBSCRIPTION NUMBERS, LICENSE KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
- AirLiquide
- Posts: 4
- Last visit: Wed Dec 13, 2023 7:06 am
- Alexander Riedel
- Posts: 8479
- Last visit: Thu Mar 28, 2024 9:29 am
- Been upvoted: 37 times
Re: Powershell Studio 2016 executable encryption
The packager is a shared component between PrimalScript and PowerShell Studio, so what applies to one also applies to the other.
Having said that, packaging will shield credentials in your code from regular users and their curious eyes but not from a determined intruder.
As the nature of Powershell requires the code to be submitted to the engine as plain text at some point, there is no absolute security
in this process. Depending on your security needs a safer route would be to additionally load the credentials from an external encrypted file.
https://blogs.technet.microsoft.com/rob ... edentials/
Note that the file has to be created from the same user context that will ultimately use the credentials.
Having said that, packaging will shield credentials in your code from regular users and their curious eyes but not from a determined intruder.
As the nature of Powershell requires the code to be submitted to the engine as plain text at some point, there is no absolute security
in this process. Depending on your security needs a safer route would be to additionally load the credentials from an external encrypted file.
https://blogs.technet.microsoft.com/rob ... edentials/
Note that the file has to be created from the same user context that will ultimately use the credentials.
Alexander Riedel
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.