[openssl.org #1665] Contribution of aes.pod

[Green, Paul via RT]

I had some time today, so I created aes.pod.  I make no claim to any
particular expertise in OpenSSL; I simply know how to read C code.
Please use this file however you see fit.  I encourage folks who are
experts in OpenSSL to review it for accuracy.

A couple of comments:

1. I took the liberty of "cleaning up" some of the declarations found in
openssl/aes.h for documentation purposes. For example:

                unsigned char *ivec
        became  unsigned char ivec[AES_BLOCK_SIZE]

                AES_KEY *key
        became  AES_KEY *schedule

2. I tried to write a more complete description than I found in the file
I started with (blowfish.pod). Raise the bar, so to speak. But if you
don't want the extra info, do with it as you will.

 <<aes.pod>> 

Thanks
PG
--
Paul Green, Senior Technical Consultant, Stratus Technologies.
Voice: +1 978-461-7557; FAX: +1 978-461-3610; Mobile: +1 (978) 235-2451;
AIM: PaulGreen

Title: Contribution of aes.pod

I had some time today, so I created aes.pod.  I make no claim to any particular expertise in OpenSSL; I simply know how to read C code.  Please use this file however you see fit.  I encourage folks who are experts in OpenSSL to review it for accuracy.

A couple of comments:

1. I took the liberty of "cleaning up" some of the declarations found in openssl/aes.h for documentation purposes. For example:

                unsigned char *ivec
        became  unsigned char ivec[AES_BLOCK_SIZE]

                AES_KEY *key
        became  AES_KEY *schedule

2. I tried to write a more complete description than I found in the file I started with (blowfish.pod). Raise the bar, so to speak. But if you don't want the extra info, do with it as you will.

<<aes.pod>>

Thanks
PG
--
Paul Green, Senior Technical Consultant, Stratus Technologies.
Voice: +1 978-461-7557; FAX: +1 978-461-3610; Mobile: +1 (978) 235-2451; AIM: PaulGreen

aes.pod
Description: Binary data