On 03/10/2013 04:13, Ray Dillinger wrote:
On 10/02/2013 02:13 PM, Brian Gladman wrote:
The NIST specification only eliminated Rijndael options - none of the
Rijndael options included in AES were changed in any way by NIST.
Leaving aside the question of whether anyone weakened
was heavily involved in writing the AES specification as
eventually used by NIST, I can confirm what John is saying.
The NIST specification only eliminated Rijndael options - none of the
Rijndael options included in AES were changed in any way by NIST.
Brian Gladman
and software.
Brian Gladman
___
The cryptography mailing list
cryptography@metzdowd.com
http://www.metzdowd.com/mailman/listinfo/cryptography
- Original Message -
From: Jonathan Thornburg jth...@astro.indiana.edu
To: Brian Gladman b...@gladman.plus.com
Cc: John Gilmore g...@toad.com; Peter Gutmann
pgut...@cs.auckland.ac.nz; cryptography@metzdowd.com;
s...@cs.columbia.edu
Sent: Monday, February 02, 2009 3:53 AM
Subject: Re
not
proved competitive. But PPERM looks interesting here as well.
Brian Gladman
-
The Cryptography Mailing List
Unsubscribe by sending unsubscribe cryptography to [EMAIL PROTECTED]
are still awaiting a decision on this.
Brian Gladman
-
The Cryptography Mailing List
Unsubscribe by sending unsubscribe cryptography to [EMAIL PROTECTED]
in applications
in which about half the time is spent in encryption and half in other
higher level activities.
Can I hence assume that your benchmark is being run at application level
rather than algorithm level? If not why is the ratio only 22% on the
PPC-32?
Brian Gladman
round than AES-128.
My guess is that you are thinking about Rijndael with a 256 bit block
and a 256 bit key.
Brian Gladman
-
The Cryptography Mailing List
Unsubscribe by sending unsubscribe cryptography to [EMAIL PROTECTED]
not
understand security).
Does anyone know the current state of affairs on this issue within the
Trusted Computing Group (and the marketed products of its members)?
Brian Gladman
-
The Cryptography Mailing List
Unsubscribe
as one integrated API call, aka:
encrypt(key[], in[], out[], no_of_blocks)
I hope this helps but if not I will try and answer any other questions.
Brian Gladman
-
The Cryptography Mailing List
Unsubscribe by sending
Eric Young wrote:
Quoting Brian Gladman [EMAIL PROTECTED]:
Ian Grigg wrote:
Jack Lloyd also passed along lots of good comments I'd
like to forward (having gained permission) FTR. I've
edited them for brevity and pertinence.
[snip]
I'm obviously being naive here ... I had thought
algorithm that is in use.
Brian Gladman
-
The Cryptography Mailing List
Unsubscribe by sending unsubscribe cryptography to [EMAIL PROTECTED]
://fp.gladman.plus.com/AES/index.htm
I focus mainly on the combined encryption/authentication modes but I
only cover those that I believe are free of licensing costs.
Brian Gladman
-
The Cryptography Mailing List
Unsubscribe by sending unsubscribe
either.
[snip]
Brian Gladman
-
The Cryptography Mailing List
Unsubscribe by sending unsubscribe cryptography to [EMAIL PROTECTED]
14 matches
Mail list logo
