[erlang-patches] True streaming of AES CTR

[Henrik Nord]

On 04/29/2011 07:14 PM, Travis Jensen wrote:
> I've added a pull request to github for a change to the crypto module 
> that allows true streaming of AES CTR mode.  I'm afraid I didn't get 
> things quite right on the formatting of the pull request (I'm more 
> familiar with Mercurial than Git), but here it is, anyway: 
> https://github.com/erlang/otp/pull/12
>
> Basically, this change makes AES CTR behave similarly to the RC4 
> implementation.
>
> An example usage looks like:
>
> State = crypto:aes_ctr_state_init(Key, IV),
> { Cipher, State2 } = crypto:aes_ctr_encrypt_with_state(State, Data),
> { Cipher2, State3 } = crypto:aes_ctr_encrypt_with_state(State2, Data),
>
> I've used the existing AES CTR tests to implement tests for it as 
> well.  If I need to reformat the patch, I can certainly do that, but 
> it really pretty minor.
>
> tj
> -- 
> *Travis Jensen*
> *
> *Read the Software Maven @ http://softwaremaven.innerbrane.com/
> Read my LinkedIn profile @ http://www.linkedin.com/in/travisjensen
> Read my Twitter mumblings @ http://twitter.com/SoftwareMaven
> Send me email @ travis.jensen@REDACTED <mailto:travis.jensen@REDACTED>
>
> /*What kind of guy calls himself the Software Maven???*/
>
>
> _______________________________________________
> erlang-patches mailing list
> erlang-patches@REDACTED
> http://erlang.org/mailman/listinfo/erlang-patches

Please don't use pull requests as that is not the correct channel to get 
the patch into Erlang/OTP

Have a look at the patch guide.

https://github.com/erlang/otp/wiki/Submitting-patches
https://github.com/erlang/otp/wiki/Writing-good-commit-messages
https://github.com/erlang/otp/wiki/FAQ%3A-What-kind-of-patches-will-be-approved%3F

Also please make sure you only have relevant commits in your branch
https://github.com/erlang/otp/wiki/Refining-patches-using-git

Thank you for the contribution!



-- 
/Henrik Nord Erlang/OTP

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-patches/attachments/20110502/3493c97e/attachment.htm>