Swift
Swift
Add a Detached Signature (Separate Key, Header Control)
See more MIME Examples
Demonstrates the Chilkat Mime.AddDetachedSignaturePk2 method, which creates a detached signature with a separately supplied certificate and private key, and a third argument controlling transfer of the existing message header fields to the new outer entity.
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: This combines the two variations — certificate and key supplied separately, plus explicit header placement — for the case that needs both. It is the most flexible of the detached-signature methods; choose it when your key material is separate and you also care about where the message headers end up on the signed result.
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 a detached signature with separately supplied cert and private key, where the 3rd
// argument controls whether the existing message header fields are transferred to the new outer
// multipart/signed entity.
var transferHeaderFields: Bool = true
success = mime.addDetachedSignaturePk2(cert: cert, privateKey: privKey, transferHeaderFields: transferHeaderFields)
if success == false {
print("\(mime.lastErrorText!)")
return
}
success = mime.save(path: "qa_output/signed.eml")
if success == false {
print("\(mime.lastErrorText!)")
return
}
print("Detached signature added (headers transferred).")
}