|Top Previous Next|
The Bat!'s internal implementation of S/MIME allows you to export one or more selected certificates to a file for backup or distribution (e.g. import into other programs or The Bat! installations). Certificates are exported to known, open formats only.
Conforms to PKCS 12 v1.0: Personal Information Exchange Syntax developed by RSA Laboratories.
It allows export of a group of certificates as well as their private keys, which are encrypted using the same passphrases used in The Bat!,; the corresponding certificates are not encrypted.
Conforms to RFC- 2630 (Cryptographic Message Syntax). A group of certificates can be exported to a file based on a signed message packet, but the packet has no message body and no signature, only the attached certificates. It contains only certificates but no private keys. This is the most commonly accepted format.
This format only allows you to export a single certificate without associated private keys.
The output file contains a single X.509 certificate encoded according to DER-encoding rules; it will not be encrypted. If a certificate contains a private key, the key may be exported to a separate binary file, unencrypted, corresponding to PKCS#1 DER-encoded RSA.
Beware: Not all software applications can handle DER encoded binary X.509!
This format is based on DER encoded binary X.509, but additionally encodes with a Base64-wrapper. The file only contains printable characters, which can easily be put into an e-mail or on a Web site.
Base-64 encoded X.509 is widely supported. Private keys may be exported to separate plain-text files.
Check this option if you want to make sure your certificate can be verified (which is only possible with an unbroken chain of certificates).
Note: This option only works with standards supporting multiple certificates in a single file.
This option is not supported for Cryptographic Message Syntax Standard - PKCS #7 (.P7B).