From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>, Stefan Sterz <s.sterz@proxmox.com>
Subject: [pbs-devel] applied: [PATCH proxmox-backup] auth: request a write lock when exposing the `LockedTfaConfig`
Date: Wed, 24 Apr 2024 21:28:29 +0200 [thread overview]
Message-ID: <98f516a5-ae66-4828-ae5e-f3fecb99d143@proxmox.com> (raw)
In-Reply-To: <20240412123155.178657-1-s.sterz@proxmox.com>
Am 12/04/2024 um 14:31 schrieb Stefan Sterz:
> this function is called every time a user tries to log in to check
> whether a tfa challenge is required. since the tfa config may need to
> be written by the auth api (e.g. when a recovery key is used) this
> needs to use a write lock instead of a read lock in order to avoid
> potential races.
>
> Signed-off-by: Stefan Sterz <s.sterz@proxmox.com>
> ---
> src/auth.rs | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>
applied, thanks!
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
prev parent reply other threads:[~2024-04-24 19:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 12:31 [pbs-devel] " Stefan Sterz
2024-04-24 19:28 ` 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=98f516a5-ae66-4828-ae5e-f3fecb99d143@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
--cc=s.sterz@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox