SQL Server
SQL Server
Export a Private Key as PKCS #8 PEM
See more Private Key Examples
Demonstrates the Chilkat PrivateKey.GetPkcs8Pem method, which exports the loaded key as unencrypted PKCS #8 PEM (-----BEGIN 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: PKCS #8 is the modern, algorithm-independent container — the same
PRIVATE KEY PEM wrapper holds RSA, EC, or Ed25519 keys alike, which is why it is the format most current tooling expects. Being unencrypted, the PEM carries the key material in the clear, so treat the output as sensitive. Use GetPkcs8EncryptedPem when the exported key needs a passphrase.Chilkat SQL Server Downloads
-- Important: See this note about string length limitations for strings returned by sp_OAMethod calls.
--
CREATE PROCEDURE ChilkatSample
AS
BEGIN
DECLARE @hr int
DECLARE @iTmp0 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
-- Export as unencrypted PKCS #8 PEM ("-----BEGIN PRIVATE KEY-----"). PKCS #8 is an
-- algorithm-independent container that works for RSA, EC, and Ed25519.
DECLARE @pem nvarchar(4000)
EXEC sp_OAMethod @privKey, 'GetPkcs8Pem', @pem OUT
EXEC sp_OAGetProperty @privKey, 'LastMethodSuccess', @iTmp0 OUT
IF @iTmp0 = 0
BEGIN
EXEC sp_OAGetProperty @privKey, 'LastErrorText', @sTmp0 OUT
PRINT @sTmp0
EXEC @hr = sp_OADestroy @privKey
RETURN
END
PRINT @pem
EXEC @hr = sp_OADestroy @privKey
END
GO