langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 12:05:30 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

[PR #28374] feat: add configurable password hash iterations for enhanced security #32027

New Issue
Open
opened 2026-02-21 20:50:36 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 20:50:36 -05:00
Owner
Copy Link
Copy Source

Original Pull Request: https://github.com/langgenius/dify/pull/28374

State: open
Merged: No

Summary

Risk
Hardware Evolution: Modern GPUs and specialized hardware (such as ASICs) can compute billions of hashes per second. 10,000 iterations provide insufficient cost for brute-force attacks.

Industry Standard Changes:

OWASP recommended at least 600,000 iterations for PBKDF2-SHA256 in 2023
NIST SP 800-63B recommends at least 10,000 iterations (this is a 2017 standard, now considered outdated)
Some security experts suggest 1,000,000+ iterations should be used in 2025
Real-World Impact: If a database is breached, attackers using modern hardware can rapidly test common passwords and dictionary attacks. The time cost provided by 10,000 iterations is nearly negligible.

fix https://github.com/langgenius/dify/issues/28576

**Original Pull Request:** https://github.com/langgenius/dify/pull/28374 **State:** open **Merged:** No --- ## Summary Risk Hardware Evolution: Modern GPUs and specialized hardware (such as ASICs) can compute billions of hashes per second. 10,000 iterations provide insufficient cost for brute-force attacks. Industry Standard Changes: OWASP recommended at least 600,000 iterations for PBKDF2-SHA256 in 2023 NIST SP 800-63B recommends at least 10,000 iterations (this is a 2017 standard, now considered outdated) Some security experts suggest 1,000,000+ iterations should be used in 2025 Real-World Impact: If a database is breached, attackers using modern hardware can rapidly test common passwords and dictionary attacks. The time cost provided by 10,000 iterations is nearly negligible. fix https://github.com/langgenius/dify/issues/28576
yindo added the pull-request label 2026-02-21 20:50:36 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#32027
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?