Swift
Swift
Set the Decryption Certificate and Private Key
See more Email Object Examples
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 Swift Downloads
func chilkatTest() {
var success: Bool = 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.
let email = CkoEmail()!
// Load the certificate (public) and the matching private key from separate files.
let cert = CkoCert()!
success = cert.load(fromFile: "qa_data/certs/recipient.cer")
if success == false {
print("\(cert.lastErrorText!)")
return
}
let privKey = CkoPrivateKey()!
success = privKey.loadPemFile(path: "qa_data/certs/recipient_privkey.pem")
if success == false {
print("\(privKey.lastErrorText!)")
return
}
// Provide the certificate and private key to use for decryption.
success = email.setDecryptCert2(cert: cert, key: privKey)
if success == false {
print("\(email.lastErrorText!)")
return
}
// Load the encrypted email; Chilkat decrypts it using the certificate and key.
success = email.loadEml(mimePath: "qa_data/eml/encrypted.eml")
if success == false {
print("\(email.lastErrorText!)")
return
}
print("Decrypted = \(email.decrypted)")
// Note: Paths such as "qa_data/..." are relative local filesystem paths,
// relative to the current working directory of the running application.
}