Re: Crypto Algorithm Calling Interfaces
From: David Wagner (daw_at_taverner.cs.berkeley.edu)
Date: 05/13/05
- Next message: jEL: "Re: linear congruential pseudorandom number generator question"
- Previous message: BRG: "Crypto Algorithm Calling Interfaces"
- In reply to: BRG: "Crypto Algorithm Calling Interfaces"
- Next in thread: Mike Amling: "Re: Crypto Algorithm Calling Interfaces"
- Reply: Mike Amling: "Re: Crypto Algorithm Calling Interfaces"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Fri, 13 May 2005 08:55:04 +0000 (UTC)
BRG wrote:
>At the risk of starting a flame war, I would be interested to hear
>people's preferences _and_ their rationale for their choice.
I don't have any strong opinions, but:
Have you considered something like the following?
AES_encrypt(out, in, context);
AES_cbc_encrypt(out, in, nblocks, key, iv);
Rationale: this ordering of parameters is intended to be parallel
to the order of parameters to memcpy(), strcpy(), etc.
- Next message: jEL: "Re: linear congruential pseudorandom number generator question"
- Previous message: BRG: "Crypto Algorithm Calling Interfaces"
- In reply to: BRG: "Crypto Algorithm Calling Interfaces"
- Next in thread: Mike Amling: "Re: Crypto Algorithm Calling Interfaces"
- Reply: Mike Amling: "Re: Crypto Algorithm Calling Interfaces"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
