Because of the limitations of the key lengths used in 3DES and its poor execution on general-purpose computers, S/MIME eventually adopted AES as the standard for its encryption. AES, also known as Rijndael and FIPS-197, is a symmetric block cipher that can accept variable block and key lengths up to 256-bits and isn't restricted to the less secure 64-bit key lengths of 3DES. Plus, it would probably run a bit better on your server than 3DES. Because of this, it's hard to recommend using 3DES (even though it should be technically possible) because ultimately you'll be taking a giant step backward. But assuming you have a requirement due to a legacy system, I'd recommend doing some research on the Internet to find an old copy of the S/MIME protocol standard for guidance on how to integrate a 3DES encryption key into it.
Dig Deeper on Disk and file encryption tools
Related Q&A from Randall Gamby
Learn how to create account lockout policies that detail how many unsuccessful login attempts are allowed before a password lockout in order to ... Continue Reading
When it comes to minimum password length, 14-character passwords are generally considered secure, but they may not be enough to keep your enterprise ... Continue Reading
Enterprise SSO products have matured over the years, so what's the state of eSSO today? Expert Randall Gamby discusses. Continue Reading