mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-26 01:35:54 +03:00
[GH-ISSUE #2937] Very large notes cause problems #1418
Labels
No labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
pull-request
question
troubleshooting
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vaultwarden#1418
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @przemub on GitHub (Nov 28, 2022).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/2937
Subject of the issue
Thank you so much for this re-implementation, I love it!
When I was bored, I created a secure note, of approximately 15 MB size, consisting of repeating 4-character string. I used the Firefox extension.
I observed the following problems:
Actually, the last problem was how I discovered what caused this :)
Probably, some limit is needed, or maybe not searching inside the whole note?
Deployment environment
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden:
Steps to reproduce
Expected behaviour
Actual behaviour
@BlackDex commented on GitHub (Nov 28, 2022):
We currently do not impose a limit. Maybe we should, but that will break previous large sized notes. We should think about what to do. Maybe we can make a difference between new and previous notes, that way older items can still be preserved, and newer items will have a limit.
Not searching them is a client side item, which we do not maintain.
@dani-garcia commented on GitHub (Dec 1, 2022):
I think checking the limit on save would work to preserve the existing notes while limiting any new ones that are created, you couldn't edit the existing ones but that's a minor thing, I think. We could create an option if that breaks someone's use case but I would prefer to limit the number of config options we support.
We definitely shouldn't keep the current unlimited notes if it breaks search, bitwarden import and the ios client though.
@BlackDex commented on GitHub (Dec 1, 2022):
It definitely breaks exports from Vaultwarden and then import to Bitwarden. But providing an option to break clients is probably not something we should add.