Ruby

Set the Decryption Certificate and Private Key

Demonstrates the Chilkat Email.SetDecryptCert2 method, which explicitly provides a certificate and its corresponding private key as separate objects for decrypting a received encrypted email. Set them before loading the encrypted message. This example loads a .cer certificate and a PEM private key, sets both, then loads an encrypted email.

Background: Sometimes the certificate and its private key are stored separately — a public .cer file plus a PEM (or other format) key file — rather than combined in a PFX. SetDecryptCert2 accepts the two objects individually, which is the natural fit for that arrangement. It is the two-object counterpart to SetDecryptCert, which takes a single certificate that already carries its private key.

Chilkat Ruby Downloads

Download Chilkat for Ruby

Ruby

require 'chilkat'

success = false

#  Demonstrates the SetDecryptCert2 method, which explicitly provides a certificate and its
#  corresponding private key (as separate objects) for decrypting a received encrypted
#  email.  Set them before loading the encrypted email.

email = Chilkat::CkEmail.new()

#  Load the certificate (public) and the matching private key from separate files.
cert = Chilkat::CkCert.new()
success = cert.LoadFromFile("qa_data/certs/recipient.cer")
if (success == false)
    print cert.lastErrorText() + "\n";
    exit
end

privKey = Chilkat::CkPrivateKey.new()
success = privKey.LoadPemFile("qa_data/certs/recipient_privkey.pem")
if (success == false)
    print privKey.lastErrorText() + "\n";
    exit
end

#  Provide the certificate and private key to use for decryption.
success = email.SetDecryptCert2(cert,privKey)
if (success == false)
    print email.lastErrorText() + "\n";
    exit
end

#  Load the encrypted email; Chilkat decrypts it using the certificate and key.
success = email.LoadEml("qa_data/eml/encrypted.eml")
if (success == false)
    print email.lastErrorText() + "\n";
    exit
end

print "Decrypted = " + email.get_Decrypted().to_s() + "\n";

#  Note: Paths such as "qa_data/..." are relative local filesystem paths,
#  relative to the current working directory of the running application.