SQL Server Requires Chilkat v11.0.0+
SQL Server
Generate an ECC Key (Public and Private)
See more ECC Examples
Demonstrates how to generate an ECC key and save both public and private parts.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 @sTmp0 nvarchar(4000)
DECLARE @success int
SELECT @success = 0
-- This example requires the Chilkat API to have been previously unlocked.
-- See Global Unlock Sample for sample code.
-- Create a Fortuna PRNG and seed it with system entropy.
-- This will be our source of random data for generating the ECC private key.
DECLARE @fortuna int
EXEC @hr = sp_OACreate 'Chilkat.Prng', @fortuna OUT
IF @hr <> 0
BEGIN
PRINT 'Failed to create ActiveX component'
RETURN
END
DECLARE @entropy nvarchar(4000)
EXEC sp_OAMethod @fortuna, 'GetEntropy', @entropy OUT, 32, 'base64'
EXEC sp_OAMethod @fortuna, 'AddEntropy', @success OUT, @entropy, 'base64'
DECLARE @ecc int
EXEC @hr = sp_OACreate 'Chilkat.Ecc', @ecc OUT
-- Generate a random ECC private key on the secp256r1 curve.
-- Chilkat also supports other curves, such as secp384r1, secp521r1, and secp256k1.
DECLARE @privKey int
EXEC @hr = sp_OACreate 'Chilkat.PrivateKey', @privKey OUT
EXEC sp_OAMethod @ecc, 'GenKey', @success OUT, 'secp256r1', @fortuna, @privKey
IF @success = 0
BEGIN
EXEC sp_OAGetProperty @ecc, 'LastErrorText', @sTmp0 OUT
PRINT @sTmp0
EXEC @hr = sp_OADestroy @fortuna
EXEC @hr = sp_OADestroy @ecc
EXEC @hr = sp_OADestroy @privKey
RETURN
END
-- Save the private key to PKCS8 encrypted PEM
-- (The private key can be saved in a variety of different formats. See the online reference documentation.)
EXEC sp_OAMethod @privKey, 'SavePkcs8EncryptedPemFile', @success OUT, 'pemPassword', 'qa_output/eccPrivKey.pem'
IF @success <> 1
BEGIN
EXEC sp_OAGetProperty @privKey, 'LastErrorText', @sTmp0 OUT
PRINT @sTmp0
END
-- The private key PEM looks like this:
-- -----BEGIN ENCRYPTED PRIVATE KEY-----
-- MIHFMEAGCSqGSIb3DQEFDTAzMBsGCSqGSIb3DQEFDDAOBAhUmn+1/lwCIwICCAAw
-- FAYIKoZIhvcNAwcECPlyNXAXZO+oBIGAIvxvTENXJWbrCwSjh0QNxLecBotUpfI5
-- auOonLmwVMyt1ahMmNyVo/D+pnKQSE41Fg8fApM0DCDKZUOVCCcK1qirIsMPQkGp
-- klPJbvrQRVYgzBtU31uNB5y2wqhrIeepal1HXBvbkUK0nfJMbcdz/XAEIQu2HhTD
-- t6LMScPQld4=
-- -----END ENCRYPTED PRIVATE KEY-----
-- Now get the public key part from the private key.
-- (A public key is actually a subset of the private key.)
DECLARE @pubKey int
EXEC @hr = sp_OACreate 'Chilkat.PublicKey', @pubKey OUT
EXEC sp_OAMethod @privKey, 'ToPublicKey', @success OUT, @pubKey
-- Save the public key to a PEM file.
-- (The public key can be saved in a variety of different formats. See the online reference documentation.)
-- For ECC keys, the 1st argument (bPreferPkcs1) is ignored and unused.
DECLARE @bPreferPkcs1 int
SELECT @bPreferPkcs1 = 0
EXEC sp_OAMethod @pubKey, 'SavePemFile', @success OUT, @bPreferPkcs1, 'qa_output/eccPubKey.pem'
-- The public key PEM looks like this:
-- -----BEGIN PUBLIC KEY-----
-- MIIBSzCCAQMGByqGSM49AgEwgfcCAQEwLAYHKoZIzj0BAQIhAP////8AAAABAAAA
-- AAAAAAAAAAAA////////////////MFsEIP////8AAAABAAAAAAAAAAAAAAAA////
-- ///////////8BCBaxjXYqjqT57PrvVV2mIa8ZR0GsMxTsPY7zjw+J9JgSwMVAMSd
-- NgiG5wSTamZ44ROdJreBn36QBEEEaxfR8uEsQkf4vOblY6RA8ncDfYEt6zOg9KE5
-- RdiYwpZP40Li/hp/m47n60p8D54WK84zV2sxXs7LtkBoN79R9QIhAP////8AAAAA
-- //////////+85vqtpxeehPO5ysL8YyVRAgEBA0IABGdOH8uM6SfX3mdV+TR0mWp2
-- gfVRPlxWxwhOiowuNByBxmQz7ZR4CJY1XcN2zkUo5pzW73ZhGwgd2XTOvqPqG40=
-- -----END PUBLIC KEY-----
--
PRINT 'finished.'
EXEC @hr = sp_OADestroy @fortuna
EXEC @hr = sp_OADestroy @ecc
EXEC @hr = sp_OADestroy @privKey
EXEC @hr = sp_OADestroy @pubKey
END
GO