I’ve launched an apt server to host my BeagleBone Black Debian packages. Currently, there are only two packages: linux-cryptodev and openssl, which is compiled to use hardware acceleration. It’s a Debian wheezy only repository at the moment. You can always build everything yourself if you desire. The next one I’ll put up there is tor, which I’ll configure to use hardware acceleration. (The armhf package in the tor development server works great BTW).
This is my first time hosting packages; use at your own risk. Let me know if there are issues.
This HOWTO describes the process of enabling acceleration for certain cryptographic algorithms on the BeagleBone Black(BBB). A week ago, I tried and failed due to all sorts of kernel modules problems, but it now appears I have everything in order. Specifically, I will detail how to configure OpenSSL to use the BBB crypto hardware. Update 3/22/14: In the 3.13 kernel, the OMAP TI crypto drivers are enabled by default (for the BBB images).
According to the BeagleBone Black (BBB) system reference manual, the TI processor supports cryptographic acceleration of AES, SHA (1 I assume), MD5 and has a hardware RNG. The performance with hardware acceleration is much better than just using the CPU. To date, I do not know how to take advantage of the hardware in a user-space application, like OpenSSL. In this post, I’ll document what I tried and hopefully I’ll either solve it later (look for a pingback below) or somebody will help post a solution!
I’m running a tor relay on my BBB, which establishes TLS connections that use AES and SHA according to the spec. My relay runs at about 70% CPU usage and I’m hoping I can lower that with hardware acceleration.