PowerShell

Export a Traditional Private Key as Encoded Text

Demonstrates the Chilkat PrivateKey.GetPkcs1ENC method, which exports the key as the traditional/preferred unencrypted DER and encodes the DER bytes as text. The only argument names the binary encoding, such as base64 or hex.

Note: The file paths are relative to the application's current working directory. Absolute paths may also be used. Supply the paths appropriate to your own environment.

Background: This is the encoded-text form of the traditional DER representation — the same bytes the traditional PEM wraps, but returned as a string in the encoding you choose. Use it when a legacy consumer needs the traditional key structure delivered as text rather than as a PEM file. The DER is unencrypted, so the result is sensitive.

Chilkat PowerShell Downloads

Download Chilkat for PowerShell

PowerShell

Add-Type -Path "C:\chilkat\ChilkatDotNet47-x64\ChilkatDotNet47.dll"

$success = $false

#  Load a private key to export.
$privKey = New-Object Chilkat.PrivateKey
$success = $privKey.LoadPemFile("qa_data/private.pem")
if ($success -eq $false) {
    $($privKey.LastErrorText)
    exit
}

#  Export as the traditional/preferred unencrypted DER, then encode the DER bytes as text.  The
#  only argument names the binary encoding, such as "base64" or "hex".
$encoded = $privKey.GetPkcs1ENC("base64")
if ($privKey.LastMethodSuccess -eq $false) {
    $($privKey.LastErrorText)
    exit
}

$($encoded)