But after examining SSL code I've realized that SSL layer *always* feeds
libcrypto with *unaligned* data:-( So I'm considering to tweak the SSL
code so that message payload gets aligned at 64-bit boundary. But before
I do so I'd like to hear opinions on this.
Sounds like a good idea,
Andy Polyakov wrote:
But after examining SSL code I've realized that SSL layer *always* feeds
libcrypto with *unaligned* data:-( So I'm considering to tweak the SSL
code so that message payload gets aligned at 64-bit boundary. But before
I do so I'd like to hear opinions on this.
Andy Polyakov wrote:
BTW, although malloc() returns a pointer "suitable aligned", that
doesn't mean it is fast. The comment refers to the fact that some CPUs
don't like fetching a long (say) except off a 4-byte boundary.
"Some CPUs"? It should say "all, but Intel", shouldn't it? And
OpenSSL STATUS Last modified at
__ $Date: 1999/08/14 20:49:37 $
DEVELOPMENT STATE
o OpenSSL 0.9.5: Under development...
o OpenSSL 0.9.4: Released on August 09th, 1999
o OpenSSL 0.9.3a: Released on May
Having a crypto API (pkcs11?) within the product would be very welcome.
Personally, I think only asymmetric private key operations should be
performed in hardware and symmetric key operation would be performed as
they are now. This is because some applications would use smart cards
which
