Up to [cvs.NetBSD.org] / pkgsrc / security / libsodium
Request diff between arbitrary revisions
Keyword substitution: kv
Default branch: MAIN
libsodium: updated to 1.0.22 1.0.22 This point release includes all the changes from 1.0.21-stable, plus: - Post-quantum key encapsulation is now available. ML-KEM768, the NIST-standardized lattice-based KEM, is accessible through the `crypto_kem_mlkem768_*()` functions. - X-Wing, a hybrid KEM combining ML-KEM768 with X25519 for protection against both classical and quantum adversaries, is available through the `crypto_kem_*()` functions. X-Wing is the recommended KEM for most applications. - SHA-3 hash functions are now available as `crypto_hash_sha3256_*()` and `crypto_hash_sha3512_*()`, with both one-shot and streaming APIs.
libsodium: updated to 1.0.21 * Version 1.0.21-stable - Export missing crypto_ipcrypt_nd_keygen() helper function. - Fixed compilation with GCC on aarch64. * Version 1.0.21 This point release includes all the changes from 1.0.20-stable, which include a security fix for the `crypto_core_ed25519_is_valid_point()` function, as well as two new sets of functions: - The new `crypto_ipcrypt_*` functions implement mechanisms for securely encrypting and anonymizing IP addresses as specified in https://ipcrypt-std.github.io - The `sodium_bin2ip` and `sodium_ip2bin` helper functions have been added to complement the `crypto_ipcrypt_*` functions and easily convert addresses between bytes and strings. - XOF: the `crypto_xof_shake*` and `crypto_xof_turboshake*` functions are standard extendable output functions. From input of any length, they can derive output of any length with the same properties as hash functions. These primitives are required by many post-quantum mechanisms, but can also be used for a wide range of applications, including key derivation, session encryption and more.
libsodium: updated to 1.0.19 Version 1.0.19 This release includes all the changes from 1.0.18-stable, as well as two additions: - New AEADs: AEGIS-128L and AEGIS-256 are now available in the `crypto_aead_aegis128l_*()` and `crypto_aead_aegis256_*()` namespaces. AEGIS is a family of authenticated ciphers for high-performance applications, leveraging hardware AES acceleration on `x86_64` and `aarch64`. In addition to performance, AEGIS ciphers have unique properties making them easier and safer to use than AES-GCM. They can also be used as high-performance MACs. - The HKDF key derivation mechanism, required by many standard protocols, is now available in the `crypto_kdf_hkdf_*()` namespace. It is implemented for the SHA-256 and SHA-512 hash functions. - The `osx.sh` build script was renamed to `macos.sh`. - Support for android-mips was removed.
libsodium: updated to 1.0.18 Version 1.0.18 - The Enterprise versions of Visual Studio are now supported. - Visual Studio 2019 is now supported. - 32-bit binaries for Visual Studio 2010 are now provided. - A test that didn't work properly on Linux systems with overcommit memory turned on has been removed. This fixes Ansible builds. - Emscripten: print and printErr functions are overridden to send errors to the console, if there is one. - Emscripten: UTF8ToString() is now exported since Pointer_stringify() has been deprecated. - Libsodium version detection has been fixed in the CMake recipe. - Generic hashing got a 10% speedup on AVX2. - New target: WebAssembly/WASI (compile with dist-builds/wasm32-wasi.sh). - New functions to map a hash to an edwards25519 point or get a random point: core_ed25519_from_hash() and core_ed25519_random(). - crypto_core_ed25519_scalar_mul() has been implemented for scalar*scalar (mod L) multiplication. - Support for the Ristretto group has been implemented, for compatibility with wasm-crypto. - Improvements have been made to the test suite. - Portability improvements has been made. - getentropy() is now used on systems providing this system call. - randombytes_salsa20 has been renamed to randombytes_internal. - Support for (p)nacl has been removed. - Most ((nonnull)) attributes have been relaxed to allow 0-length inputs to be NULL. - The -ftree-vectorize and -ftree-slp-vectorize compiler switches are now used, if available, for optimized builds.
libsodium: updated to 1.0.16 Version 1.0.16 - Signatures computations and verifications are now way faster on 64-bit platforms with compilers supporting 128-bit arithmetic (gcc, clang, icc). This includes the WebAssembly target. - New low-level APIs for computations over edwards25519: `crypto_scalarmult_ed25519()`, `crypto_scalarmult_ed25519_base()`, `crypto_core_ed25519_is_valid_point()`, `crypto_core_ed25519_add()`, `crypto_core_ed25519_sub()` and `crypto_core_ed25519_from_uniform()` (elligator representative to point). - `crypto_sign_open()`, `crypto_sign_verify_detached() and `crypto_sign_edwards25519sha512batch_open` now reject public keys in non-canonical form in addition to low-order points. - The library can be built with `ED25519_NONDETERMINISTIC` defined in order to use synthetic nonces for EdDSA. This is disabled by default. - Webassembly: `crypto_pwhash_*()` functions are now included in non-sumo builds. - `sodium_stackzero()` was added to wipe content off the stack. - Android: support new SDKs where unified headers have become the default. - The Salsa20-based PRNG example is now thread-safe on platforms with support for thread-local storage, optionally mixes bits from RDRAND. - CMAKE: static library detection on Unix systems has been improved - Argon2 and scrypt are slightly faster on Linux.
libsodium: update to 1.0.15 Version 1.0.15 - The default password hashing algorithm is now Argon2id. The `pwhash_str_verify()` function can still verify Argon2i hashes without any changes, and `pwhash()` can still compute Argon2i hashes as well. - The aes128ctr primitive was removed. It was slow, non-standard, not authenticated, and didn't seem to be used by any opensource project. - Argon2id required at least 3 passes like Argon2i, despite a minimum of `1` as defined by the `OPSLIMIT_MIN` constant. This has been fixed. - The secretstream construction was slightly changed to be consistent with forthcoming variants. - The Javascript and Webassembly versions have been merged, and the module now returns a `.ready` promise that will resolve after the Webassembly code is loaded and compiled. - Note that due to these incompatible changes, the library version major was bumped up.
Version 1.0.13 - Javascript: the sumo builds now include all symbols. They were previously limited to symbols defined in minimal builds. - The public `crypto_pwhash_argon2i_MEMLIMIT_MAX` constant was incorrectly defined on 32-bit platforms. This has been fixed. - Version 1.0.12 didn't compile on OpenBSD/i386 using the base gcc compiler. This has been fixed. - The Android compilation scripts have been updated for NDK r14b. - armv7s-optimized code was re-added to iOS builds. - An AVX2 optimized implementation of the Argon2 round function was added. - The Argon2id variant of Argon2 has been implemented. The high-level `crypto_pwhash_str_verify()` function automatically detects the algorithm and can verify both Argon2i and Argon2id hashed passwords. The default algorithm for newly hashed passwords remains Argon2i in this version to avoid breaking compatibility with verifiers running libsodium <= 1.0.12. - A `crypto_box_curve25519xchacha20poly1305_seal*()` function set was implemented. - scrypt was removed from minimal builds. - libsodium is now available on Nuget.
Update libsodium to 1.0.6.
Provided by csosstudy in PR 50455.
Version 1.0.6
Optimized implementations of Blake2 have been added for modern Intel platforms. crypto_generichash() is now faster than MD5 and SHA1 implementations while being far more secure.
Functions for which the return value should be checked have been tagged with __attribute__ ((warn_unused_result)). This will intentionally break code compiled with -Werror that didn't bother checking critical return values.
The crypto_sign_edwards25519sha512batch_*() functions have been tagged as deprecated.
Undocumented symbols that were exported, but were only useful for internal purposes have been removed or made private: sodium_runtime_get_cpu_features(), the implementation-specific crypto_onetimeauth_poly1305_donna() symbols, crypto_onetimeauth_poly1305_set_implementation(), crypto_onetimeauth_poly1305_implementation_name() and crypto_onetimeauth_pick_best_implementation().
sodium_compare() now works as documented, and compares numbers in little-endian format instead of behaving like memcmp().
The previous changes should not break actual applications, but to be safe, the library version major was incremented.
sodium_runtime_has_ssse3() and sodium_runtime_has_sse41() have been added.
The library can now be compiled with the CompCert compiler.
Version 1.0.5
This release only fixes compilation issues on some platforms.
If 1.0.4 compiled and installed fine on your system, upgrading to this version is not required.
There are no functional changes.
Compilation issues on some platforms were fixed: missing alignment directives were added (required at least on RHEL-6/i386), a workaround for a VRP bug on gcc/armv7 was added, and the library can now be compiled with the SunPro compiler.
Javascript target: io.js is not supported any more. Use nodejs.
Version 1.0.4
Support for AES256-GCM has been added. This requires a CPU with the aesni and pclmul extensions, and is accessible via the crypto_aead_aes256gcm_*() functions.
The Javascript target doesn't use eval() any more, so that the library can be used in Chrome packaged applications.
QNX and CloudABI are now supported.
Support for NaCl has finally been added.
ChaCha20 with an extended (96 bit) nonce and a 32-bit counter has been implemented as crypto_stream_chacha20_ietf(), crypto_stream_chacha20_ietf_xor() and crypto_stream_chacha20_ietf_xor_ic(). An IETF-compatible version of ChaCha20Poly1305 is available as crypto_aead_chacha20poly1305_ietf_npubbytes(), crypto_aead_chacha20poly1305_ietf_encrypt() and crypto_aead_chacha20poly1305_ietf_decrypt().
The sodium_increment() helper function has been added, to increment an arbitrary large number (such as a nonce).
The sodium_compare() helper function has been added, to compare arbitrary large numbers (such as nonces, in order to prevent replay attacks).
Version 1.0.3
In addition to sodium_bin2hex(), sodium_hex2bin() is now a constant-time function.
crypto_stream_xsalsa20_ic() has been added.
crypto_generichash_statebytes(), crypto_auth_*_statebytes() and crypto_hash_*_statebytes() have been added in order to retrieve the size of structures keeping states from foreign languages.
The JavaScript target doesn't require /dev/urandom or an external randombytes() implementation any more. Other minor Emscripten-related improvements have been made in order to support libsodium.js
Custom randombytes implementations do not need to provide their own implementation of randombytes_uniform() any more. randombytes_stir() and randombytes_close() can also be NULL pointers if they are not required.
On Linux, getrandom(2) is being used instead of directly accessing /dev/urandom, if the kernel supports this system call.
crypto_box_seal() and crypto_box_seal_open() have been added.
A solutions for Visual Studio 2015 was added.
Update to 1.0.0, from maintainer csosstudy in PR 49251. While here, add rpath to pkgconfig file. * Version 1.0.0 - The API and ABI are now stable. New features will be added, but backward-compatibility is guaranteed through all the 1.x.y releases. - crypto_sign() properly works with overlapping regions again. Thanks to @pysiak for reporting this regression introduced in version 0.6.1. - The test suite has been extended. * Version 0.7.1 (1.0 RC2) - This is the second release candidate of Sodium 1.0. Minor compilation, readability and portability changes have been made and the test suite was improved, but the API is the same as the previous release candidate. * Version 0.7.0 (1.0 RC1) - Allocating memory to store sensitive data can now be done using sodium_malloc() and sodium_allocarray(). These functions add guard pages around the protected data to make it less likely to be accessible in a heartbleed-like scenario. In addition, the protection for memory regions allocated that way can be changed using sodium_mprotect_noaccess(), sodium_mprotect_readonly() and sodium_mprotect_readwrite(). - ed25519 keys can be converted to curve25519 keys with crypto_sign_ed25519_pk_to_curve25519() and crypto_sign_ed25519_sk_to_curve25519(). This allows using the same keys for signature and encryption. - The seed and the public key can be extracted from an ed25519 key using crypto_sign_ed25519_sk_to_seed() and crypto_sign_ed25519_sk_to_pk(). - aes256 was removed. A timing-attack resistant implementation might be added later, but not before version 1.0 is tagged. - The crypto_pwhash_scryptxsalsa208sha256_* compatibility layer was removed. Use crypto_pwhash_scryptsalsa208sha256_*. - The compatibility layer for implementation-specific functions was removed. - Compilation issues with Mingw64 on MSYS (not MSYS2) were fixed. - crypto_pwhash_scryptsalsa208sha256_STRPREFIX was added: it contains the prefix produced by crypto_pwhash_scryptsalsa208sha256_str() * Version 0.6.1 - Important bug fix: when crypto_sign_open() was given a signed message too short to even contain a signature, it was putting an unlimited amount of zeros into the target buffer instead of immediately returning -1. The bug was introduced in version 0.5.0. - New API: crypto_sign_detached() and crypto_sign_verify_detached() to produce and verify ed25519 signatures without having to duplicate the message. - New ./configure switch: --enable-minimal, to create a smaller library, with only the functions required for the high-level API. Mainly useful for the JavaScript target and embedded systems. - All the symbols are now exported by the Emscripten build script. - The pkg-config .pc file is now always installed even if the pkg-config tool is not available during the installation. * Version 0.6.0 - The ChaCha20 stream cipher has been added, as crypto_stream_chacha20_* - The ChaCha20Poly1305 AEAD construction has been implemented, as crypto_aead_chacha20poly1305_* - The _easy API does not require any heap allocations any more and does not have any overhead over the NaCl API. With the password hashing function being an obvious exception, the library doesn't allocate and will not allocate heap memory ever. - crypto_box and crypto_secretbox have a new _detached API to store the authentication tag and the encrypted message separately. - crypto_pwhash_scryptxsalsa208sha256*() functions have been renamed crypto_pwhash_scryptsalsa208sha256*(). - The low-level crypto_pwhash_scryptsalsa208sha256_ll() function allows setting individual parameters of the scrypt function. - New macros and functions for recommended crypto_pwhash_* parameters have been added. - Similarly to crypto_sign_seed_keypair(), crypto_box_seed_keypair() has been introduced to deterministically generate a key pair from a seed. - crypto_onetimeauth() now provides a streaming interface. - crypto_stream_chacha20_xor_ic() and crypto_stream_salsa20_xor_ic() have been added to use a non-zero initial block counter. - On Windows, CryptGenRandom() was replaced by RtlGenRandom(), which doesn't require the Crypt API. - The high bit in curve25519 is masked instead of processing the key as a 256-bit value. - The curve25519 ref implementation was replaced by the latest ref10 implementation from Supercop. - sodium_mlock() now prevents memory from being included in coredumps on Linux 3.4+ * Version 0.5.0 - sodium_mlock()/sodium_munlock() have been introduced to lock pages in memory before storing sensitive data, and to zero them before unlocking them. - High-level wrappers for crypto_box and crypto_secretbox (crypto_box_easy and crypto_secretbox_easy) can be used to avoid dealing with the specific memory layout regular functions depend on. - crypto_pwhash_scryptsalsa208sha256* functions have been added to derive a key from a password, and for password storage. - Salsa20 and ed25519 implementations now support overlapping inputs/keys/outputs (changes imported from supercop-20140505). - New build scripts for Visual Studio, Emscripten, different Android architectures and msys2 are available. - The poly1305-53 implementation has been replaced with Floodyberry's poly1305-donna32 and poly1305-donna64 implementations. - sodium_hex2bin() has been added to complement sodium_bin2hex(). - On OpenBSD and Bitrig, arc4random() is used instead of reading /dev/urandom. - crypto_auth_hmac_sha512() has been implemented. - sha256 and sha512 now have a streaming interface. - hmacsha256, hmacsha512 and hmacsha512256 now support keys of arbitrary length, and have a streaming interface. - crypto_verify_64() has been implemented. - first-class Visual Studio build system, thanks to @evoskuil - CPU features are now detected at runtime.
Update libsodium to 0.4.3, per maintainer update request by PR pkg/48260. * Version 0.4.3 - crypto_sign_seedbytes() and crypto_sign_SEEDBYTES were added. - crypto_onetimeauth_poly1305_implementation_name() was added. - poly1305-ref has been replaced by a faster implementation, Floodyberry's poly1305-donna-unrolled. - Stackmarkings have been added to assembly code, for Hardened Gentoo. - pkg-config can now be used in order to retrieve compilations flags for using libsodium. - crypto_stream_aes256estream_*() can now deal with unaligned input on platforms that require word alignment. - portability improvements.
Update to 0.4.2, provided by csosstudy in PR 48046. * Version 0.4.2 - All NaCl constants are now also exposed as functions. - The Android and iOS cross-compilation script have been improved. - libsodium can now be cross-compiled to Windows from Linux. - libsodium can now be compiled with emscripten. - New convenience function (prototyped in utils.h): sodium_bin2hex().
Update security/libsodium from version 0.3 to 0.4.1 Provided in pkg PR/47767 by csosstudy Changes from previous version: * Version 0.4.1 - sodium_version_*() functions were not exported in version 0.4. They are now visible as intended. - sodium_init() now calls randombytes_stir(). - optimized assembly version of salsa20 is now used on amd64. - further cleanups and enhanced compatibility with non-C99 compilers. * Version 0.4 - Most constants and operations are now available as actual functions instead of macros, making it easier to use from other languages. - New operation: crypto_generichash, featuring a variable key size, a variable output size, and a streaming API. Currently implemented using Blake2b. - The package can be compiled in a separate directory. - aes128ctr functions are exported. - Optimized versions of curve25519 (curve25519_donna_c64), poly1305 (poly1305_53) and ed25519 (ed25519_ref10) are available. Optionally calling sodium_init() once before using the library makes it pick the fastest implementation. - New convenience function: sodium_memzero() in order to securely wipe a memory area. - A whole bunch of cleanups and portability enhancements. - On Windows, a .REF file is generated along with the shared library, for use with Visual Studio. The installation path for these has become $prefix/bin as expected by MingW. pkgsrc change: * install the NEWS file under share/ hierarchy
Import libsodium-0.3 into the Packages Collection. Provided by csosstudy E. in PR 47600. NaCl (pronounced "salt") is a new easy-to-use high-speed software library for network communication, encryption, decryption, signatures, etc. NaCl's goal is to provide all of the core operations needed to build higher-level cryptographic tools. libsodium is a library for network communication, encryption, decryption, signatures, etc. libsodium is a portable, cross-compilable, installable, packageable, API-compatible version for NaCl. One minor change was to take the "check" target out of the post-build state and put it into the TEST_TARGET definition.
Initial revision