Arch Linux

deadfall

Member

Registered: 2010-08-12

Posts: 1

openssl, openssh & via padlock

Hi,

I am having some inconsistencies with openssl using my via cpu.

Firstly, with the default config file I get the following speeds, first line default engine, second line padlock

# openssl speed -evp aes-128-ecb [-engine padlock]
type             16 bytes     64 bytes    256 bytes   1024 bytes   8192 bytes
aes-128-ecb       8866.22k     9166.51k     9264.21k     9289.05k     9297.92k
aes-128-ecb      88659.47k   315260.46k   823743.66k  1309561.86k  1581550.25k

As you can see, a big difference.

After adding the following into /etc/ssl/openssl.cnf to try and force openssl to use the padlock engine as default:

openssl_conf = openssl_def

[openssl_def]
engines = openssl_engines

[openssl_engines]
padlock = padlock_engine

[padlock_engine]
default_algorithms = ALL

and I get the following speeds

type             16 bytes     64 bytes    256 bytes   1024 bytes   8192 bytes
aes-128-ecb      53334.24k   135585.00k   224817.66k   294245.03k   349088.43k

a big difference than the second run, especially with the larger bytes.  Any pointers on why?

Also, what is the status of hardware crypto with arch's openssh package? I used to use a package from AUR, but now I can't find anything in there.

fijam

Member

Registered: 2009-02-03

Posts: 244

Website

Re: openssl, openssh & via padlock

The status is that it used to work well with stock packages up until openssh 5.6p-2. I suppose upstream fucked up in 5.7 and nobody noticed. Will file a bug and see how it goes.

fijam

Member

Registered: 2009-02-03

Posts: 244

Website

Re: openssl, openssh & via padlock

It's fixed https://bugzilla.mindrot.org/show_bug.cgi?id=1882 . Will probably be a part of the next upstream release.