Select X.509 Name Attributes Dialog


This dialog box allows you to choose which information should be included in a certificate that you are about to generate. The information is split into individual items (name attributes), each item has a X.509-specific type and a string value. The Bat! collects all the information from your address entry (vCard file) and creates corresponding items. Please note that name attribute types are specific to the X.509 standard and are named differently from field types in The Bat!'s address entry, but The Bat! tries to find a corresponding attribute type for every string in your address entry. For example, if you've put "London" in the "City" field of your vCard, The Bat! creates an X.509 Item of type "localityName" and value "London".


The meaning of each name attribute type is not discussed here. Each CA may set their own rules as to how particular name attributes are treated. But there are two attributes that are treated similarly by most CAs: "commonName" (your full name) and "e-mailAddress" (your e-mail address).


Each name attribute contains a checkbox indicating whether this attribute should be included in the certificate. Unchecking an attribute has the same effect as if the item had been deleted from the list.


You can also add new attributes. Just click the "New" button and select the attribute type from the drop-down list. A new item with an empty value will appear. Select the item and type the value in the edit line in the bottom of the dialog box. Similarly, you can edit the values of other items as well.


Please note that according to X.509, all national characters will be encoded in the Unicode character set. Thus the "Windows User Interface Controls" list of items and the "Value" edit line work in Unicode mode. If there is a configuration problem (e.g. the required input locale was not properly installed in Microsoft Windows, or the system-default font doesn't contain the required characters), you may see question marks or square boxes instead of some characters. Please also note that the edit line is implemented using the Window RichEdit v2 component (although v3 is preferable). If you have problems with the edit line, try upgrading the RichEdit component.