Hi all,
I released the intel-aes package which has support for AESNI (and as a
fallback uses the same C code as AES, both with Thomas's
Crypto.Classes.BlockCipher interface).
But it has a long way to go to be portable. I'm afraid of exactly these
sorts of compiler problems. For arguments sake,
OK, now I'm sure I tried it before: I tried switching Haskellers over
to AES with that code change you mention, and it results in runtime
crashes (I assume segfaults, I didn't really look into it too much).
So Svein, please disregard my requested code change, it's a bad idea.
Michael
On Fri, Feb
On Fri, Feb 04, 2011 at 08:00:24AM +0200, Michael Snoyman wrote:
Hi everyone,
Does anyone else have trouble installing the AES package on a 32-bit
system? My system at home installs it just fine, but my VPS chokes
with the following error messages (plus a bunch of warnings):
On Fri, Feb 4, 2011 at 11:00 AM, Vincent Hanquez t...@snarc.org wrote:
On Fri, Feb 04, 2011 at 08:00:24AM +0200, Michael Snoyman wrote:
Hi everyone,
Does anyone else have trouble installing the AES package on a 32-bit
system? My system at home installs it just fine, but my VPS chokes
with
On Fri, Feb 04, 2011 at 06:11:38AM +, Daniel Peebles wrote:
Knowing nothing about the package or its code, it looks like a typo to me.
The stdint.h naming of types would have it be uint64_t, not uint_64t. Could
that be it?
While it does indeed solve the problem, technically the whole code
Hi everyone,
Does anyone else have trouble installing the AES package on a 32-bit
system? My system at home installs it just fine, but my VPS chokes
with the following error messages (plus a bunch of warnings):
cbits/ctr_inc.c:11:0:
error: 'uint_64t' undeclared (first use in this function)
Knowing nothing about the package or its code, it looks like a typo to me.
The stdint.h naming of types would have it be uint64_t, not uint_64t. Could
that be it?
On Fri, Feb 4, 2011 at 6:00 AM, Michael Snoyman mich...@snoyman.com wrote:
Hi everyone,
Does anyone else have trouble installing
Wow, I thought I'd tried that before, I guess not. Yes, that compiles,
and an initial test seems that it does not break at runtime either.
I'll email the author and see if he can make that change.
Michael
On Fri, Feb 4, 2011 at 8:11 AM, Daniel Peebles pumpkin...@gmail.com wrote:
Knowing nothing
