Hey @nickjohnson, good question — the tropicssl AES implementation is definitely not part of our documented public API. It should continue to work for the foreseeable future, but at some point down the road (2016 summer/fall?) we’ll create a publicly documented API for crypto tasks.