JavaScript

Export a Private Key as Traditional PEM

Demonstrates the Chilkat PrivateKey.GetPkcs1Pem method, which exports the key as unencrypted PEM, preferring the traditional algorithm-specific representation when one exists (for example -----BEGIN RSA PRIVATE KEY-----). It takes no arguments.

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: Before PKCS #8 unified key storage, each algorithm had its own PEM format — RSA PRIVATE KEY, EC PRIVATE KEY, and so on. Some older tools still expect that traditional form, and this method produces it. When you have the choice, PKCS #8 (GetPkcs8Pem) is the more interoperable modern option; use this for compatibility with software that requires the legacy layout.

Note

This example is intended for running within a Chilkat.Js embedded JavaScript engine. All Chilkat JavaScript examples require Chilkat v11.4.0 or greater.

JavaScript

var success = false;

//  Load a private key to export.
var privKey = new CkPrivateKey();
success = privKey.LoadPemFile("qa_data/private.pem");
if (success == false) {
    console.log(privKey.LastErrorText);
    return;
}

//  Export as unencrypted PEM, preferring the traditional algorithm-specific representation when
//  one exists (for example "-----BEGIN RSA PRIVATE KEY-----").
var pem = privKey.GetPkcs1Pem();
if (privKey.LastMethodSuccess == false) {
    console.log(privKey.LastErrorText);
    return;
}

console.log(pem);