From 23faf7409280802c03ec5086611d37cef61a86dd Mon Sep 17 00:00:00 2001 From: Jakob Scheid Date: Sun, 3 May 2026 18:06:45 +0200 Subject: [PATCH] Bug fix: use heximal SHA256 hash instead of bytes (repr) integrations.gitea.middlewares.signature.GiteaSignatureMiddleware.dispatch used the Python bytes representation of the SHA256 hash for comparision in the f-string. Now, the hexadecimal hash is used. --- .../integrations/gitea/middlewares/signature.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/jcloud_deployment_server/integrations/gitea/middlewares/signature.py b/src/jcloud_deployment_server/integrations/gitea/middlewares/signature.py index 9eab7db..b2e3ede 100644 --- a/src/jcloud_deployment_server/integrations/gitea/middlewares/signature.py +++ b/src/jcloud_deployment_server/integrations/gitea/middlewares/signature.py @@ -54,7 +54,7 @@ class GiteaSignatureMiddleware(BaseHTTPMiddleware): self.secret, body, hashlib.sha256 - ).digest()}', + ).hexdigest()}', signature ): raise HTTPException(status_code = 401, detail = 'Invalid signature')