27.11.2012 Views

IronPort - advanced configuration guide

IronPort - advanced configuration guide

IronPort - advanced configuration guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Signer<br />

Issuer<br />

Escaping in Regular Expressions<br />

6-40<br />

Cisco <strong>IronPort</strong> AsyncOS 7.6 for Email Advanced Configuration Guide<br />

Chapter 6 Using Message Filters to Enforce Email Policies<br />

and is the value for matching the “issuer” or “signer.”<br />

If the message is signed using multiple signatures, the rule returns true if any of the issuers or signers<br />

match the regular expression. The short form of this rule, signed-certificate(“issuer”) and<br />

signed-certificate(“signer”), returns true if the S/MIME message contains an issuer or signer.<br />

For message signers, the rule extracts the sequence of rfc822Name names from the X.509 certificate’s<br />

subjectAltName extension. If there is no subjectAltName field in the signing certificate, or this field<br />

does not have any rfc822Name names, the signed-certificate(“signer”) rule evaluates to false. In the<br />

rare cases of multiple rfc822Name names, the rule tries to match all of the names to the regular<br />

expression and evaluates as true on the first match.<br />

The issuer is a non-empty distinguished name in the X.509 certificate. AsyncOS extracts the issuer from<br />

the certificate and converts it to an LDAP-UTF8 Unicode string. For example:<br />

C=US,S=CA,O=<strong>IronPort</strong><br />

C=US,CN=Bob Smith<br />

Since X.509 certificates require the issuer field, signed-certificate(“issuer”) evaluates whether the<br />

S/MIME message contains an X.509 certificate.<br />

LDAP-UTF8 defines a mechanism for escaping that you can use in your regular expressions. For a<br />

detailed discussion on escaping characters in LDAP-UTF8, consult Lightweight Directory Access<br />

Protocol (LDAP): String Representation of Distinguished Names, accessible from<br />

http://www.ietf.org/rfc/rfc4514.txt.<br />

The escaping rules for the signed-certificate rule’s regular expressions differ from the escaping rules<br />

defined in LDAP-UTF8 by limiting escaping to only the characters that require escaping. LDAP-UTF8<br />

allows optional escaping for characters that can be represented without escaping. For example, the<br />

following two strings are considered correct for “Example, Inc.” using the LDAP-UTF8 escaping rules:<br />

Example\, Inc.<br />

$CertificateSigners Action Variable<br />

Example\,\ Inc\.<br />

However, the signed-certificate rule only matches Example\, Inc. The regular expression does not<br />

allow escaping the space and period for matching because these characters do not require escaping, even<br />

though it is permitted in LDAP-UTF8. When creating a regular expression for the signed-certificate<br />

rule, do not escape a character if it can be represented without escaping.<br />

The action variable $CertificateSigners is a comma separated list of signers obtained from the<br />

subjectAltName element of the signing certificate. Multiple email addresses of a single signer will be<br />

included in the list with duplicates removed.<br />

OL-25137-01

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!