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