-
-
Notifications
You must be signed in to change notification settings - Fork 738
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Client can override server storage-quota #4093
Comments
|
For borg hosting providers, this might be a security issue, because users could use unlimited resources, even if the provider set a quota on |
|
Distro packagers should consider cherry-picking this commit for their packages, right? |
See also borgbackup/borg#4093 for this.
See also borgbackup/borg#4093 for this. (cherry picked from commit 0cfc923)
|
@ThomasWaldmann Current 1.1.8 milestone stuck for 15+ days. Is it possible to release binaries with this patch with version named like '1.1.7.1' or '1.1.8' now or near future? |
|
I'll release 1.1.8 soon. |
|
@ThomasWaldmann How soon is soon? ) |
Have you checked borgbackup docs, FAQ, and open Github issues?
Yes
Is this a BUG / ISSUE report or a QUESTION?
BUG
System information. For client/server mode post info for both machines.
Your borg version (borg -V).
1.1.7
Operating system (distribution) and version.
Debian 9
Hardware / network configuration, and filesystems used.
Ext4
How much data is handled by borg?
10MB
Full borg commandline that lead to the problem (leave away excludes and passwords)
borg init -e none ssh://$REPO_HOST --storage-quota 1000Mborg serve --restrict-to-repository /srv/repos/nz71ss19/repo --storage-quota 10M --append-only(server)Describe the problem you're observing.
The repo-config file always gets the quota specified by the client. Quota-enforcement is also as per client-set quota.
Can you reproduce the problem? If so, describe how. If not, describe troubleshooting steps you took before opening the issue.
Run client and server commands (set in ssh
command=)Include any warning/errors/backtraces from the system logs
No errors
Possible fix by extending
forced_resultas done in #4091The text was updated successfully, but these errors were encountered: