Security Fix: Replace hardcoded secrets with placeholders in .env.exa… #393
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…mple Resolved security vulnerability where .env.example contained hardcoded secrets and real credentials. Changes: - Replaced POSTGRES_PASSWORD with secure placeholder - Changed ADMIN_PASSWORD from weak 'admin123' to placeholder - Replaced all OAuth secrets and tokens with placeholders - Updated JWT secrets, encryption keys, and notebook tokens - Changed SHARED_SECRET_KEY to placeholder - Updated BASE_DIR path to generic example - Changed ADMIN_EMAIL to example.com domain This prevents accidental deployment with insecure default credentials and exposure of sensitive authentication tokens. Signed-off-by: MasterAsnackin <39118622+MasteraSnackin@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…mple
Resolved security vulnerability where .env.example contained hardcoded secrets and real credentials.
Changes:
This prevents accidental deployment with insecure default credentials and exposure of sensitive authentication tokens. tokens.