update to latest upstream master #11
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This fixes vulnerability GO-2022-0969 reported by govulncheck: HTTP/2 server connections can hang forever waiting for a clean shutdown that was preempted by a fatal error. This condition can be exploited by a malicious client to cause a denial of service. Call stacks in your code: Error: cmd/serve/restic/restic.go:150:22: github.com/rclone/rclone/cmd/serve/restic.init$1$1 calls golang.org/x/net/http2.Server.ServeConn Found in: golang.org/x/net/http2@v0.0.0-20220805013720-a33c5aa5df48 Fixed in: golang.org/x/net/http2@v0.0.0-20220906165146-f3363e06e74c More info: https://pkg.go.dev/vuln/GO-2022-0969
…k host on windows (#6420)
The API endpoint GetBucketLocation requires top level permission. If we do an authenticated head request to a bucket, the bucket location will be returned in the HTTP headers. Fixes #5066
… header - fixes #5730 Before this fix it was impossible to stop rclone generating an X-Amx-Acl: header which is incompatible with GCS with uniform access control and is generally deprecated at AWS.
…sizes differ
Before this change, some files were giving this error when downloaded
from Cloudflare and other providers.
ERROR corrupted on transfer: sizes differ NNN vs MMM
This is because these providers auto gzips the object when rclone
wasn't expecting it to. (AWS does not gzip objects without their being
uploaded gzipped).
This patch adds a quirk to for fix the problem and a flag to control
it. The quirk `might_gzip` is set to `true` for all providers except
AWS.
See: https://forum.rclone.org/t/s3-error-corrupted-on-transfer-sizes-differ-nnn-vs-mmm/33694/
Fixes: #6533
As of Go 1.16, the same functionality is now provided by package io or package os, and those implementations should be preferred in new code.
Solves link error while running rclone's wasm version. Go's `walltime1` function was renamed to `walltime`. This commit updates wasm_exec.js with the new name.
Before this change if --s3-no-head was in use rclone didn't check the multipart upload ETag at all. However the ETag is returned in the final POST request when completing the object. This change uses that ETag from the final POST if --s3-no-head is in use, otherwise it uses the ETag from a fresh HEAD request. See: https://forum.rclone.org/t/in-some-cases-rclone-does-not-use-etag-to-verify-files/36095/
The block size for crypt is 64k + a few bytes. The default block size for sftp is 32k. This means that the blocks for crypt get split over 3 sftp packets two of 32k and one of a few bytes. However due to a bug in pkg/sftp it was sending 32k instead of just a few bytes, leading to the 65% slowdown. This was fixed in the upstream library. This bug probably affected transfers from over the network sources also. Fixes #6763 See: pkg/sftp#537
This adds support for providing custom Go templates for use in the `rclone authorize` command. Fixes #6741
docker volume plugin restoreState: skip fs option if empty Fixes #6769 Co-authored-by: Peter Kreuser <logo@kreuser.name>
Before this change, all types of checkers showed "checking" after the file name despite the fact that not all of them were checking. After this change, they can show - checking - deleting - hashing - importing - listing - merging - moving - renaming See: https://forum.rclone.org/t/what-is-rclone-checking-during-a-purge/35931/
…ferring files There were some places (e.g. deleting files) where we were using --transfers instead of --checkers to control the concurrency when files weren't being transferred. These have been updated to use --checkers.
Before this change if an --s3-profile was set which used AWS STS (eg to assume a role) and --s3-endpoint was set then rclone would use the value from --s3-endpoint to contact the STS server which did not work. This fix implements an endpoint resolver which only overrides the "s3" service if --s3-endpoint is set. It sends the "sts" service (and any other service) to the default resolver. Fixes #6443 See: https://forum.rclone.org/t/s3-profile-failing-when-explicit-s3-endpoint-is-present/36063/
In preparation for Microsoft removing the SHA1 hash on OneDrive Personal this allows the hash type to be set on OneDrive. See: https://forum.rclone.org/t/microsoft-is-switching-onedrive-personal-to-quickxorhash-from-sha1/36296/
Before this change the hash used for Onedrive Personal was SHA1. From July 2023 Microsoft is phasing out SHA1 hashes in favour of QuickXorHash in Onedrive Personal. Onedrive Business and Sharepoint remain using QuickXorHash as before. This choice can be changed using the --onedrive-hash-type flag (and config option) so that SHA1 can be selected while it is still available in the transition period. See: https://forum.rclone.org/t/microsoft-is-switching-onedrive-personal-to-quickxorhash-from-sha1/36296/
Some ISPs throttle HTTP which MEGA uses by default, so some users may find using HTTPS beneficial.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is the purpose of this change?
Was the change discussed in an issue or in the forum before?
Checklist