Swift
Swift
Create an Opaque Signature with a Separate Private Key
See more MIME Examples
Demonstrates the Chilkat Mime.ConvertToSignedPk method, which creates an opaque signature using a signer certificate and its separately supplied private key. The first argument is the Cert and the second is the PrivateKey.
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: The separate-key form of
ConvertToSigned, for when the certificate and private key are not bundled together. It produces the same opaque CMS signed-data result; only the source of the key material differs.Chilkat Swift Downloads
func chilkatTest() {
var success: Bool = false
let mime = CkoMime()!
success = mime.setBody(fromPlainText: "This message will be signed.")
if success == false {
print("\(mime.lastErrorText!)")
return
}
// Load the certificate and its private key separately.
let cert = CkoCert()!
success = cert.load(fromFile: "qa_data/signer.cer")
if success == false {
print("\(cert.lastErrorText!)")
return
}
let privKey = CkoPrivateKey()!
success = privKey.loadPemFile(path: "qa_data/signer_privkey.pem")
if success == false {
print("\(privKey.lastErrorText!)")
return
}
// Create an opaque signature when the certificate and private key are supplied separately. The
// 1st argument is the signer certificate and the 2nd is its private key.
success = mime.convert(toSignedPk: cert, privateKey: privKey)
if success == false {
print("\(mime.lastErrorText!)")
return
}
success = mime.save(path: "qa_output/signed_opaque.eml")
if success == false {
print("\(mime.lastErrorText!)")
return
}
print("Message converted to an opaque signed message.")
}