Objective-C

Supply a Fallback Certificate for S/MIME Verification

Demonstrates the Chilkat Mime.SetVerifyCert method, which supplies a signer-certificate fallback for subsequent signature verification. The only argument is the Cert.

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: Most signed messages embed the signer's certificate, so Verify can find it automatically. But some signatures omit it to save space, expecting the recipient to already have it. This method provides that certificate as a fallback so verification can proceed — the S/MIME equivalent of already knowing the sender's public key out of band.

Chilkat Objective-C Downloads

Download Chilkat for Objective-C

Objective-C

#import <CkoMime.h>
#import <CkoCert.h>

BOOL success = NO;

CkoMime *mime = [[CkoMime alloc] init];
success = [mime LoadMimeFile: @"qa_data/signed.eml"];
if (success == NO) {
    NSLog(@"%@",mime.LastErrorText);
    return;
}

//  Supply a signer-certificate fallback for verification.  This is useful when the signature does
//  not embed the signer certificate and Chilkat cannot otherwise locate it.
CkoCert *cert = [[CkoCert alloc] init];
success = [cert LoadFromFile: @"qa_data/signer.cer"];
if (success == NO) {
    NSLog(@"%@",cert.LastErrorText);
    return;
}

success = [mime SetVerifyCert: cert];
if (success == NO) {
    NSLog(@"%@",mime.LastErrorText);
    return;
}

//  Now verify using the supplied certificate.
success = [mime Verify];
if (success != YES) {
    NSLog(@"%@",mime.LastErrorText);
    return;
}

NSLog(@"%@",@"Signature verified using the supplied certificate.");