Are there good examples of how to optimally design a program on #Linux that is meant to generally run in userspace, but occasionally requires to execute a root command in a way the user is *not* prompted by polkit every time out of the blue but only once when the program is installed?
A persistent polkit rule looks super icky (I don't see how I could prevent process impersonation, maybe I'm missing sth?). Is there any clean, standardised way for this?
#coding #Python
Natanox 🔜 #40C3
npub1zm…thp6u
2026-07-23 12:56:55 UTC
Author Public Key
npub1zmqeumjs7pyqwfs7un4rcdqs7mlavh9mzghz6ls4psd54kvy8xlq5thp6uSeen on
wss://relay.ditto.pubPublished at
2026-07-23 12:56:55 UTCEvent JSON
{
"id": "2f8fbcd5e9649033d7e5ca632aa174d6a0a5ee8b6a93f2af6cab0f61853aa4ad",
"pubkey": "16c19e6e50f04807261ee4ea3c3410f6ffd65cbb122e2d7e150c1b4ad98439be",
"created_at": 1784811415,
"kind": 1,
"tags": [
[
"t",
"linux"
],
[
"t",
"coding"
],
[
"t",
"python"
],
[
"proxy",
"https://chaos.social/users/Natanox/statuses/116969400943030258",
"activitypub"
],
[
"client",
"Mostr",
"31990:6be38f8c63df7dbf84db7ec4a6e6fbbd8d19dca3b980efad18585c46f04b26f9:mostr",
"wss://relay.ditto.pub"
]
],
"content": "Are there good examples of how to optimally design a program on #Linux that is meant to generally run in userspace, but occasionally requires to execute a root command in a way the user is *not* prompted by polkit every time out of the blue but only once when the program is installed?\n\nA persistent polkit rule looks super icky (I don't see how I could prevent process impersonation, maybe I'm missing sth?). Is there any clean, standardised way for this?\n#coding #Python",
"sig": "536f1d7323f8e145b8a6038c5c787baaa58ae78ccbaffbe9edd49de700707159ee6491184eb8fef6825385ce4a318ed51ec7521792a4a4c80725e39ec5539901"
}