Solution to "AES functions not available" on (Arch) Linux

I wasn't able to get whatpulse working in arch linux due to "AES functions not available". According to the knowledge base article there were no workarounds: http://help.whatpulse.org/kb/client/linu...ry-present

I was able to find a work around to get whatpulse working in Arch Linux, and probably other distributions.

To get whatpulse working in Arch Linux you need to have 2 packages installed:
whatpulse (from the AUR)
openssl-1.0 (from the Core repository)

The secret to getting this working is setting the LD_LIBRARY_PATH environment variable to the old version of openssl before running whatpulse. You can do this using this command:
You probably want whatpulse to continue after you exit the terminal so you can add a & to the end of the last command:
Running whatpulse as a user rather than as root unfortunately doesn't work since it seems the way whatpulse escalates its permissions also means it leaves the users environment meaning that it wont be able to find the older libraries it needs.

There may be security issues with running whatpulse this way but at least it works. I'm not sure how to get it to run automatically at login but I'm sure theres a way of doing so.

For other distributions you will need to install the package that provides openssl 1.0 and simply modify the above command to point to where it (and whatpulse is installed if its not in $PATH):