Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

panicked ring-0.16.11/src/rsa/signing.rs:422:13 #1295

Closed
silence-coding opened this issue May 14, 2021 · 5 comments
Closed

panicked ring-0.16.11/src/rsa/signing.rs:422:13 #1295

silence-coding opened this issue May 14, 2021 · 5 comments

Comments

@silence-coding
Copy link

silence-coding commented May 14, 2021

Platform
Linux OMP-01 4.18.0-147.5.1.6.h451.eulerosv2r9.x86_64 #1 SMP Thu Apr 22 04:55:25 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Panic

thread 'tokio-runtime-worker' panicked at 'called `Result::unwrap()` on an `Err` value: Unspecified', ring-0.16.11/src/rsa/signing.rs:422:13


13: core::panicking::panic_fmt
             at src/libcore/panicking.rs:101
  14: core::option::expect_none_failed
             at src/libcore/option.rs:1272
  15: ring::rsa::signing::RsaKeyPair::public_modulus_len
  16: <rustls::sign::RSASigner as rustls::sign::Signer>::sign
  17: <rustls::client::tls13::ExpectFinished as rustls::client::hs::State>::handle
  18: rustls::client::ClientSessionImpl::process_main_protocol
  19: <rustls::client::ClientSession as rustls::session::Session>::process_new_packets
  20: tokio_rustls::common::Stream<IO,S>::process_new_packets
  21: tokio_rustls::common::Stream<IO,S>::handshake
  22: <tokio_rustls::common::handshake::MidHandshake<IS> as core::future::future::Future>::poll
  23: <hbx::net::tls::TlsConnect as core::future::future::Future>::poll
  24: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
  25: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
  26: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
  27: <hyper::service::oneshot::Oneshot<S,Req> as core::future::future::Future>::poll
  28: futures_util::future::try_future::try_chain::TryChain<Fut1,Fut2,Data>::poll
  29: <hyper::common::lazy::Lazy<F,R> as core::future::future::Future>::poll
  30: futures_util::future::future::chain::Chain<Fut1,Fut2,Data>::poll
  31: futures_util::future::try_future::try_chain::TryChain<Fut1,Fut2,Data>::poll
  32: <futures_util::future::poll_fn::PollFn<F> as core::future::future::Future>::poll
  33: <hyper::client::ResponseFuture as core::future::future::Future>::poll
  34: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
  35: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
  36: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
  37: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll

Code
image

@briansmith
Copy link
Owner

@silence-coding Does it happen with 0.16.20?

@briansmith
Copy link
Owner

@silence-coding Can you share the RSA public key it happens with?

@briansmith
Copy link
Owner

@silence-coding Also, which version of Rust are you using? 1.53 nightly or 1.52 or older stable releases?

@silence-coding
Copy link
Author

silence-coding commented May 18, 2021

I'm sorry, I didn't reserve the environment. I tried to reproduce the problem in the environment, but it didn't recur. ssl configurations in the environment are not changed when the problem is reproduced.

Rust : 1.51
rustls:0.17
ring: 0.16.11 (PRIVATE_KEY_PUBLIC_MODULUS_MAX_BITS was changed from 4096 to 8192.)

@briansmith
Copy link
Owner

You were probably using a pre-Stable Rust release that had a bug: rust-lang/rust#84958. I'm closing this since you can't reproduce it. Thanks for the bug report!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants