SABnzbd Forums

Hi Shypike,

Something to keep an eye on:
http://bazaar.launchpad.net/~stuart-mcl ... vision/168

Add call for load_builtin_engines(). This
enables the use of any available hardware
acceleration for performance.

Not sure if it's been committed to mainline pyopenssl yet.

Synology is starting to ship NAS devices with freescale ppc cpus and these cpus come with a hardware decryption/encryption engine.
Also, all modern Intel/AMD cpus have AES-NI. This has been in Intel CPUs since Westmere.

Supporting the hardware engine essentially means "free" SSL in terms of CPU cycles.
This is especially important for these new low-power 1ghz Dual-core Freescale PPCs cpus that are starting to find their way into NASes as an Atom alternative.

Also I noticed SAB is still using 0.11 which is 2 years old, 0.13 is out: https://launchpad.net/pyopenssl/main/0.13

The OpenSSL libraries are very awkward things to use and we've had loads of problems with them.
That's the reason we seldom change them, especially not in maintenance releases.
Something to consider for 0.8.0.
BTW: for NAS systems you need to approach the package creators.
SABnzbd uses whatever is on the system or in the package.
There are only two exceptions to this: the Windows and the OSX binaries.

Thanks for the tip.