RA Crashes with aes-gcm crate. #13506
Labels
A-ty
type system / type inference / traits / method resolution
Broken Window
Bugs / technical debt to be addressed immediately
S-unactionable
Issue requires feedback, design decisions or is blocked on other work
Comments
|
Probably a dupe of #13006 |
lnicola
added
A-ty
|
@dtzxporter can you please update your code example with a proper reproduction? I tried the following: [package]
name = "hello"
version = "0.1.0"
edition = "2021"
[dependencies]
aes-gcm = "0.10.1"
bincode = "2.0.0-rc.2"
rand = "0.8.5"use aes_gcm::aead::Aead;
use aes_gcm::Aes256Gcm;
use aes_gcm::KeyInit;
use aes_gcm::Nonce;
use bincode::config::Config;
use bincode::enc;
use bincode::error::EncodeError;
use bincode::Decode;
use bincode::Encode;
use rand::rngs::OsRng;
use rand::RngCore;
struct EncryptedData(([u8; 32], Vec<u8>));
/// Encrypt and encode the given value into a `Vec<u8>` with the key and given `Config`.
pub fn encode_to_vec<E: enc::Encode, C: Config>(
val: E,
key: &[u8],
config: C,
) -> Result<Vec<u8>, EncodeError> {
let cipher = Aes256Gcm::new_from_slice(key).unwrap();
let nonce_bytes = [0; 32];
let nonce = Nonce::from_slice(&nonce_bytes);
let bincode_data = bincode::encode_to_vec(val, config)?;
let ciphertext = cipher.encrypt(nonce, bincode_data.as_ref()).unwrap();
Ok(bincode::encode_to_vec(
EncryptedData((nonce_bytes, ciphertext)),
config,
)?)
}
impl Encode for EncryptedData {
fn encode<E: enc::Encoder>(&self, encoder: &mut E) -> Result<(), EncodeError> {
todo!()
}
}
fn main() {}I don't get a crash in Code, nor in |
lnicola
added
the
S-unactionable
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
rust-analyzer version: (eg. output of "rust-analyzer: Show RA Version" command, accessible in VSCode via Ctrl/⌘+Shift+P)
0.3.1258-standalone (43fb956 2022-10-23)
rustc version: (eg. output of
rustc -V)rustc 1.64.0 (a55dd71d5 2022-09-19)
relevant settings: (eg. client settings, or environment variables like
CARGO,RUSTUP_HOMEorCARGO_HOME)Hi All, I had reported a similar crash with tonic (#7817). Which seemed to be infinite recursion.
It looks like this can be triggered with the aes-gcm crate as well.
It's enough to trigger using:
Callstack (Seems same issue as before, infinite recursion):
The text was updated successfully, but these errors were encountered: