Thank you for your feedback. I understand the concerns about the security approach in the script. The use of sudo was intended to provide a way to discover clusters without requiring permanent elevated privileges. However, I realize this might introduce security risks.
I would appreciate any suggestions on how to handle privilege requirements more securely while detecting PostgreSQL clusters that aren't managed by Debian tools. My aim was to improve visibility across different cluster management methods, but I want to ensure it aligns with best practices. Would an alternative approach that avoids it sudo entirely, even with more limited detection capabilities for non-postgres users, be preferable? Best regards, Akash On Tue, Apr 1, 2025 at 4:53 PM Christoph Berg <m...@debian.org> wrote: > Re: AKASH > > Security & Efficiency: Runs only with sudo, minimizing privilege > > escalations. > > I have no words for this. > > Christoph >
