all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pbs-devel@lists.proxmox.com, Christian Ebner <c.ebner@proxmox.com>
Subject: applied: [PATCH proxmox 0/3] s3-client: fix request signing and update request time on retry
Date: Wed, 11 Nov 2026 23:00:46 +0100	[thread overview]
Message-ID: <179443424650.1210260.2843796365713327912.b4-ty@b4> (raw)
In-Reply-To: <20261007123406.429342-1-c.ebner@proxmox.com>

On Wed, 07 Oct 2026 14:34:03 +0200, Christian Ebner wrote:
> This patch series fixes 2 issues with the current s3-client
> implementation.
> 
> In particular:
> - Patch 1 fixes an issue with s3-client request signing, encountered
>   during development. The canonical request headers and query
>   parameters were incorrectly sorted by key+value strings instead
>   of key only, which could lead to sorting mismatches with the API
>   server, resulting in signature mismatches and therefore rejected
>   requests. In particular, this might be encountered if one header
>   name is a prefix to another header name.
>   Fixed by sorting headers and queries via their respective key only.
> - Patches 2+3 fix a not updated request time for requests being
>   retried. This could potentially lead to `RequestTimeTooSkewed`
>   errors when the time in-between retried requests is very large and
>   might explain such errors observed as reported in the community
>   forum [0].
>   Fixed by setting the current request time and updating the request
>   signature each time before sending the request via the client.
> 
> [...]

Applied, thanks!

For the first patch I adapted the query parameter handling a bit: the
parameters are now URI-encoded first and only then sorted, with the
encoded value ordering duplicate names, as that is the order the SigV4
docs specify for the canonical request [0]. Sorting the raw pairs could
still produce a different order than the server computes, e.g., for
names where the encoded form sorts differently or for repeated
parameters.

[0]: https://docs.aws.amazon.com/IAM/latest/UserGuide/create-signed-request.html

[1/3] s3-client: fix header and query parameter sorting during aws sign v4
      commit: 91e7f7e8a135d3bc3826ab50e05d3126c039df11
[2/3] s3-client: factor out request signing and related header updates
      commit: 97960079e9c715559ac7d94421a5eb40d1052740
[3/3] s3-client: update request time and signature on retries
      commit: 07a4feb646fdeaf4651da81490bb921b646d80e4




      parent reply	other threads:[~2026-11-11 22:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-07 12:34 [PATCH proxmox 0/3] s3-client: fix request signing and update request time on retry Christian Ebner
2026-10-07 12:34 ` [PATCH proxmox 1/3] s3-client: fix header and query parameter sorting during aws sign v4 Christian Ebner
2026-10-07 12:34 ` [PATCH proxmox 2/3] s3-client: factor out request signing and related header updates Christian Ebner
2026-10-07 12:34 ` [PATCH proxmox 3/3] s3-client: update request time and signature on retries Christian Ebner
2026-11-11 22:00 ` Thomas Lamprecht [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=179443424650.1210260.2843796365713327912.b4-ty@b4 \
    --to=t.lamprecht@proxmox.com \
    --cc=c.ebner@proxmox.com \
    --cc=pbs-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal