#pkexec
Live, measured metrics for the hashtag #pkexec from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #pkexec
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-28 03:46 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · fosstodon.org (Mastodon public search API) · fetched 2026-07-28 03:46 UTCNo related tags with measured usage found for #pkexec.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 03:46 UTCEverything below is measured over the latest 9 public posts (spanning ~37357 hours).
Posting hours (UTC)
Languages: English (8) · German (1)
Avg boosts / post: 2.4
Top of the latest posts
While #NixOS should not be affected by #CopyFail as it uses recent kernels, here are additional fixes you can apply: Disabling setuid does not mitigate it, but reduces the attack surfaces overall significantly. Instead of #sudo, #su, #pkexe
Rooted another OSCP machine this morning. There is no other exploit that has been more widespread and easy to leverage than pwnkit (CVE-2021-4034). I've simply lost count of the the number of machines I've been able to use this on to get ro
@debacle @xpac: #pkexec alleine ist schon grusig, siehe z.B. CVE-2021-4034. Und da dann noch #JavaScript dahinter? 🤮 Gut, dass man auch sehr gut ohne #PolicyKit, #sudo und ähnliche #LPE-anfällige Programme leben kann — auch auf dem #Linux
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/pkexec