superseeded by v2: https://lore.proxmox.com/pve-devel/[email protected]/T/#u
On Tue Jul 29, 2025 at 12:40 PM CEST, Fabian Grünbichler wrote: > > So the order will the lock TFA -> lock user cfg -> update user cfg -> > > update tfa cfg. > > yes, unless you find another code path that does the inverse (lock user > first, then lock TFA while the lock is held) - in that case we need to > settle on one of the two variants ;) I think it's not possible to do the other way around as when i checked the implementaion of `lock_tfa_config` in PVE::AccessControl if the user config is locked it's not possible to acquire a tfa lock. Also there is a comment that mentions about locking of the files are only allowed together in one order. _______________________________________________ pve-devel mailing list [email protected] https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
