Classic ASP

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.

Chilkat Classic ASP Downloads

Download Chilkat for Classic ASP

Classic ASP

<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<%
success = 0

'  Load a private key to export.
set privKey = Server.CreateObject("Chilkat.PrivateKey")
success = privKey.LoadPemFile("qa_data/private.pem")
If (success = 0) Then
    Response.Write "<pre>" & Server.HTMLEncode( privKey.LastErrorText) & "</pre>"
    Response.End
End If

'  Export as unencrypted PEM, preferring the traditional algorithm-specific representation when
'  one exists (for example "-----BEGIN RSA PRIVATE KEY-----").
pem = privKey.GetPkcs1Pem()
If (privKey.LastMethodSuccess = 0) Then
    Response.Write "<pre>" & Server.HTMLEncode( privKey.LastErrorText) & "</pre>"
    Response.End
End If

Response.Write "<pre>" & Server.HTMLEncode( pem) & "</pre>"

%>
</body>
</html>