<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>User-Management on LinuxHosted.com</title><link>https://www.linuxhosted.com/tags/user-management/</link><description>Recent content in User-Management on LinuxHosted.com</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>LinuxHosted.com</copyright><lastBuildDate>Thu, 18 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.linuxhosted.com/tags/user-management/index.xml" rel="self" type="application/rss+xml"/><item><title>Manage Linux Users and sudo Permissions on a VPS</title><link>https://www.linuxhosted.com/post/manage-linux-users-sudo-permissions-vps/</link><pubDate>Thu, 18 Jun 2026 00:00:00 +0000</pubDate><guid>https://www.linuxhosted.com/post/manage-linux-users-sudo-permissions-vps/</guid><description>
&lt;p&gt;Every shared-root server has the same origin story. One person spins up the VPS, a second needs access so they get handed the root password, a contractor joins and gets it too, and within a year nobody can say who logged in last week or who still knows the password that protects everything. When something is deleted at 3 a.m., the audit trail is a single word: &lt;code&gt;root&lt;/code&gt;. Proper user management is the cure, and on Linux it is neither hard nor optional — give every human their own account, grant privilege narrowly through &lt;code&gt;sudo&lt;/code&gt;, and the question &amp;quot;who did this?&amp;quot; always has a real answer. This guide sets that up from a fresh server.&lt;/p&gt;</description></item></channel></rss>