I've got a small Via Eden CPU based computer running FreeBSD 11.2 release, and I can't for the life of me get hardware acceleration enabled with the openSSL library.
I have the Kernel module install and loaded at boot time. I have tried building OpenSSL from ports - but it appears the mirrors are missing a file (1001-crypto-hmac-support-EVP_MD_CTX_FLAG_ONESHOT-and-set-.patch). I have had a peak at the 'current' pkg package and noted that the libpadlock.so is contained within it, but I can't fathom out if it is installed along with the userland OpenSSL package. I have tried to force the base OpenSSL to use libpadlock.so from this file, but I get a segmentation fault (no doubt due to the base version being compiled against different binaries).
Btw, I am new to FreeBSD - I've spent hours at this. So, if you can tollerate a such a N00b, it would be greatly appreciated.
So, it is possible to get the required engine libraries for compiled against the base openSSL so I can enable padlock acceleration? Or even instructions on how to compile it myself (sources for the version included with the base?) If not, is there a way to customise the installation of the package from PKG to ensure it's installation includes the additional engine libraries that are in the package (I don't think they are installed by default, either that or I am running openssl from the base install, in which case, how can I change that?). Failing this, how can I compile a later version when such files are missing?
I know that the random number generator is percieved as unsafe, and compromised, however I wouldn't be using it for this use, I will be using it purely for it's hardware hashing and AES acceleration (randomness goes through Yammer as far as I am aware anyway).
I've spent hours on this, and I'm frustrated and tired. Any pointers on where I can pick up from in the morning would be great.
Ideally I'd like to enable padlock support with the 'base' install of OpenSSL. But if not, another local copy will suffice.
Cheers.
[Edit] Just to confirm that the hardware features of this ancient CPU are seen by FreeBSD - it's now just a matter of getting OpenSSL to play ball [/Edit]
I have the Kernel module install and loaded at boot time. I have tried building OpenSSL from ports - but it appears the mirrors are missing a file (1001-crypto-hmac-support-EVP_MD_CTX_FLAG_ONESHOT-and-set-.patch). I have had a peak at the 'current' pkg package and noted that the libpadlock.so is contained within it, but I can't fathom out if it is installed along with the userland OpenSSL package. I have tried to force the base OpenSSL to use libpadlock.so from this file, but I get a segmentation fault (no doubt due to the base version being compiled against different binaries).
Btw, I am new to FreeBSD - I've spent hours at this. So, if you can tollerate a such a N00b, it would be greatly appreciated.
So, it is possible to get the required engine libraries for compiled against the base openSSL so I can enable padlock acceleration? Or even instructions on how to compile it myself (sources for the version included with the base?) If not, is there a way to customise the installation of the package from PKG to ensure it's installation includes the additional engine libraries that are in the package (I don't think they are installed by default, either that or I am running openssl from the base install, in which case, how can I change that?). Failing this, how can I compile a later version when such files are missing?
I know that the random number generator is percieved as unsafe, and compromised, however I wouldn't be using it for this use, I will be using it purely for it's hardware hashing and AES acceleration (randomness goes through Yammer as far as I am aware anyway).
I've spent hours on this, and I'm frustrated and tired. Any pointers on where I can pick up from in the morning would be great.
Ideally I'd like to enable padlock support with the 'base' install of OpenSSL. But if not, another local copy will suffice.
Cheers.
[Edit] Just to confirm that the hardware features of this ancient CPU are seen by FreeBSD - it's now just a matter of getting OpenSSL to play ball [/Edit]