Closed Diggsey closed 2 months ago
I believe this problem will be resolved for Windows once we have a release for PR #486
I've been using the following basic setup to successfully test on MacOS, Linux, and now Windows (using that PR branch):
[package]
name = "aws-lc-rs-test"
version = "0.1.0"
edition = "2021"
[dependencies]
aws-lc-rs = "1.8.1"
boring = "4.9.1"
fn main() {
const MESSAGE: &[u8] = b"Hello Technician!";
let output = aws_lc_rs::digest::digest(&aws_lc_rs::digest::SHA256, MESSAGE);
print!("\nAWS-LC: ");
for v in output.as_ref() {
print!("{:02x}", *v);
}
print!("\nBoringSSL: ");
let digest = boring::hash::MessageDigest::sha256();
let boring_output = boring::hash::hash(digest, MESSAGE).unwrap();
for v in boring_output.as_ref() {
print!("{:02x}", *v);
}
println!();
}
I'll follow up once we've merged the relevant PRs.
This is resolved with the release of aws-lc-rs v1.9.0.
Problem:
The
libaws_lc_sys
crate exports symbols which conflict with other crates, such aslibboring_sys
.Relevant details
AWS-LC for Rust versions or commit: (6b1bce0...)
System information: for linux, below info can be collected by running
uname -srvmp
Build log: