Brian Smith
Brian Smith
Currently Cargo.toml has: ``` [dependencies] quote = "0.3.15" syn = "0.11.11" synstructure = "0.6.0" ``` Other libraries my project depends on require: * quote 0.4.2 * syn 0.12.10 It would...
We can probably add support for the secp256k1 curve pretty easily mostly by copy/pasting the P-384 code and changing the constants (number of limbs: 4, new `q` and `n` values)....
Add CCM AEAD
crypto/cmac is being removed because it depends on the non-AEAD cipher.h encryption interface, which is being removed. In order to implement the CCM AEAD, we need a new CTR +...
The most common cross-compilation target seems to be wasm32-unknown-unknown and wasm32-wasi. Users have found needing to install a LLVM/clang toolchain that can target wasm32 to be too much of a...
I've no intention of doing any PowerPC-specific work, but we did merge in some PowerPC code from BoringSSL. Besides testing, we should minimize `aesp8-ppc.pl` the same we did for other...
The vast majority of the time we are not building for a `no_std` environment when targeting x86, x86-64, ARM, or AAarch64. If we're not targeting a no_std environment then we...
Issue #1478 proposes adding support for larger keys. Currently we limit the maximum peer public key size we accept when verifying a signature to 8192 bits. Whatever we end up...
Currently, *ring* limits the size of the public modulus of RSA private key operations to 4096 bits. This is in line with NIST/FIPS guidance that suggested (at the time, at...
Provide a way for users of RSA private keys to opt into support for keys with public modulus less than 2048 bits and at least 1024 bits. ring already has...
Currently we have `RSA_PKCS1_1024_8192_SHA1_FOR_LEGACY_USE_ONLY` for *verifying* signatures that use SHA-1 (and weak keys). However, we don't expose the ability to *produce* such signatures. Some *ring* users need to support existing...