security: remover credencial MySQL exposta do tracking do git - #50
Open
brunosilvaJava wants to merge 1 commit into
Open
security: remover credencial MySQL exposta do tracking do git#50brunosilvaJava wants to merge 1 commit into
brunosilvaJava wants to merge 1 commit into
Conversation
- Remove .kiro/settings/mcp.json (contained plaintext DB password) from git tracking and add it to .gitignore. - Add .kiro/settings/mcp.json.example as a template with placeholder values, so the local MCP config structure is still documented. Note: the credential was already exposed in git history on a public repo. This commit stops further exposure going forward, but does not remove it from past commits. The password must be rotated, and a history rewrite (git filter-repo/BFG) is recommended as a follow-up. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Contexto
Durante análise de arquitetura, identifiquei que
.kiro/settings/mcp.jsonestava commitado emmastercom usuário e senha de MySQL em texto puro (config de um MCP server). O repositório é público, logo a credencial ficou exposta publicamente.Mudanças
.kiro/settings/mcp.jsondo tracking (mantido localmente, ignorado pelo git)..kiro/settings/mcp.jsonao.gitignore..kiro/settings/mcp.json.examplecom placeholders, documentando a estrutura sem expor segredo real.Issue relacionada: #49