I have been working on packaging the "aws-lc-rs" and / "aws-lc-sys" Rust crates, which are safe Rust bindings for aws-lc and generated Rust bindings for the included aws-lc library, respectively.
TL;DR: The motivation is to replace the "rust-ring" package, which has been problematic for a long time, with rust-aws-lc. The "ring" crate is maintained by a single person, whereas AWS-LC and its Rust bindings are officially supported by Amazon / AWS. I agree that none of these two are ideal, and using something based on an existing crypto library would be preferable, but these two are the only available choices - and aws-lc seems to be the objectively less bad choice.
In accordance with the Crypto Policies guidelines, I have sent an email to the "crypto team" (crypto-team mailing list).
This was two weeks ago, and there is no indication that my message has ever been received. The list has zero messages in its public archives ever, and my email to the list is stuck in moderation - because my subscription request is stuck in moderation.
At this point, I don't know how to proceed. Consulting the Crypto Team is a MUST requirement according to the policy. But am I stuck with the current (bad) situation since they (who's "they"? I don't even know) don't react at all and don't even acknowledge that I sent an email to the mailing list?
For reference, I sent that email to both the "crypto-team" and the "rust" mailing lists, so at least there's a public copy in the archives: https://lists.fedoraproject.org/archives/list/rust@lists.fedoraproject.org/thread/FQGWNIFKIUEMWIIOE5H3TXAWRF4LK5ZX/
@kevin As an admin, would you be able to tell who is supposed to handle the "crypto-team" list?
The "owners" of that list are "Simo Sorce" and "Tomas Mraz"
thanks, CC @simo @tmraz then
Sorry but the list says there were no messages this month and I have not seen anything as well, sounds like a mail issue occurred when you sent?
And sure enough I now see it is on hold, but as admin I never got any notifications about the several message on hold there :/
Okay, it looks like communication is happening so I'll close this issue and you can open more if/when needed.
Metadata Update from @james: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)