On Mon, Nov 25, 2019 at 19:28, David Díaz <dgonza...@suse.de> wrote:
Hi there!
Today, while I was working to fix an issue when executing "yast2
system_settings" without enough permissions[1][2], some questions
arose
to my mind. Let me share them,
* If I run "/usr/sbin/yast2" it warns about the permissions and only
shows a few modules[3]. So,
* Can we manage [1] and [2] in a "centralized" way? I mean, do we
have
a way to know in advance when the execution of a certain module will
require root permissions? If the answer is NO,
* Can we open a discussion/research/whatever to do something to this
regard? Do you think it worth it? Or do you already had such
discussions
in the past? If so, what was the conclusion?
Apart from these questions, a little bit off-topic but also related to
the topic, I found weird that "yast2 storage" prompt a warning[4]
saying
> The storage subsystem is locked by an unknown application.
> You must quit that application before you can continue.
>
> Would you like to abort or try again?
when it is executed as a normal user. Actually is a problem with
permissions, not an "unknown application locking the storage
subsystem".
Sounds like a job for polkit ;)
The only way YaST is currently aware of a need of elevated permissions
is contents of the desktop file. This however is very limited, because
it only allows elevating permissions to root, even if the user has
permissions to perform the actions without switching to root.
LCP [Stasiek]
https://lcp.world
--
To unsubscribe, e-mail: yast-devel+unsubscr...@opensuse.org
To contact the owner, e-mail: yast-devel+ow...@opensuse.org
