closed as not constructive by Sean Middleditch, Trevor Powell, Nicol Bolas, Byte56♦, bummzack Jan 12 '13 at 10:46
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. If this question can be reworded to fit the rules in the help center, please edit the question.
I'm assuming that the presence of crypto isn't the only thing that's part of your evaluation of game engines. My suggestion would be to start making a list of features you require (including crypto), and start whittling down the list of engines.
Additionally, what you want to do with it is a factor as well. If you just want to encrypt a local file, that's going to be pretty easy perhaps. If you want to encrypt data transmission between your client and a server, that's getting more complex. But at the same time client/server encryption is pretty common, including just using HTTPS.