>OpenSSL directly talks to the crypto engine via a proprietary interface >that the FW/driver exposes to userspace. The *data* flow does not cross >the linux kernel crypto API
No, OpenSSL doesn't directly talk to the crypto engine via a proprietary interface that the FW/driver exposes to userspace. "cryptodev engine" is NOT the "HW engine" chip vendor provides. It's a common interface and its source is not from chip vendor. Please refer to: https://github.com/cryptodev-linux/cryptodev-linux https://openwrt.org/docs/techref/hardware/cryptographic.hardware.accelerators Tony Antonio Quartulli <a...@unstable.cc> 于2020年11月26日周四 上午12:19写道： > Hi Tony, > > > OpenVPN-> openssl->crypodev engine->cryptodev-linux->Linux kernel crypto > API->HW engine crypto API-> HW engine driver-> HW engine > > Now I understand better what you have in mind. > > To the best of my knowledge, this is not how it works. > > OpenSSL directly talks to the crypto engine via a proprietary interface > that the FW/driver exposes to userspace. The *data* flow does not cross > the linux kernel crypto API. > > Moist of the time this special interfaces are made "to work with openssl > only", so I am not even sure how the kernel API could use it. > > Do you have any pointer saying otherwise? > > > -- > Antonio Quartulli > >
_______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
