<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 04/29/2011 07:14 PM, Travis Jensen wrote:
<blockquote
cite="mid:BANLkTin=5fEQKFhM9J5_2ZeMgQq28OSOVA@mail.gmail.com"
type="cite">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: <a moz-do-not-send="true"
href="https://github.com/erlang/otp/pull/12">https://github.com/erlang/otp/pull/12</a>
<div>
<br>
</div>
<div>Basically, this change makes AES CTR behave similarly to the
RC4 implementation.</div>
<div><br>
</div>
<div>An example usage looks like:</div>
<div><br>
</div>
<div><font class="Apple-style-span" face="'courier new',
monospace">State = crypto:aes_ctr_state_init(Key, IV),</font></div>
<div><font class="Apple-style-span" face="'courier new',
monospace">{ Cipher, State2 } =
crypto:aes_ctr_encrypt_with_state(State, Data),<br clear="all">
<meta charset="utf-8">
{ Cipher2, State3 } =
crypto:aes_ctr_encrypt_with_state(State2, Data),<br
clear="all">
</font><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>tj</div>
<div>
-- <br>
<b><span style="font-size: large;">Travis Jensen</span></b>
<div><span style="font-size: large;"><b><br>
</b></span>Read the Software Maven @ <a
moz-do-not-send="true"
href="http://softwaremaven.innerbrane.com/" target="_blank">http://softwaremaven.innerbrane.com/</a><br>
Read my LinkedIn profile @ <a moz-do-not-send="true"
href="http://www.linkedin.com/in/travisjensen"
target="_blank">http://www.linkedin.com/in/travisjensen</a><br>
Read my Twitter mumblings @ <a moz-do-not-send="true"
href="http://twitter.com/SoftwareMaven" target="_blank">http://twitter.com/SoftwareMaven</a><br>
Send me email @ <a moz-do-not-send="true"
href="mailto:travis.jensen@gmail.com" target="_blank">travis.jensen@gmail.com</a>
<div><br>
</div>
<div><i>*What kind of guy calls himself the Software Maven???*</i></div>
</div>
<br>
</div>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
erlang-patches mailing list
<a class="moz-txt-link-abbreviated" href="mailto:erlang-patches@erlang.org">erlang-patches@erlang.org</a>
<a class="moz-txt-link-freetext" href="http://erlang.org/mailman/listinfo/erlang-patches">http://erlang.org/mailman/listinfo/erlang-patches</a>
</pre>
</blockquote>
<br>
Please don't use pull requests as that is not the correct channel to
get the patch into Erlang/OTP<br>
<br>
Have a look at the patch guide.<br>
<br>
<a class="moz-txt-link-freetext"
href="https://github.com/erlang/otp/wiki/Submitting-patches">https://github.com/erlang/otp/wiki/Submitting-patches</a><br>
<a class="moz-txt-link-freetext" href="https://github.com/erlang/otp/wiki/Writing-good-commit-messages">https://github.com/erlang/otp/wiki/Writing-good-commit-messages</a><br>
<a class="moz-txt-link-freetext"
href="https://github.com/erlang/otp/wiki/FAQ%3A-What-kind-of-patches-will-be-approved%3F">https://github.com/erlang/otp/wiki/FAQ%3A-What-kind-of-patches-will-be-approved%3F</a><br>
<br>
Also please make sure you only have relevant commits in your branch<br>
<a class="moz-txt-link-freetext"
href="https://github.com/erlang/otp/wiki/Refining-patches-using-git">https://github.com/erlang/otp/wiki/Refining-patches-using-git</a><br>
<br>
Thank you for the contribution! <br>
<br>
<br>
<br>
<pre class="moz-signature" cols="72">--
/Henrik Nord Erlang/OTP</pre>
</body>
</html>