sudo make uninstall didn't work "no rule to make target 'uninstall'.
Remember, there are two versions of OpenSSL involved, the normal
OpenSSL, that came with Jessie, which no one cares about. And this
self-compiled one in /usr/local/ssl/ that we're trying to get to
work with cryptodev and Tor. Should I just delete the /ssl/ folder
in /usr/local/? I have no idea where Cryptodev is installed because
it's a mod that's loaded. But, from what I understand, the problem
lies in OpenSSL needing a patch or something to play nicely with
Cryptodev in the first place. So, for now, I don't see the need to
reinstall Cryptodev. Naturally, I could be completely mistaken.
On 2.5.15 11:19, Igor Chelnokov wrote:
FYI: sudo
make install is bad, use checkinstall -D
sudo
make uninstall should do the trick, but I'm not sure
Step 1: Getting OpenSSL to become Hardware-Accelerated
sudo apt-get install linux-image-3.14.39-ti-r61
sudo apt-get install linux-headers-3.14.39-ti-r61
wget
http://download.gna.org/cryptodev-linux/cryptodev-linux-1.7.tar.gz
tar zxf cryptodev-linux-1.7.tar.gz cd cryptodev-linux-1.7/
sudo make
sudo make install
sudo depmod -a
sudo modprobe cryptodev
lsmod
sudo sh -c 'echo cryptodev>>/etc/modules'
cd ~
wget https://www.openssl.org/source/openssl-1.0.2a.tar.gz
tar zxf openssl-1.0.2a.tar.gz
cd openssl-1.0.2a/
You left out, patching OpenSSL's cryptodev support to function.
ls
./config -DHAVE_CRYPTODEV -DUSE_CRYPTDEV_DIGESTS shared
sudo make
sudo make install
And you left out "running the test suite, which according to the bug in
OpenSSL's bugtracker, would have failed".
Both of these dastardly details are hidden in the depths of the file
misleadingly titled "README" in cryptodev-linux-1.7.tar.gz, under the
heading "* OpenSSL:".
Regards,