I'm trying to add HMAC support to an OpenSSL engine. Without it, after all, the throughput for most hardware accellerators is cut by at least a factor of two when actually used for SSL/TLS: every record has to talk to the hardware twice, instead of once, to do the raw hash processing for the MAC.
I see there are now OIDs allocated for HMAC, but I'm unsure whether it's actually possible to register an engine which supports them -- everything in the digests list for an engine has message-digest datastructures at the interface to the rest of OpenSSL, but HMAC has its own context structures which look quite different. Am I barking up the wrong tree? Where is the right place to start with this? -- Thor Lancelot Simon [email protected] "Even experienced UNIX users occasionally enter rm *.* at the UNIX prompt only to realize too late that they have removed the wrong segment of the directory structure." - Microsoft WSS whitepaper ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [email protected] Automated List Manager [email protected]
