ChangeLog 23 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480
  1. * Version 1.0.15
  2. - The default password hashing algorithm is now Argon2id. The
  3. `pwhash_str_verify()` function can still verify Argon2i hashes
  4. without any changes, and `pwhash()` can still compute Argon2i hashes
  5. as well.
  6. - The aes128ctr primitive was removed. It was slow, non-standard, not
  7. authenticated, and didn't seem to be used by any opensource project.
  8. - Argon2id required at least 3 passes like Argon2i, despite a minimum
  9. of `1` as defined by the `OPSLIMIT_MIN` constant. This has been fixed.
  10. - The secretstream construction was slightly changed to be consistent
  11. with forthcoming variants.
  12. - The Javascript and Webassembly versions have been merged, and the
  13. module now returns a `.ready` promise that will resolve after the
  14. Webassembly code is loaded and compiled.
  15. - Note that due to these incompatible changes, the library version
  16. major was bumped up.
  17. * Version 1.0.14
  18. - iOS binaries should now be compatible with WatchOS and TVOS.
  19. - WebAssembly is now officially supported. Special thanks to
  20. @facekapow and @pepyakin who helped to make it happen.
  21. - Internal consistency checks failing and primitives used with
  22. dangerous/out-of-bounds/invalid parameters used to call abort(3).
  23. Now, a custom handler *that doesn't return* can be set with the
  24. `set_sodium_misuse()` function. It still aborts by default or if the
  25. handler ever returns. This is not a replacement for non-fatal,
  26. expected runtime errors. This handler will be only called in
  27. unexpected situations due to potential bugs in the library or in
  28. language bindings.
  29. - `*_MESSAGEBYTES_MAX` macros (and the corresponding
  30. `_messagebytes_max()` symbols) have been added to represent the
  31. maximum message size that can be safely handled by a primitive.
  32. Language bindings are encouraged to check user inputs against these
  33. maximum lengths.
  34. - The test suite has been extended to cover more edge cases.
  35. - crypto_sign_ed25519_pk_to_curve25519() now rejects points that are
  36. not on the curve, or not in the main subgroup.
  37. - Further changes have been made to ensure that smart compilers will
  38. not optimize out code that we don't want to be optimized.
  39. - Visual Studio solutions are now included in distribution tarballs.
  40. - The `sodium_runtime_has_*` symbols for CPU features detection are
  41. now defined as weak symbols, i.e. they can be replaced with an
  42. application-defined implementation. This can be useful to disable
  43. AVX* when temperature/power consumption is a concern.
  44. - `crypto_kx_*()` now aborts if called with no non-NULL pointers to
  45. store keys to.
  46. - SSE2 implementations of `crypto_verify_*()` have been added.
  47. - Passwords can be hashed using a specific algorithm with the new
  48. `crypto_pwhash_str_alg()` function.
  49. - Due to popular demand, base64 encoding (`sodium_bin2base64()`) and
  50. decoding (`sodium_base642bin()`) have been implemented.
  51. - A new `crypto_secretstream_*()` API was added to safely encrypt files
  52. and multi-part messages.
  53. - The `sodium_pad()` and `sodium_unpad()` helper functions have been
  54. added in order to add & remove padding.
  55. - An AVX512 optimized implementation of Argon2 has been added (written
  56. by Ondrej Mosnáček, thanks!)
  57. - The `crypto_pwhash_str_needs_rehash()` function was added to check if
  58. a password hash string matches the given parameters, or if it needs an
  59. update.
  60. - The library can now be compiled with recent versions of
  61. emscripten/binaryen that don't allow multiple variables declarations
  62. using a single `var` statement.
  63. * Version 1.0.13
  64. - Javascript: the sumo builds now include all symbols. They were
  65. previously limited to symbols defined in minimal builds.
  66. - The public `crypto_pwhash_argon2i_MEMLIMIT_MAX` constant was
  67. incorrectly defined on 32-bit platforms. This has been fixed.
  68. - Version 1.0.12 didn't compile on OpenBSD/i386 using the base gcc
  69. compiler. This has been fixed.
  70. - The Android compilation scripts have been updated for NDK r14b.
  71. - armv7s-optimized code was re-added to iOS builds.
  72. - An AVX2 optimized implementation of the Argon2 round function was
  73. added.
  74. - The Argon2id variant of Argon2 has been implemented. The
  75. high-level `crypto_pwhash_str_verify()` function automatically detects
  76. the algorithm and can verify both Argon2i and Argon2id hashed passwords.
  77. The default algorithm for newly hashed passwords remains Argon2i in
  78. this version to avoid breaking compatibility with verifiers running
  79. libsodium <= 1.0.12.
  80. - A `crypto_box_curve25519xchacha20poly1305_seal*()` function set was
  81. implemented.
  82. - scrypt was removed from minimal builds.
  83. - libsodium is now available on NuGet.
  84. * Version 1.0.12
  85. - Ed25519ph was implemented, adding a multi-part signature API
  86. (`crypto_sign_init()`, `crypto_sign_update()`, `crypto_sign_final_*()`).
  87. - New constants and related accessors have been added for Scrypt and
  88. Argon2.
  89. - XChaCha20 has been implemented. Like XSalsa20, this construction
  90. extends the ChaCha20 cipher to accept a 192-bit nonce. This makes it safe
  91. to use ChaCha20 with random nonces.
  92. - `crypto_secretbox`, `crypto_box` and `crypto_aead` now offer
  93. variants leveraging XChaCha20.
  94. - SHA-2 is about 20% faster, which also gives a speed boost to
  95. signature and signature verification.
  96. - AVX2 implementations of Salsa20 and ChaCha20 have been added. They
  97. are twice as fast as the SSE2 implementations. The speed gain is
  98. even more significant on Windows, that previously didn't use
  99. vectorized implementations.
  100. - New high-level API: `crypto_kdf`, to easily derive one or more
  101. subkeys from a master key.
  102. - Siphash with a 128-bit output has been implemented, and is
  103. available as `crypto_shorthash_siphashx_*`.
  104. - New `*_keygen()` helpers functions have been added to create secret
  105. keys for all constructions. This improves code clarity and can prevent keys
  106. from being partially initialized.
  107. - A new `randombytes_buf_deterministic()` function was added to
  108. deterministically fill a memory region with pseudorandom data. This
  109. function can especially be useful to write reproducible tests.
  110. - A preliminary `crypto_kx_*()` API was added to compute shared session
  111. keys.
  112. - AVX2 detection is more reliable.
  113. - The pthreads library is not required any more when using MingW.
  114. - `contrib/Findsodium.cmake` was added as an example to include
  115. libsodium in a project using cmake.
  116. - Compatibility with gcc 2.x has been restored.
  117. - Minimal builds can be checked using `sodium_library_minimal()`.
  118. - The `--enable-opt` compilation switch has become compatible with more
  119. platforms.
  120. - Android builds are now using clang on platforms where it is
  121. available.
  122. * Version 1.0.11
  123. - `sodium_init()` is now thread-safe, and can be safely called multiple
  124. times.
  125. - Android binaries now properly support 64-bit Android, targeting
  126. platform 24, but without breaking compatibility with platforms 16 and
  127. 21.
  128. - Better support for old gcc versions.
  129. - On FreeBSD, core dumps are disabled on regions allocated with
  130. sodium allocation functions.
  131. - AVX2 detection was fixed, resulting in faster Blake2b hashing on
  132. platforms where it was not properly detected.
  133. - The Sandy2x Curve25519 implementation was not as fast as expected
  134. on some platforms. This has been fixed.
  135. - The NativeClient target was improved. Most notably, it now supports
  136. optimized implementations, and uses pepper_49 by default.
  137. - The library can be compiled with recent Emscripten versions.
  138. Changes have been made to produce smaller code, and the default heap
  139. size was reduced in the standard version.
  140. - The code can now be compiled on SLES11 service pack 4.
  141. - Decryption functions can now accept a NULL pointer for the output.
  142. This checks the MAC without writing the decrypted message.
  143. - crypto_generichash_final() now returns -1 if called twice.
  144. - Support for Visual Studio 2008 was improved.
  145. * Version 1.0.10
  146. - This release only fixes a compilation issue reported with some older
  147. gcc versions. There are no functional changes over the previous release.
  148. * Version 1.0.9
  149. - The Javascript target now includes a `--sumo` option to include all
  150. the symbols of the original C library.
  151. - A detached API was added to the ChaCha20-Poly1305 and AES256-GCM
  152. implementations.
  153. - The Argon2i password hashing function was added, and is accessible
  154. directly and through a new, high-level `crypto_pwhash` API. The scrypt
  155. function remains available as well.
  156. - A speed-record AVX2 implementation of BLAKE2b was added (thanks to
  157. Samuel Neves).
  158. - The library can now be compiled using C++Builder (thanks to @jcolli44)
  159. - Countermeasures for Ed25519 signatures malleability have been added
  160. to match the irtf-cfrg-eddsa draft (note that malleability is irrelevant to
  161. the standard definition of signature security). Signatures with a small-order
  162. `R` point are now also rejected.
  163. - Some implementations are now slightly faster when using the Clang
  164. compiler.
  165. - The HChaCha20 core function was implemented (`crypto_core_hchacha20()`).
  166. - No-op stubs were added for all AES256-GCM public functions even when
  167. compiled on non-Intel platforms.
  168. - `crypt_generichash_blake2b_statebytes()` was added.
  169. - New macros were added for the IETF variant of the ChaCha20-Poly1305
  170. construction.
  171. - The library can now be compiled on Minix.
  172. - HEASLR is now enabled on MinGW builds.
  173. * Version 1.0.8
  174. - Handle the case where the CPU supports AVX, but we are running
  175. on an hypervisor with AVX disabled/not supported.
  176. - Faster (2x) scalarmult_base() when using the ref10 implementation.
  177. * Version 1.0.7
  178. - More functions whose return value should be checked have been
  179. tagged with `__attribute__ ((warn_unused_result))`: `crypto_box_easy()`,
  180. `crypto_box_detached()`, `crypto_box_beforenm()`, `crypto_box()`, and
  181. `crypto_scalarmult()`.
  182. - Sandy2x, the fastest Curve25519 implementation ever, has been
  183. merged in, and is automatically used on CPUs supporting the AVX
  184. instructions set.
  185. - An SSE2 optimized implementation of Poly1305 was added, and is
  186. twice as fast as the portable one.
  187. - An SSSE3 optimized implementation of ChaCha20 was added, and is
  188. twice as fast as the portable one.
  189. - Faster `sodium_increment()` for common nonce sizes.
  190. - New helper functions have been added: `sodium_is_zero()` and
  191. `sodium_add()`.
  192. - `sodium_runtime_has_aesni()` now properly detects the CPU flag when
  193. compiled using Visual Studio.
  194. * Version 1.0.6
  195. - Optimized implementations of Blake2 have been added for modern
  196. Intel platforms. `crypto_generichash()` is now faster than MD5 and SHA1
  197. implementations while being far more secure.
  198. - Functions for which the return value should be checked have been
  199. tagged with `__attribute__ ((warn_unused_result))`. This will
  200. intentionally break code compiled with `-Werror` that didn't bother
  201. checking critical return values.
  202. - The `crypto_sign_edwards25519sha512batch_*()` functions have been
  203. tagged as deprecated.
  204. - Undocumented symbols that were exported, but were only useful for
  205. internal purposes have been removed or made private:
  206. `sodium_runtime_get_cpu_features()`, the implementation-specific
  207. `crypto_onetimeauth_poly1305_donna()` symbols,
  208. `crypto_onetimeauth_poly1305_set_implementation()`,
  209. `crypto_onetimeauth_poly1305_implementation_name()` and
  210. `crypto_onetimeauth_pick_best_implementation()`.
  211. - `sodium_compare()` now works as documented, and compares numbers
  212. in little-endian format instead of behaving like `memcmp()`.
  213. - The previous changes should not break actual applications, but to be
  214. safe, the library version major was incremented.
  215. - `sodium_runtime_has_ssse3()` and `sodium_runtime_has_sse41()` have
  216. been added.
  217. - The library can now be compiled with the CompCert compiler.
  218. * Version 1.0.5
  219. - Compilation issues on some platforms were fixed: missing alignment
  220. directives were added (required at least on RHEL-6/i386), a workaround
  221. for a VRP bug on gcc/armv7 was added, and the library can now be compiled
  222. with the SunPro compiler.
  223. - Javascript target: io.js is not supported any more. Use nodejs.
  224. * Version 1.0.4
  225. - Support for AES256-GCM has been added. This requires
  226. a CPU with the aesni and pclmul extensions, and is accessible via the
  227. crypto_aead_aes256gcm_*() functions.
  228. - The Javascript target doesn't use eval() any more, so that the
  229. library can be used in Chrome packaged applications.
  230. - QNX and CloudABI are now supported.
  231. - Support for NaCl has finally been added.
  232. - ChaCha20 with an extended (96 bit) nonce and a 32-bit counter has
  233. been implemented as crypto_stream_chacha20_ietf(),
  234. crypto_stream_chacha20_ietf_xor() and crypto_stream_chacha20_ietf_xor_ic().
  235. An IETF-compatible version of ChaCha20Poly1305 is available as
  236. crypto_aead_chacha20poly1305_ietf_npubbytes(),
  237. crypto_aead_chacha20poly1305_ietf_encrypt() and
  238. crypto_aead_chacha20poly1305_ietf_decrypt().
  239. - The sodium_increment() helper function has been added, to increment
  240. an arbitrary large number (such as a nonce).
  241. - The sodium_compare() helper function has been added, to compare
  242. arbitrary large numbers (such as nonces, in order to prevent replay
  243. attacks).
  244. * Version 1.0.3
  245. - In addition to sodium_bin2hex(), sodium_hex2bin() is now a
  246. constant-time function.
  247. - crypto_stream_xsalsa20_ic() has been added.
  248. - crypto_generichash_statebytes(), crypto_auth_*_statebytes() and
  249. crypto_hash_*_statebytes() have been added in order to retrieve the
  250. size of structures keeping states from foreign languages.
  251. - The JavaScript target doesn't require /dev/urandom or an external
  252. randombytes() implementation any more. Other minor Emscripten-related
  253. improvements have been made in order to support libsodium.js
  254. - Custom randombytes implementations do not need to provide their own
  255. implementation of randombytes_uniform() any more. randombytes_stir()
  256. and randombytes_close() can also be NULL pointers if they are not
  257. required.
  258. - On Linux, getrandom(2) is being used instead of directly accessing
  259. /dev/urandom, if the kernel supports this system call.
  260. - crypto_box_seal() and crypto_box_seal_open() have been added.
  261. - Visual Studio 2015 is now supported.
  262. * Version 1.0.2
  263. - The _easy and _detached APIs now support precalculated keys;
  264. crypto_box_easy_afternm(), crypto_box_open_easy_afternm(),
  265. crypto_box_detached_afternm() and crypto_box_open_detached_afternm()
  266. have been added as an alternative to the NaCl interface.
  267. - Memory allocation functions can now be used on operating systems with
  268. no memory protection.
  269. - crypto_sign_open() and crypto_sign_edwards25519sha512batch_open()
  270. now accept a NULL pointer instead of a pointer to the message size, if
  271. storing this information is not required.
  272. - The close-on-exec flag is now set on the descriptor returned when
  273. opening /dev/urandom.
  274. - A libsodium-uninstalled.pc file to use pkg-config even when
  275. libsodium is not installed, has been added.
  276. - The iOS target now includes armv7s and arm64 optimized code, as well
  277. as i386 and x86_64 code for the iOS simulator.
  278. - sodium_free() can now be called on regions with PROT_NONE protection.
  279. - The Javascript tests can run on Ubuntu, where the node binary was
  280. renamed nodejs. io.js can also be used instead of node.
  281. * Version 1.0.1
  282. - DLL_EXPORT was renamed SODIUM_DLL_EXPORT in order to avoid
  283. collisions with similar macros defined by other libraries.
  284. - sodium_bin2hex() is now constant-time.
  285. - crypto_secretbox_detached() now supports overlapping input and output
  286. regions.
  287. - NaCl's donna_c64 implementation of curve25519 was reading an extra byte
  288. past the end of the buffer containing the base point. This has been
  289. fixed.
  290. * Version 1.0.0
  291. - The API and ABI are now stable. New features will be added, but
  292. backward-compatibility is guaranteed through all the 1.x.y releases.
  293. - crypto_sign() properly works with overlapping regions again. Thanks
  294. to @pysiak for reporting this regression introduced in version 0.6.1.
  295. - The test suite has been extended.
  296. * Version 0.7.1 (1.0 RC2)
  297. - This is the second release candidate of Sodium 1.0. Minor
  298. compilation, readability and portability changes have been made and the
  299. test suite was improved, but the API is the same as the previous release
  300. candidate.
  301. * Version 0.7.0 (1.0 RC1)
  302. - Allocating memory to store sensitive data can now be done using
  303. sodium_malloc() and sodium_allocarray(). These functions add guard
  304. pages around the protected data to make it less likely to be
  305. accessible in a heartbleed-like scenario. In addition, the protection
  306. for memory regions allocated that way can be changed using
  307. sodium_mprotect_noaccess(), sodium_mprotect_readonly() and
  308. sodium_mprotect_readwrite().
  309. - ed25519 keys can be converted to curve25519 keys with
  310. crypto_sign_ed25519_pk_to_curve25519() and
  311. crypto_sign_ed25519_sk_to_curve25519(). This allows using the same
  312. keys for signature and encryption.
  313. - The seed and the public key can be extracted from an ed25519 key
  314. using crypto_sign_ed25519_sk_to_seed() and crypto_sign_ed25519_sk_to_pk().
  315. - aes256 was removed. A timing-attack resistant implementation might
  316. be added later, but not before version 1.0 is tagged.
  317. - The crypto_pwhash_scryptxsalsa208sha256_* compatibility layer was
  318. removed. Use crypto_pwhash_scryptsalsa208sha256_*.
  319. - The compatibility layer for implementation-specific functions was
  320. removed.
  321. - Compilation issues with Mingw64 on MSYS (not MSYS2) were fixed.
  322. - crypto_pwhash_scryptsalsa208sha256_STRPREFIX was added: it contains
  323. the prefix produced by crypto_pwhash_scryptsalsa208sha256_str()
  324. * Version 0.6.1
  325. - Important bug fix: when crypto_sign_open() was given a signed
  326. message too short to even contain a signature, it was putting an
  327. unlimited amount of zeros into the target buffer instead of
  328. immediately returning -1. The bug was introduced in version 0.5.0.
  329. - New API: crypto_sign_detached() and crypto_sign_verify_detached()
  330. to produce and verify ed25519 signatures without having to duplicate
  331. the message.
  332. - New ./configure switch: --enable-minimal, to create a smaller
  333. library, with only the functions required for the high-level API.
  334. Mainly useful for the JavaScript target and embedded systems.
  335. - All the symbols are now exported by the Emscripten build script.
  336. - The pkg-config .pc file is now always installed even if the
  337. pkg-config tool is not available during the installation.
  338. * Version 0.6.0
  339. - The ChaCha20 stream cipher has been added, as crypto_stream_chacha20_*
  340. - The ChaCha20Poly1305 AEAD construction has been implemented, as
  341. crypto_aead_chacha20poly1305_*
  342. - The _easy API does not require any heap allocations any more and
  343. does not have any overhead over the NaCl API. With the password
  344. hashing function being an obvious exception, the library doesn't
  345. allocate and will not allocate heap memory ever.
  346. - crypto_box and crypto_secretbox have a new _detached API to store
  347. the authentication tag and the encrypted message separately.
  348. - crypto_pwhash_scryptxsalsa208sha256*() functions have been renamed
  349. crypto_pwhash_scryptsalsa208sha256*().
  350. - The low-level crypto_pwhash_scryptsalsa208sha256_ll() function
  351. allows setting individual parameters of the scrypt function.
  352. - New macros and functions for recommended crypto_pwhash_* parameters
  353. have been added.
  354. - Similarly to crypto_sign_seed_keypair(), crypto_box_seed_keypair()
  355. has been introduced to deterministically generate a key pair from a seed.
  356. - crypto_onetimeauth() now provides a streaming interface.
  357. - crypto_stream_chacha20_xor_ic() and crypto_stream_salsa20_xor_ic()
  358. have been added to use a non-zero initial block counter.
  359. - On Windows, CryptGenRandom() was replaced by RtlGenRandom(), which
  360. doesn't require the Crypt API.
  361. - The high bit in curve25519 is masked instead of processing the key as
  362. a 256-bit value.
  363. - The curve25519 ref implementation was replaced by the latest ref10
  364. implementation from Supercop.
  365. - sodium_mlock() now prevents memory from being included in coredumps
  366. on Linux 3.4+
  367. * Version 0.5.0
  368. - sodium_mlock()/sodium_munlock() have been introduced to lock pages
  369. in memory before storing sensitive data, and to zero them before
  370. unlocking them.
  371. - High-level wrappers for crypto_box and crypto_secretbox
  372. (crypto_box_easy and crypto_secretbox_easy) can be used to avoid
  373. dealing with the specific memory layout regular functions depend on.
  374. - crypto_pwhash_scryptsalsa208sha256* functions have been added
  375. to derive a key from a password, and for password storage.
  376. - Salsa20 and ed25519 implementations now support overlapping
  377. inputs/keys/outputs (changes imported from supercop-20140505).
  378. - New build scripts for Visual Studio, Emscripten, different Android
  379. architectures and msys2 are available.
  380. - The poly1305-53 implementation has been replaced with Floodyberry's
  381. poly1305-donna32 and poly1305-donna64 implementations.
  382. - sodium_hex2bin() has been added to complement sodium_bin2hex().
  383. - On OpenBSD and Bitrig, arc4random() is used instead of reading
  384. /dev/urandom.
  385. - crypto_auth_hmac_sha512() has been implemented.
  386. - sha256 and sha512 now have a streaming interface.
  387. - hmacsha256, hmacsha512 and hmacsha512256 now support keys of
  388. arbitrary length, and have a streaming interface.
  389. - crypto_verify_64() has been implemented.
  390. - first-class Visual Studio build system, thanks to @evoskuil
  391. - CPU features are now detected at runtime.
  392. * Version 0.4.5
  393. - Restore compatibility with OSX <= 10.6
  394. * Version 0.4.4
  395. - Visual Studio is officially supported (VC 2010 & VC 2013)
  396. - mingw64 is now supported
  397. - big-endian architectures are now supported as well
  398. - The donna_c64 implementation of curve25519_donna_c64 now handles
  399. non-canonical points like the ref implementation
  400. - Missing scalarmult_curve25519 and stream_salsa20 constants are now exported
  401. - A crypto_onetimeauth_poly1305_ref() wrapper has been added
  402. * Version 0.4.3
  403. - crypto_sign_seedbytes() and crypto_sign_SEEDBYTES were added.
  404. - crypto_onetimeauth_poly1305_implementation_name() was added.
  405. - poly1305-ref has been replaced by a faster implementation,
  406. Floodyberry's poly1305-donna-unrolled.
  407. - Stackmarkings have been added to assembly code, for Hardened Gentoo.
  408. - pkg-config can now be used in order to retrieve compilations flags for
  409. using libsodium.
  410. - crypto_stream_aes256estream_*() can now deal with unaligned input
  411. on platforms that require word alignment.
  412. - portability improvements.
  413. * Version 0.4.2
  414. - All NaCl constants are now also exposed as functions.
  415. - The Android and iOS cross-compilation script have been improved.
  416. - libsodium can now be cross-compiled to Windows from Linux.
  417. - libsodium can now be compiled with emscripten.
  418. - New convenience function (prototyped in utils.h): sodium_bin2hex().
  419. * Version 0.4.1
  420. - sodium_version_*() functions were not exported in version 0.4. They
  421. are now visible as intended.
  422. - sodium_init() now calls randombytes_stir().
  423. - optimized assembly version of salsa20 is now used on amd64.
  424. - further cleanups and enhanced compatibility with non-C99 compilers.
  425. * Version 0.4
  426. - Most constants and operations are now available as actual functions
  427. instead of macros, making it easier to use from other languages.
  428. - New operation: crypto_generichash, featuring a variable key size, a
  429. variable output size, and a streaming API. Currently implemented using
  430. Blake2b.
  431. - The package can be compiled in a separate directory.
  432. - aes128ctr functions are exported.
  433. - Optimized versions of curve25519 (curve25519_donna_c64), poly1305
  434. (poly1305_53) and ed25519 (ed25519_ref10) are available. Optionally calling
  435. sodium_init() once before using the library makes it pick the fastest
  436. implementation.
  437. - New convenience function: sodium_memzero() in order to securely
  438. wipe a memory area.
  439. - A whole bunch of cleanups and portability enhancements.
  440. - On Windows, a .REF file is generated along with the shared library,
  441. for use with Visual Studio. The installation path for these has become
  442. $prefix/bin as expected by MingW.
  443. * Version 0.3
  444. - The crypto_shorthash operation has been added, implemented using
  445. SipHash-2-4.
  446. * Version 0.2
  447. - crypto_sign_seed_keypair() has been added
  448. * Version 0.1
  449. - Initial release.