https://bugs.kde.org/show_bug.cgi?id=523364
Mike H <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|1 |0 Status|CONFIRMED |REPORTED --- Comment #4 from Mike H <[email protected]> --- Look, I won't disclaim this came from Gemini(AI Search) But it MAKES A LOT OF USEFUL POINTS. Please, for the love of god, explain to me why Discover does not follow sudo/polkit timeout limits. Industry Standards & Defaults Most secure operating systems use a short window that expires quickly but allows a user to complete a multi-step task (like updating a system) without re-typing their password for every command. • Sudo Default: 15 minutes (on Ubuntu/Debian) or 5 minutes (on Fedora/RHEL). • Polkit Default: Commonly 5 minutes, or restricted strictly to the current process/session. • Package Managers: Usually inherit the underlying sudo or polkit timeout rather than managing their own. Recommended Configurations 1. Standard Desktop Users • Recommended Time: 5 to 15 minutes. • Rationale: Perfect balance for developers or general users running sudo apt update && sudo apt upgrade. It keeps the cache alive long enough for compilation or multi-package installs to finish without prompting again mid-process. 2. High-Security / Corporate Environments • Recommended Time: 0 minutes (Always prompt) or restricted by TTY. • Rationale: Zero caching ensures that if a user walks away from their desk, an attacker cannot execute administrative commands. 3. Servers & Remote SSH Sessions • Recommended Time: 0 minutes or per-session only. • Rationale: Session hijacking or left-open terminal multiplexers (like tmux/screen) pose a high risk. -- You are receiving this mail because: You are watching all bug changes.
