Internet Forensics

Export a securestring to a safe, persistent format

Snap-In: Microsoft.PowerShell.Security

Syntax:

ConvertFrom-SecureString

[-SecureString] <SecureString> [ [-SecureKey] <SecureString>] [-Verbose] [-Debug] [-ErrorAction <ActionPreference>] [-ErrorVariable <String>] [-OutVariable <String>] [-OutBuffer <Int32>]

ConvertFrom-SecureString

[-SecureString] <SecureString> [-Key <Byte[]>] [-Verbose] [-Debug] [-ErrorAction <ActionPreference>] [-ErrorVariable <String>] [-OutVariable <String>] [-OutBuffer <Int32>]

Description:

ConvertFrom-SecureString takes a secure string and converts it into a DPAPI-protected normal string. This string can be securely embedded in a script and reconstituted to a secure string with the ConvertTo-SecureString Cmdlet. If a key is provided, the encryption should not use the DPAPI encryption. Instead, another FIPS-140 compliant algorithm should be used. The encryption key should be 16, 24, or 32 bytes long. The Rijndael algorithm used supports keys with lengths of 128, 192, and 256 bits.