Still: EPEL6 doesn't contain @rpm5.org code and I can hardly "trust"
linkage against hostile sources from projects that (for me and
mostly the @rpm5.org project) are non-participatory and "hostile".
I prefer
--with-beecrypt=internal
for building @rpm5.org (nothing else links BeeCrypt because of
Red Hat removing in RHEL).
And I still prefer BeeCrypt as the highest performing crypto
framework I have measured. The ordering for performance
was
BeeCrypt
NSS
opessl
and BeeCrypt was ~10% faster than NSS at the time.
The current state of RPM+crypto performance should likely be re-measured using
rpm -Va --use-crypto=XX --stats
and published.
Thank you!
Still: EPEL6 doesn't contain @rpm5.org code and I can hardly "trust"
linkage against hostile sources from projects that (for me and
mostly the @rpm5.org project) are non-participatory and "hostile".
I prefer beecrypt= internal
--with-
for building @rpm5.org (nothing else links BeeCrypt because of
Red Hat removing in RHEL).
And I still prefer BeeCrypt as the highest performing crypto
framework I have measured. The ordering for performance
was
BeeCrypt
NSS
opessl
and BeeCrypt was ~10% faster than NSS at the time.
The current state of RPM+crypto performance should likely be re-measured using
rpm -Va --use-crypto=XX --stats
and published.