From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>,
Hannes Laimer <h.laimer@proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox-backup 3/5] fix #4382: api2: remove permissions and tokens of user on deletion
Date: Wed, 21 Dec 2022 10:23:09 +0100 [thread overview]
Message-ID: <a971a959-4a95-581f-5c13-cdebfc544ce0@proxmox.com> (raw)
In-Reply-To: <20221220145714.63985-4-h.laimer@proxmox.com>
On 20/12/2022 15:57, Hannes Laimer wrote:
> Signed-off-by: Hannes Laimer <h.laimer@proxmox.com>
> ---
> src/api2/access/user.rs | 24 +++++++++++++++++++++++-
> 1 file changed, 23 insertions(+), 1 deletion(-)
>
> diff --git a/src/api2/access/user.rs b/src/api2/access/user.rs
> index ce676252..40177c8d 100644
> --- a/src/api2/access/user.rs
> +++ b/src/api2/access/user.rs
> @@ -346,7 +346,7 @@ pub fn update_user(
> )]
> /// Remove a user from the configuration file.
> pub fn delete_user(userid: Userid, digest: Option<String>) -> Result<(), Error> {
> - let _lock = pbs_config::user::lock_config()?;
> + let _user_lock = pbs_config::user::lock_config()?;
> let _tfa_lock = crate::config::tfa::write_lock()?;
>
> let (mut config, expected_digest) = pbs_config::user::config()?;
> @@ -390,6 +390,28 @@ pub fn delete_user(userid: Userid, digest: Option<String>) -> Result<(), Error>
> }
> }
>
> + // delete_token needs the user config lock, therefore we have to drop it here
> + drop(_user_lock);
opens us up for a data race though. Why not have a private (or marked unsafe)
delete_token_no_lock fn that we can call here and in delete_token?
Alternative but similar: a private do_delete_token that takes the locks as
parameters, probably nicer.
Did not looked at the whole code closely in recent times, so there may even
better ways - possible encapsulating this in a impl on a User/AuthId type
(especially helpful if we want to re-use this for other projects); but for now
I think the do_delete_token taking the locks as parameters would be the
simplest and nicest to avoid races and other issues.
> +
> + let user_tokens: Vec<ApiToken> = config
> + .convert_to_typed_array::<ApiToken>("token")?
> + .into_iter()
> + .filter(|token| token.tokenid.user().eq(&userid))
> + .collect();
> + for token in user_tokens {
> + if let Some(name) = token.tokenid.tokenname() {
> + let user = token.tokenid.user();
> + delete_token(user.clone(), name.to_owned(), None)?
> + }
> + }
> +
> + // delete_token needs the acl config lock, that's why it is not aquired at the beginning
s/aquired/acquired/
> + let _acl_lock = pbs_config::acl::lock_config()?;
> +
> + let (mut tree, _digest) = pbs_config::acl::config()?;
> + tree.delete_authid(&Authid::from(userid));
> + pbs_config::acl::save_config(&tree)?;
> +
> Ok(())
> }
>
next prev parent reply other threads:[~2022-12-21 9:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 14:57 [pbs-devel] [PATCH proxmox-backup 0/5] ACL removal on user/token deletion + token regeneration Hannes Laimer
2022-12-20 14:57 ` [pbs-devel] [PATCH proxmox-backup 1/5] pbs-config: add delete_authid to ACL-tree Hannes Laimer
2022-12-20 14:57 ` [pbs-devel] [PATCH proxmox-backup 2/5] fix #4382: api2: remove permissions of token on deletion Hannes Laimer
2022-12-20 14:57 ` [pbs-devel] [PATCH proxmox-backup 3/5] fix #4382: api2: remove permissions and tokens of user " Hannes Laimer
2022-12-21 9:23 ` Thomas Lamprecht [this message]
2022-12-20 14:57 ` [pbs-devel] [PATCH proxmox-backup 4/5] fix #3887: api2: add regenerate token endpoint Hannes Laimer
2022-12-21 9:56 ` Thomas Lamprecht
2022-12-21 10:53 ` Fabian Grünbichler
2022-12-21 13:06 ` Thomas Lamprecht
2022-12-20 14:57 ` [pbs-devel] [PATCH proxmox-backup 5/5] fix #3887: ui: add regenerate token button Hannes Laimer
2022-12-21 11:04 ` Thomas Lamprecht
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=a971a959-4a95-581f-5c13-cdebfc544ce0@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=h.laimer@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox