Chilkat Examples

ChilkatHOME.NET Core C#Android™AutoItCC#C++Chilkat2-PythonCkPythonClassic ASPDataFlexDelphi ActiveXDelphi DLLGoJavaLianjaMono C#Node.jsObjective-CPHP ActiveXPHP ExtensionPerlPowerBuilderPowerShellPureBasicRubySQL ServerSwift 2Swift 3,4,5...TclUnicode CUnicode C++VB.NETVBScriptVisual Basic 6.0Visual FoxProXojo Plugin

SQL Server Examples

Web API Categories

ASN.1
AWS KMS
AWS Misc
Amazon EC2
Amazon Glacier
Amazon S3
Amazon S3 (new)
Amazon SES
Amazon SNS
Amazon SQS
Async
Azure Cloud Storage
Azure Key Vault
Azure Service Bus
Azure Table Service
Base64
Bounced Email
Box
CAdES
CSR
CSV
Certificates
Code Signing
Compression
DKIM / DomainKey
DNS
DSA
Diffie-Hellman
Digital Signatures
Dropbox
Dynamics CRM
EBICS
ECC
Ed25519
Email Object
Encryption
FTP
FileAccess
Firebase
GMail REST API
GMail SMTP/IMAP/POP
Geolocation
Google APIs
Google Calendar
Google Cloud SQL
Google Cloud Storage
Google Drive
Google Photos
Google Sheets
Google Tasks
Gzip
HTML-to-XML/Text
HTTP

HTTP Misc
IMAP
JSON
JSON Web Encryption (JWE)
JSON Web Signatures (JWS)
JSON Web Token (JWT)
Java KeyStore (JKS)
MHT / HTML Email
MIME
MS Storage Providers
Microsoft Graph
Misc
NTLM
OAuth1
OAuth2
OIDC
Office365
OneDrive
OpenSSL
Outlook
Outlook Calendar
Outlook Contact
PDF Signatures
PEM
PFX/P12
PKCS11
POP3
PRNG
REST
REST Misc
RSA
SCP
SCard
SFTP
SMTP
SSH
SSH Key
SSH Tunnel
ScMinidriver
SharePoint
SharePoint Online
Signing in the Cloud
Socket/SSL/TLS
Spider
Stream
Tar Archive
ULID/UUID
Upload
WebSocket
XAdES
XML
XML Digital Signatures
XMP
Zip
curl

 

 

 

(SQL Server) Working with PEM Encrypted Private Keys

Demonstrates how to load and save PEM encrypted private keys.

Chilkat ActiveX Downloads

ActiveX for 32-bit and 64-bit Windows

// 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)
    -- Starting in v9.5.0.49, all Chilkat classes can be unlocked at once at the beginning of a program
    -- by calling UnlockBundle.  It requires a Bundle unlock code.
    DECLARE @chilkatGlob int
    EXEC @hr = sp_OACreate 'Chilkat_9_5_0.Global', @chilkatGlob OUT
    IF @hr <> 0
    BEGIN
        PRINT 'Failed to create ActiveX component'
        RETURN
    END

    DECLARE @success int
    EXEC sp_OAMethod @chilkatGlob, 'UnlockBundle', @success OUT, 'Anything for 30-day trial.'
    IF @success <> 1
      BEGIN
        EXEC sp_OAGetProperty @chilkatGlob, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @chilkatGlob
        RETURN
      END

    DECLARE @pem int
    EXEC @hr = sp_OACreate 'Chilkat_9_5_0.Pem', @pem OUT

    DECLARE @pemPassword nvarchar(4000)
    SELECT @pemPassword = 'secret'

    -- To load a PEM file containing encrypted private keys, simply
    -- provide the password.
    EXEC sp_OAMethod @pem, 'LoadPemFile', @success OUT, '/Users/chilkat/testData/pem/pemContainingEncryptedPrivateKeys.pem', @pemPassword
    IF @success <> 1
      BEGIN
        EXEC sp_OAGetProperty @pem, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @chilkatGlob
        EXEC @hr = sp_OADestroy @pem
        RETURN
      END

    DECLARE @fac int
    EXEC @hr = sp_OACreate 'Chilkat_9_5_0.FileAccess', @fac OUT

    DECLARE @pemText nvarchar(4000)
    EXEC sp_OAMethod @fac, 'ReadEntireTextFile', @pemText OUT, '/Users/chilkat/testData/pem/pemContainingEncryptedPrivateKeys.pem', @pemPassword

    -- To load a PEM from a string, call LoadPem instead of LoadPemFile:
    EXEC sp_OAMethod @pem, 'LoadPem', @success OUT, @pemText
    IF @success <> 1
      BEGIN
        EXEC sp_OAGetProperty @pem, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @chilkatGlob
        EXEC @hr = sp_OADestroy @pem
        EXEC @hr = sp_OADestroy @fac
        RETURN
      END

    -- A few notes:
    -- The PEM may contain both private keys and certificates (or anything else).
    -- The password is utilized for whatever content in the PEM is encrypted.  
    -- It is OK to have both encrypted and non-encrypted content within a given PEM.

    -- PEM private keys can be encrypted in different formats.  The LoadPem and LoadPemFile
    -- methods automatically handle the different formats.
    -- One format is PKCS8 and is indicated by this delimiter within the PEM:

    -- -----BEGIN ENCRYPTED PRIVATE KEY-----
    -- MIICoTAbBgkqhkiG9w0BBQMwDgQIfdD0zv24lgkCAggABIICgE0PdHJmRbNs6cBX
    -- ...

    -- Another format, we'll call "passphrase" looks like this in the PEM:
    -- -----BEGIN RSA PRIVATE KEY-----
    -- Proc-Type: 4,ENCRYPTED
    -- DEK-Info: DES-EDE3-CBC,A4215544D11C5D0C
    -- 
    -- paqy9XRexcSjurHfG0xhCaUD0HrvIdhuC0CbRxxxeMlkLaV6+uT80rBxt2AaibWG
    -- ...

    -- Show the bit length of each private key:
    DECLARE @i int

    DECLARE @numPrivateKeys int
    EXEC sp_OAGetProperty @pem, 'NumPrivateKeys', @numPrivateKeys OUT
    IF @numPrivateKeys = 0
      BEGIN

        PRINT ('Error: Expected the PEM to contain private keys.')
        EXEC @hr = sp_OADestroy @chilkatGlob
        EXEC @hr = sp_OADestroy @pem
        EXEC @hr = sp_OADestroy @fac
        RETURN
      END
    SELECT @i = 1
    WHILE @i <= @numPrivateKeys
      BEGIN
        DECLARE @privKey int
        EXEC sp_OAMethod @pem, 'GetPrivateKey', @privKey OUT, @i - 1

        EXEC sp_OAGetProperty @privKey, 'BitLength', @iTmp0 OUT

        PRINT @i + ': ' + @iTmp0 + ' bits'
        EXEC @hr = sp_OADestroy @privKey

        SELECT @i = @i + 1
      END

    EXEC @hr = sp_OADestroy @chilkatGlob
    EXEC @hr = sp_OADestroy @pem
    EXEC @hr = sp_OADestroy @fac


END
GO

 

© 2000-2024 Chilkat Software, Inc. All Rights Reserved.