Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 22:23:50 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[PR #1352] [MERGED] prevent accidental lockout from restricted chars in single pass mode #3659

New Issue
Closed
opened 2026-02-22 18:34:14 -05:00 by yindo · 0 comments
yindo commented 2026-02-22 18:34:14 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/Mintplex-Labs/anything-llm/pull/1352
Author: @timothycarambat
Created: 5/10/2024
Status: ✅ Merged
Merged: 5/10/2024
Merged by: @timothycarambat

Base: master ← Head: 1289-prevent-protected-chars-in-authToken

📝 Commits (2)

  • e7a555d prevent accidental lockout from restrict chars in single pass mode
  • 8fd76c6 update error message

📊 Changes

2 files changed (+22 additions, -5 deletions)

View changed files

📝 frontend/src/pages/GeneralSettings/Security/index.jsx (+14 -4)
📝 server/utils/helpers/updateENV.js (+8 -1)

📄 Description

Pull Request Type

  • ✨ feat
  • 🐛 fix
  • ♻️ refactor
  • 💄 style
  • 🔨 chore
  • 📝 docs

Relevant Issues

resolves #1289

What is in this change?

Prevent a password-protected instance from being self-owned by accidentally using .env file-protected chars in their password since they will be either removed or escaped and therefore the password will no longer match or will be broken on instance reboot as loading from the .env on boot will only boot what the system can read as opposed to what the user actually wanted the password to be.

Regex: /^[a-zA-Z0-9_\-!@$%^&*();]+$/

Additional Information

Developer Validations

  • I ran yarn lint from the root of the repo & committed changes
  • Relevant documentation has been updated
  • I have tested my code functionality
  • Docker build succeeds locally

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/Mintplex-Labs/anything-llm/pull/1352 **Author:** [@timothycarambat](https://github.com/timothycarambat) **Created:** 5/10/2024 **Status:** ✅ Merged **Merged:** 5/10/2024 **Merged by:** [@timothycarambat](https://github.com/timothycarambat) **Base:** `master` ← **Head:** `1289-prevent-protected-chars-in-authToken` --- ### 📝 Commits (2) - [`e7a555d`](https://github.com/Mintplex-Labs/anything-llm/commit/e7a555db17fe2316a01f724c210847acdd336612) prevent accidental lockout from restrict chars in single pass mode - [`8fd76c6`](https://github.com/Mintplex-Labs/anything-llm/commit/8fd76c6ab19ef47f957c24ada28c5a9150a30dab) update error message ### 📊 Changes **2 files changed** (+22 additions, -5 deletions) <details> <summary>View changed files</summary> 📝 `frontend/src/pages/GeneralSettings/Security/index.jsx` (+14 -4) 📝 `server/utils/helpers/updateENV.js` (+8 -1) </details> ### 📄 Description ### Pull Request Type <!-- For change type, change [ ] to [x]. --> - [ ] ✨ feat - [x] 🐛 fix - [ ] ♻️ refactor - [ ] 💄 style - [ ] 🔨 chore - [ ] 📝 docs ### Relevant Issues <!-- Use "resolves #xxx" to auto resolve on merge. Otherwise, please use "connect #xxx" --> resolves #1289 ### What is in this change? <!-- Describe the changes in this PR that are impactful to the repo. --> Prevent a password-protected instance from being self-owned by accidentally using `.env` file-protected chars in their password since they will be either removed or escaped and therefore the password will no longer match or will be broken on instance reboot as loading from the `.env` on boot will only boot what the system can read as opposed to what the user actually wanted the password to be. Regex: `/^[a-zA-Z0-9_\-!@$%^&*();]+$/` ### Additional Information <!-- Add any other context about the Pull Request here that was not captured above. --> ### Developer Validations <!-- All of the applicable items should be checked. --> - [x] I ran `yarn lint` from the root of the repo & committed changes - [x] Relevant documentation has been updated - [x] I have tested my code functionality - [x] Docker build succeeds locally --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-22 18:34:14 -05:00
yindo closed this issue 2026-02-22 18:34:14 -05:00
yindo changed title from [PR #1352] prevent accidental lockout from restricted chars in single pass mode to [PR #1352] [MERGED] prevent accidental lockout from restricted chars in single pass mode 2026-06-05 15:14:33 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
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: Mintplex-Labs/anything-llm#3659
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?