MailKit Documentation

## Encryption |

Encryption algorithms supported by S/MIME and OpenPGP.

Syntax

C#

public enum EncryptionAlgorithm

Members

Member name | Value | Description |
---|---|---|

Aes128 | 0 | The AES 128-bit encryption algorithm. |

Aes192 | 1 | The AES 192-bit encryption algorithm. |

Aes256 | 2 | The AES 256-bit encryption algorithm. |

Camellia128 | 3 | The Camellia 128-bit encryption algorithm. |

Camellia192 | 4 | The Camellia 192-bit encryption algorithm. |

Camellia256 | 5 | The Camellia 256-bit encryption algorithm. |

Cast5 | 6 | The Cast-5 128-bit encryption algorithm. |

Des | 7 | The DES 56-bit encryption algorithm. |

TripleDes | 8 | The Triple-DES encryption algorithm. |

Idea | 9 | The IDEA 128-bit encryption algorithm. |

Blowfish | 10 | The Blowfish encryption algorithm. |

Twofish | 11 | The Twofish encryption algorithm. |

RC240 | 12 | The RC2 40-bit encryption algorithm (S/MIME only). |

RC264 | 13 | The RC2 64-bit encryption algorithm (S/MIME only). |

RC2128 | 14 | The RC2 128-bit encryption algorithm (S/MIME only). |

Seed | 15 | The SEED 128-bit encryption algorithm (S/MIME only). |

Remarks

Represents the available encryption algorithms for use with S/MIME and OpenPGP.

RC-2/40 was required by all S/MIME v2 implementations. However, since the mid-to-late 1990's, RC-2/40 has been considered to be extremely weak and starting with S/MIME v3.0 (published in 1999), all S/MIME implementations are required to implement support for Triple-DES (aka 3DES) and should no longer encrypt using RC-2/40 unless explicitly requested to do so by the user.

These days, most S/MIME implementations support the AES-128 and AES-256 algorithms which are the recommended algorithms specified in S/MIME v3.2 and should be preferred over the use of Triple-DES unless the client capabilities of one or more of the recipients is unknown (or only supports Triple-DES).

See Also