How should I handle configuration and secrets in Rust?
Configuration must be available to the application without exposing credentials in source control, logs or browser code. What belongs in the runtime and which access controls matter?
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Configuration must be available to the application without exposing credentials in source control, logs or browser code. What belongs in the runtime and which access controls matter?
Context The rustls crate currently ships with the webpki-roots bundle as its default root certificate store. This provides cross-platform consistency but omits locally installed or corporate CAs unless the application explicitly loads them via rustls-native-certs or platform-specific APIs. Unresolved decision An open issue in the rustls repository debates wh