session 的 uuid 是v4 ，v4 是随机生成，是有可能重复的吧
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 5.3k
- Forks
- 614
- PR merge metrics
- No merged PRs in 30d
Description
DESC
ENV
OS Platform:
Node.js Version:
ThinkJS Version:3.0
code
// your code here
error message
// your error message here
more description
// your detail description
如果session 是保存到redis 的，那这样不会有人拿到别人的session id 吗？想请问下这样是否有问题，因为我们的项目中出现奇怪的问题
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating ThinkJS's session UUID generation and Redis-backed session lookup; no file or test is named in the report. Reproduce the reported behavior and verify whether UUID collisions can expose another session, then document the finding and any required change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js, redis
- Domain
- authentication, backend, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100