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