Inquiry About Compiling Rust Programs Without Certificate Warnings #127
Description
Hello,
As a Rust beginner, I'm excited to explore the capabilities of this powerful programming language. I recently downloaded the aarch64-apple-darwin-simple-http-server executable from the releases section of this repository and noticed that it runs without any certificate warning or risk prompt on my macOS system.
Upon inspecting the executable with the codesign -dvvv aarch64-apple-darwin-simple-http-server command, I found out that it is signed with a self-signed certificate. This got me curious about how Rust programs can be compiled and signed in such a way that they do not trigger security warnings, especially during development.
Could you please share some insights or guidance on how to compile Rust programs without encountering certificate warnings? As a newcomer to the language, I'm particularly interested in understanding the best practices and tools available for ensuring that my Rust applications can be distributed and run safely without causing concern for end-users regarding security risks.
Thank you for your time and assistance. I look forward to learning more about Rust and contributing to the community.