SQL Server

Save a Private Key as a Traditional PEM File

Demonstrates the Chilkat PrivateKey.SavePemFile method, which saves the key as unencrypted PEM, preferring a traditional algorithm-specific representation (for example RSA PRIVATE KEY). The only argument is the destination path.

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: The file-writing form of GetPkcs1Pem, producing the legacy per-algorithm PEM that some older software requires. Prefer SavePkcs8PemFile for modern interoperability; use this when a consumer specifically needs the traditional layout. The PEM is unencrypted.

Chilkat SQL Server Downloads

Download Chilkat for SQL Server

SQL Server

--
CREATE PROCEDURE ChilkatSample
AS
BEGIN
    DECLARE @hr int
    DECLARE @sTmp0 nvarchar(4000)
    DECLARE @success int
    SELECT @success = 0

    --  Load a private key to export.
    DECLARE @privKey int
    EXEC @hr = sp_OACreate 'Chilkat.PrivateKey', @privKey OUT
    IF @hr <> 0
    BEGIN
        PRINT 'Failed to create ActiveX component'
        RETURN
    END

    EXEC sp_OAMethod @privKey, 'LoadPemFile', @success OUT, 'qa_data/private.pem'
    IF @success = 0
      BEGIN
        EXEC sp_OAGetProperty @privKey, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @privKey
        RETURN
      END

    --  Save as unencrypted PEM, preferring the traditional algorithm-specific representation (for
    --  example "RSA PRIVATE KEY" for RSA).
    EXEC sp_OAMethod @privKey, 'SavePemFile', @success OUT, 'qa_output/private.pem'
    IF @success = 0
      BEGIN
        EXEC sp_OAGetProperty @privKey, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @privKey
        RETURN
      END

    PRINT 'Saved.'

    EXEC @hr = sp_OADestroy @privKey


END
GO