-
-
Notifications
You must be signed in to change notification settings - Fork 327
fix: 替换配置文件中的硬编码凭据为占位符 #438
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
saaa99999999
wants to merge
1
commit into
opsre:main
Choose a base branch
from
saaa99999999:fix/hardcoded-credentials
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
热更新路径会丢失
JWT_KEY覆盖值当前
JWT_KEY只在初始化阶段应用一次;viper.OnConfigChange触发后会重新Unmarshal配置并覆盖Conf.Jwt.Key,导致环境变量覆盖失效。建议把“环境变量覆盖”提取为统一函数,并在初始化与热更新回调中都调用一次。建议修复(示例)
func InitConfig() { @@ viper.OnConfigChange(func(e fsnotify.Event) { if err := viper.Unmarshal(Conf); err != nil { panic(fmt.Errorf("初始化配置文件失败:%s", err)) } normalizeConfig() + applyEnvOverrides() Conf.System.RSAPublicBytes = pub Conf.System.RSAPrivateBytes = priv }) @@ if err := viper.Unmarshal(Conf); err != nil { panic(fmt.Errorf("初始化配置文件失败:%s", err)) } normalizeConfig() + applyEnvOverrides() @@ - // 部分配合通过环境变量加载 - dbDriver := os.Getenv("DB_DRIVER") - ... +} + +func applyEnvOverrides() { + // 将 InitConfig 里现有的 DB/MYSQL/JWT/LDAP 环境变量覆盖逻辑整体迁移到这里复用 }🤖 Prompt for AI Agents
缺少对占位符/空 JWT 密钥的启动校验
即使新增了
JWT_KEY覆盖,未设置环境变量时仍会接受config.yml中的占位符密钥(your-jwt-key)。这会让服务在可预测密钥下签发/校验 token,存在认证绕过风险。建议在配置加载完成后做强校验并失败启动。建议修复(示例)
🤖 Prompt for AI Agents