Commit a8f12c4e authored by Niels Möller's avatar Niels Möller

*** empty log message ***

Rev: nettle/ChangeLog:1.203
Rev: nettle/NEWS:1.13
Rev: nettle/misc/plan.html:1.2
parent 8ab9b5dd
2011-07-01 Niels Mller <nisse@lysator.liu.se> 2011-07-01 Niels Mller <nisse@lysator.liu.se>
* cbc.c (CBC_BUFFER_LIMIT): Reduced to 512 bytes.
(cbc_decrypt): For in-place operation, use overlapping memxor3 and
eliminate a memcpy.
* ctr.c (ctr_crypt): Reorganized to call the encryption function * ctr.c (ctr_crypt): Reorganized to call the encryption function
with several blocks at a time. Handle the case of a single block with several blocks at a time. Handle the case of a single block
specially. specially.
......
...@@ -38,6 +38,8 @@ NEWS for the 2.2 release ...@@ -38,6 +38,8 @@ NEWS for the 2.2 release
* Optimized memxor using word rather than byte operations. * Optimized memxor using word rather than byte operations.
Both generic C and x86_64 assembler. Both generic C and x86_64 assembler.
* Eliminated a memcpy for in-place CBC decrypt.
Miscellaneous: Miscellaneous:
* In command line tools, no longer support -? for requesting * In command line tools, no longer support -? for requesting
......
...@@ -14,7 +14,7 @@ ...@@ -14,7 +14,7 @@
<h1> Plans for the Nettle-2.1 release </h1> <h1> Plans for the Nettle-2.1 release </h1>
<p> This is an attempt at defining a development target for <p> This is an attempt at defining a development target for
Nettle-2.1, inspired by similar pages for recent GMP releases. Nettle-2.1, inspired by similar pages for recent GMP releases.
[Last updated 2011-06-15]</p> [Last updated 2011-07-01]</p>
<h2> Color codes </h2> <h2> Color codes </h2>
<p class='should'> <p class='should'>
This really ought to be done before release This really ought to be done before release
...@@ -32,17 +32,17 @@ ...@@ -32,17 +32,17 @@
<p class='done'> <p class='done'>
Replace remaining GPLd code: serpent and blowfish. Replace remaining GPLd code: serpent and blowfish.
</p> </p>
<p class='should'> <p class='done'>
Decide which flavor of LGPL to use: LGPLv2+, LGPLv3+, or dual Decide which flavor of LGPL to use: LGPLv2+, LGPLv3+, or dual
license LGPLv3+ and GPLv2. Leaning towards the simplest option, LGPLv2+. license LGPLv3+ and GPLv2. Leaning towards the simplest option, LGPLv2+.
</p> </p>
<h2> Documentation </h2> <h2> Documentation </h2>
<p class='should'> <p class='done'>
Update documentation regarding license change and serpent Update documentation regarding license change and serpent
copyrights. copyrights.
</p> </p>
<p class='should'> <p class='done'>
Update NEWS file. Update NEWS file.
</p> </p>
<h2> Bug fixes </h2> <h2> Bug fixes </h2>
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment