Skip to content

RsaPublicKey::new_with_max_size behaves differently #528

Closed
@zacknewman

Description

@zacknewman

On rsa 0.9.8, RsaPublicKey::new_with_max_size treated the passed max_size as the actual maximum number of bits the modulus is allowed to have; however rsa 0.10.0-rc.0 expects that same parameter to actually be the maximum number of "bits precision" the modulus is allowed to have.

It would be nice if the documentation were at least amended to make this clear.

rsa 0.9.8:

use rsa::{BigUint, RsaPublicKey};
fn main() {
    let n = BigUint::from_bytes_be([1, 116, 2, 177, 35, 163, 109, 146, 185].as_slice());
    assert!(RsaPublicKey::new_with_max_size(n, 3u32.into(), 65).is_ok());
}

rsa 0.10.0-rc.0:

use rsa::{BoxedUint, RsaPublicKey};
fn main() {
    let n =
        BoxedUint::from_be_slice([1, 116, 2, 177, 35, 163, 109, 146, 185].as_slice(), 65).unwrap();
    // Despite `n` being 65 bits, `max_size` is considered to be too small.
    assert!(RsaPublicKey::new_with_max_size(n.clone(), 3u32.into(), 65).is_err());
    // `128` is the smallest `max_size` that doesn't cause an error which happens to also be
    // the value of `n.bits_precision()`.
    assert!(RsaPublicKey::new_with_max_size(n, 3u32.into(), 128).is_ok());
}
[zack@laptop ~]$ rustc --version
rustc 1.87.0 (17067e9ac 2025-05-09)
[zack@laptop ~]$ uname -a
Linux laptop 6.15.1-arch1-2 #1 SMP PREEMPT_DYNAMIC Sat, 07 Jun 2025 14:36:24 +0000 x86_64 GNU/Linux

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions