From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id D0B9B1FF187 for ; Mon, 28 Jul 2025 14:57:54 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 7CD1632EE8; Mon, 28 Jul 2025 14:59:18 +0200 (CEST) From: Thomas Lamprecht To: pbs-devel@lists.proxmox.com, Shannon Sterz Date: Mon, 28 Jul 2025 14:56:30 +0200 Message-ID: <175370737726.827548.14111433684683088963.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.2 In-Reply-To: <20250725112357.247866-1-s.sterz@proxmox.com> References: <20250725112357.247866-1-s.sterz@proxmox.com> MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1753707517432 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.031 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pbs-devel] applied: [PATCH proxmox{, -backup} 0/4] HttpOnly follow-ups X-BeenThere: pbs-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox Backup Server development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox Backup Server development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pbs-devel-bounces@lists.proxmox.com Sender: "pbs-devel" On Fri, 25 Jul 2025 13:23:53 +0200, Shannon Sterz wrote: > this small series tries to smooth out the transition to HttpOnly cookies > for our users: > > - cookies are now removed by the server if a 401 UNAUTHORIZED error is > encountered. this matches the behaviour of our previous javascript > browser-based clients. it is necessary, as they can't remove the > cookie themselves anymore due to the new security measures. > - log-in is possible again, even if an invalid HttpOnly cookie is > provided. > - `Expire` is removed from the cookies to make them "session cookies" > again. this should restore security assumptions some users may have > made about closing their browser and being logged out. note that > session cookies may still be restored after a browser was closed, if > the browser uses session restoration. > > [...] As you already noticed: Applied, thanks! [1/1] api/proxy: set auth cookie name in rest server api config commit: 8f4e455550e470a670f139d6124a00887962122c [1/3] rest-server: remove auth cookies via http header on unauthorized request commit: 4ef6a1c012a5e32d3059731094c31864ddd3fa78 [2/3] auth-api: don't set `Expire` for HttpOnly cookies anymore commit: f45eb2934c484b652e8b3676b508d0ea1e9142d6 [3/3] auth-api: allow log-in via parameters even if HttpOnly cookie is invalid commit: 2c0b5edda2f778837c4d2eb8a259a04c3dca8ebd _______________________________________________ pbs-devel mailing list pbs-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel