Repository navigation
fix(user): verify current pay key before update - #254
Closed
Aether-254 wants to merge 3 commits into
Closed
Aether-254 wants to merge 3 commits into
Aether-254 wants to merge 3 commits into
Conversation
Aether-254
marked this pull request as draft
October 6, 2026 02:10
Aether-254
force-pushed
the
fix/verify-current-pay-key
branch
from
October 6, 2026 02:16
3a12370 to
d10bdc1
Compare
Aether-254
force-pushed
the
fix/verify-current-pay-key
branch
from
October 6, 2026 02:17
d10bdc1 to
ee22a66
Compare
Aether-254
marked this pull request as ready for review
October 6, 2026 02:55
|
此 PR 长期无活动，将在 14 天后自动关闭。如需继续讨论请回复 |
Author
|
111
Aether_254
***@***.***
|
Collaborator
|
原密码忘记需要怎么修改呢 |
Author
可以改成类似二验的形式？现在这种拿到credit/l站账户 即使不知道支付密码就能改然后就能转走，是不是不太安全了些 |
Collaborator
如果账号已经被拿到，通过 API Key 也能调用接口操作；邮件验证也有发送频率限制所以目前的支付密码更多是一道二次验证，主要是避免误触后直接完成支付和支付流程体验 |
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.
例行检查
关联信息
resolves #253
变更内容
变更原因
现有
PUT /api/v1/user/pay-key只接收新密码并直接覆盖数据库中的安全密码，前端也无需输入原密码。仅修改前端仍可通过直接请求 API 绕过，因此需要由后端执行强制校验。验证
go test ./...go vet ./internal/apps/userpnpm lintpnpm buildgit diff --check